Link to home
Start Free TrialLog in
Avatar of LCW1400
LCW1400Flag for United States of America

asked on

Long logon time - windows 7 into 2003 domain

I have a Wiindows 7 machine (SP1) with latest updates on OS and all drivers that is taking a long time to logon to a domain.  

Sits at  "Please Wait" for 3-4 minutes
Sits at "Welcome" Screen for 5-7 minutes
Goes to a Black screen for 1-2 minutes then desktop is displayed

The user profile (as far as I can tell) is local and does not have any log in scripts.
 
I have tried creating a new AD user, turning off IPV6, Disabling "always wait for network at computer logon, updating drivers and OS.  All have result in the same long logon time.

Any help work be very much appreciated.

Avatar of d3ath5tar
d3ath5tar
Flag of United Kingdom of Great Britain and Northern Ireland image

Check you GPO's, see what settings are being applied.
Is there a DC on the site or is it a remote dc?
ASKER CERTIFIED SOLUTION
Avatar of johnb6767
johnb6767
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Is the DNS setting being pulled via DHCP or is the networking manually set?
Avatar of LCW1400

ASKER

Thank you all for the quick responses.

We are connecting through a VPN to the domain.  

This is occurring on only 1 machine.
When the the cable is unplugged the logon speed is normal and fast.

The DNS setting are being pulled via DHCP.

In the interim, I did disconnect a manually added mapped drive on the system and it seems to have fixed the logon in speed.  I will try remapping and see if the speed reverts back to extremely slow.
Avatar of LCW1400

ASKER

The combination of unplugging from network, logging in, removing network drive, logging out, plugging back into the network seems to have fixed the issue with the exception of a "netlogon" screen that is popping up.  

The netlogon screen seems to be pointing to a mapped directory on our server (that no one should have access to). This user doesn't have any logon scripts associated with their profile.

Why would this be?  


SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Does your user have a roaming profile ?
This can take several time depending on the profile size.
In a VPN configuration, I strongly suggest to remove roaming profile and keep it local
Avatar of LCW1400

ASKER

johnb6767
It appears as if explorer is opening it up.  It shows "netlogon on ourservername" at the top and show a mapped folder icon and a listing of folders and files on our server.

I ran autoruns.exe and didn't find anything that looked like it was calling the server and the only file not found was one related to windows media.  Can & where do I I turn off the auto netlogon?

oliverstone:
I don't believe the profile is roaming but I didn't initially set up the system.  In the AD the profile path, logon script, and local path of the user is blank.  Should I be checking somewhere else?

SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
"I ran autoruns.exe and didn't find anything that looked like it was calling the server and the only file not found was one related to windows media.  Can & where do I I turn off the auto netlogon?"

It would probably be a shortcut to that share, or perhaps in the very first Tab, under Logon, it would be a script that cannot be found.....

You do not want to turn off Netlogon Services......

You can use Autoruns (actually I would use MSConfig for this part), and disable EVERYthing on the Startup Tab, reboot and see if Explorer opens again...... If it does, enable them in chunks and use the process of elimination.....
Avatar of LCW1400

ASKER

The combination of unplugging from network, logging in, removing network drive, logging out, plugging back into the network seems to have fixed the issue with the slow logon.

However I am still trying to troubleshoot why the netlogon directory to the server is opening up when the user logs in. I will post again if I get the issue resolved.