• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Novell to AD Conversion..

E

Enderz76

Junior Member
I'm having an issue at work after our migration away from NDS to AD. Server conversions have gone without a hitch, or seemingly so, however now that we're starting to remove the Novell client from our Windows XP Pro machines, we're seeing about 1 out of 4 PC's getting stuck on the "Applyling Computer Settings" box when logging into the workstation. It is taking over 4 minutes for the screen to go away. I've checked the MS Forums and posts in regards to WebDav, DNS Authoratative DNS zones and the Webclient service, all to no avail. Anyone out there who still remembers NDS to AD conversion issues?

Any assistance would be greatly appreciated.
 
HUGE profiles being copied over would be a guess ... unless these are brand spanking new log ins, that shouldn't have any data attached yet.
 
Thank you for your response Viv. Unfortunately not a profile issue as new user's are experiencing the same issue, however it's totally random some user's experience it while their next door neighbor does not. We've elminated GPO's for test user's and it's still the same issue, which I found extremely strange as I was sure it was a GPO issue. If you put the Novell client back on said machine, it logs into the network within a minute.
 
So many variables. Any clues in event viewer? Sometimes there are DNS/DHCP type issues that slow down the PC at that point...
 
It really could be so much. Try a new machine, or a new image.... It sounds like you have isolated it from being a profile issue.
 
Are there any events logged in event viewer? Netlogon can put events in application, system and security. You can also try rebuilding the TCP/IP stack as netware would hook it. Also be absolutely sure your DNS and DHCP settings are correct as well as the AD sites and services if your in a multi-location environment.
 
Thanks guys for the responses. Yes so many areas to filter through, but I think I've narrowed it down. For some reason in the AD profile, the Home directory seems to be the culprit, when I get rid of the Home directory mapping the issues ceases. Now to figure out why the issue is being caused by a network drive mapping issue..... :\
 
Enderz76 said:
Thanks guys for the responses. Yes so many areas to filter through, but I think I've narrowed it down. For some reason in the AD profile, the Home directory seems to be the culprit, when I get rid of the Home directory mapping the issues ceases. Now to figure out why the issue is being caused by a network drive mapping issue..... :\
Click to expand...

Were these 2000/XP machines? If they are, Netware used to replace the "GINA" rather than use the MS one. MS updated the GINA several times through patches from windows update. You may be running on an old and now mostly incompatible version.

I may be way off base here but what you just mentioned reminded me of a problem we had using a certain Biometric software that did the same thing. Tons of stuff didn't work because they were not passing all of the information that the stock GINA did. (like missing home paths.)

Stock GINA does stuff like pass "home directories" and sets the environment variables like %homedrive%.%homepath%,%LOGONSERVER%, handles "CTRL-ALT-DELETE" etc. We tore are hair out trying to figure out why stuff like that had vanished until we narrowed it down to that one app.

More info:
http://msdn.microsoft.com/en-us/library/aa380543(VS.85).aspx
 
Thats very helpful, thank you kindly. I know when we initially setup Cisco's Checkpoint VPN client we ran into an GINA issue with the Novell client. I'll look into that and re-post on Monday for my test results. Thank you again for your posts!
 
If you get the lag while maping the home drive try:

Right click on "My Network Places" and choose "Properties".
In the Network Connections Window click on "tools" and "Advanced Settings"
In the "Adapters and Bindings" tab make sure IPX is not checked (better to remove it if its on the system but thats your choice) for the NIC.
On the "Provider Order" tab make sure Microsoft Windows Network is at the top of the list.

Novell may still be the top provider which would cause the delay as it times out trying to connect to \\YourServer on the Novell side and moves down the list until it can connect.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top