Networking Win2k with Novell, Just a little problem.

[Patrician]

I just finished networking a windows 2k pro box to a Novell network. So I logon using Novell's client for Window 2000/NT and as soon as a do Windows brings up it's own logon window and asks me to logon to the machine. So I end up loging on twice, once to Novell and once to the machine. The problem is that this is supposed to be a machine that anyone with a Novell logon can use. But as it is you have to have a Windows logon on that machine in order to logon as well. How can I make it so that You only need to logon to Novell, and not windows.

Any Help would be WONDERFUL!!!

Peter

 

[spidey07]

AFAIK - you will always have to log onto windows. Be it a domain account or a local machine account you will have to log on to windows. Best thing to do is make sure your passwords are the same and use the options menu of the netware client to pick the microsoft account you're using.

The novell client will synch all the passwords for you, that way you only enter one password. But you are still authenticating to MS networking and NDS.

 

[Patrician]

The only problem is that this computer is supposed to be a workstation. which means that any person that's going to logon to it has to have a local user account, and we have a lot of users that will be using this computer.

PEter

 

[spidey07]

looks like they are logging in twice then.

<edit> haven't really dealt with this in a while. maybe the newer NW clients can get around this.

 

[Nothinman]

If you have ZenWorks for Desktops (think 3 or higher, not exactly sure) you can have the Novell client not require a local logon, basically it creates a temporary local account for the time you're logged in.

 

[DenverBuc]

I disagree partly. Yes, you always have to logon to the machine, but your Novel Client should be able to do that for you as well. My company has run that way for years and I only have to log on once, not twice. There should be an option in your Novell logon to the effect of also logon to NT or 2000. Look for that - I will dig into our logon a bit and see if I can get you some more specifics.

 

[Scarpozzi]

Are you part of a domain? I think there's a way to consolidate your login if the Domain user/pass matches the Novell user/pass. I'm pretty sure if you uninstall the Novell Client and run the Microsoft Client for Novell instead, you may be able to get to only one logon. It will take some work, but you should be able to do it......somehow.

 

[Patrician]

I wouldn't mind swithching to just the microsoft novell logon but the people above me say I have to use the Novell Client.
There is no domain available to validate win2k logons.

Peter

 

[SaigonK]

So here is what is wrong:


A. You have a local account,
Novell logs onto the network then detecs a local profile with the same name and asks you to provide the information for it.

B. You can type in the user name for this account then the password then check the box that says:
"make my windows password the same as my netowrk password"

The reason for this whole thing is because of the local profile, if you would use roaming profiles then you wont have this issue.
The person logs onto the server, the Novell box sends down their profile form their home drive and then they can run their apps.
(providing they are setup for this pc. Once the decide to log out, the profile will get copied up to the server and all changes they made that are profile specific will go with them to the next workstation they touch.

If you need more info or help LMK, been doing this for awhile now =)

SK

 

[quxio]

I've seen this at work before. Basically, there are a few things that cause this issue. The last time I saw it, there was an issue with Novell's win2k client where if you logged in with the fully distinguished user ID and the context was set to something different than that user's, it would pop up with a windows logon box. There was a subsequent patch that fixed it.

I would recommend using the latest client (4.81). If that doesn't work, try searching the win2k client newsgroup on Novell's site.

Also, I believe the workstation manager piece is required.

 

[SaigonK]

Basically, there are a few things that cause this issue. The last time I saw it, there was an issue with Novell's win2k client where if you logged in with the fully distinguished user ID and the context was set to something different than that user's, it would pop up with a windows logon box. There was a subsequent patch that fixed it.

It isnt the path or the user id its because he has a local profile.

I would recommend using the latest client (4.81). If that doesn't work, try searching the win2k client newsgroup on Novell's site.

You should do this, it is a good idea.

Also, I believe the workstation manager piece is required.

Workstation manager is required for any roaming profiles, if you plan on having a local profile on you're pc's you need to make sure you shut off Workstation Manager or it will remove those profiles when you logout. Be careful with it, it sometimes doesnt shut off even though it says it did, you have to hit it twice to get it to work.