[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 247
  • Last Modified:

Single Login for NetWare, NT, Windows (without NDS for NT)

I have a network on a college campus with both NetWare 4.1 and NT servers.  Users' login names and passwords are the same on each server.  Is there a way for Windows 95 to have a single consistent login to both servers and avoid the Windows Password prompt.  I understand if I set a password for Windows and save the NT password in the password file,  this could be accomplished but our users are roaming from PC to PC in computer labs and libraries and would have to go through the windows password dialogue everytime they use a PC they have not used before.  The way it stands now, when a user logs in to a PC they have not used before, they get the Client32 login for Netware, then the Windows Login, then the Windows NT login.  I just want to have a single login on every machine.   Is there a way to accomplish this?  Please do not recommend NDS for NT.  I am aware of the product but do not wan't to purue that just yet.  Thanks.
0
davebrock
Asked:
davebrock
1 Solution
 
paulnicCommented:
...he says no to NDS for NT and thinks it's easy!?   ;-)

May be a stretch, but depending on how strong the authentication requirement is to each of the three entities, can you do something with including the login to one in another's login script, or a BAT file, or a startup group?  For instance, if a shared generic ID is OK for one server, or no Windows95 login is really needed.....

just a thought.
0
 
admintcCommented:
I would very much like to contact "davebrock" as we have the same setup and I would like to get some information from him.

Thanks
Tracey Chambers
admintc@warthog.ru.ac.za

0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now