Very slow logon time...on workstations

Gimmyno

Hey guys,

I have a problem with all my workstations in the domain, basically all workstations are shared by different agents (CC environment with different permissions), every single time someone tries to login onto the pc it will take approx 20 to 40 minutes to be able to see the desktop...The pcs are quite old Dell 210L 512mb of ram, but no heavy softwares are installed on the machines....I can see that it runs the start up scripts but...20 to 40 mins is crazy!!! Any ideas guys? What to check?

undomiel

I'd first check your AD health, make sure that they're not having any problems finding and contacting a DC. Next thought would be to check on whether you're using roaming profiles and how large those profiles are. If you still haven't found the problem or a clue to lead you to the problem then it is probably time to turn on group policy logging and see where all the logon time is being spent.

mctwist

I highly suspect a DNS problem. Is it possible your workstations DNS are configured to your point to your ISP DNS? If so, change them to point to your DNS server (which probably is the AD server if it's a smaller environment).

rwmidl

Do you have any "newer" computers? I'm wondering if they are just so "old" they are taking extra logon times?

Gimmyno

Thanks guys for your reply....I also noticed...then it does not only do this when someone logs in, it also takes ages when the pc is restarted and I can see "Applying Conf Settings" before being able to type my credentials.I also forgot to mention that I can see the usual "Running Logon Scripts" for 5/10 mins...

JeanM

Gimmyno wrote: »

Thanks guys for your reply....I also noticed...then it does not only do this when someone logs in, it also takes ages when the pc is restarted and I can see "Applying Conf Settings" before being able to type my credentials.I also forgot to mention that I can see the usual "Running Logon Scripts" for 5/10 mins...

Stand up another CLEAN install on a spare box or VM and test/compare, sounds like it could be OS/config issue not related to network (profile maybe), based on your last reply that is.

nycid

mctwist wrote: »

I highly suspect a DNS problem. Is it possible your workstations DNS are configured to your point to your ISP DNS? If so, change them to point to your DNS server (which probably is the AD server if it's a smaller environment).

I agree verify DNS. DNS is a ***** and about 90% of problems for this sort of thing...

Gimmyno

Thanks guys ,

I 've found this in the logs on all Pcs:

The system failed to update and remove host (A) resource records (RRs) for network adapter
with settings:

Adapter Name : {58E0997C-B8AB-410B-BA19-7EBA3456D8825}
Host Name : MYPC
Primary Domain Suffix : domain.domain.com
DNS server list :
10.x.x.x, 10.x.x.x
Sent update to server : 10.x.x.x
IP Address(es) :
10.x.x.x


And This DHCP;

Your computer was unable to automatically configure the IP parameters for the Network Card with the network address 60EBR43F50E48. The following error occurred during configuration: The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.

Any suggestion?

joehalford01

Make sure that you have enough available ip addresses in your DHCP range and that DNS is aging and scavenging effectively; clearing old records. This should all work seamlessly without too much intervention in a small environment but if your infratructure is aging, something could be dropping the ball.
Also, it sounds like you have a "wait for the network" gpo applied, this forces the computers to completely apply all group policy changes everytime the computer is booted up and everytime the user logs in before allowing access to the user. If something is slowing the network down and the computers are slow on top of that, it could be a problem as well. I'm configuring brand new workstations right now and when I first bring them onto the domain it takes several minutes for all of the gpos to apply; I could imagine this would be excessive in a slow network with old computers.

undomiel

Have you done any of the above mentioned troubleshooting? What did you discover during the troubleshooting? Is the client actually receiving an address from DHCP or not?

whatthehell

DCdiag /verbose?
Perhaps try flushing DNS on one of the workstations and testing?
Not sure if this was asked or answered, but is this a new environment? Or was it working well before?

Are the clients all local to the DC? Or remote? Dialing in?

Gaber

Do you have roaming profiles? Check how big the user profiles are. Do a gpresult after logged in and check all applied group policies. Have a look through event viewer to see if anything is flagged up there.

Gimmyno

Hi guys,

thanks everyone for your reply,I'm still testing.The current DC with connections was setup from another person, the DC has 3 NICs connected to the same switch, I noticed that one of the port on the switch which is connected straight to the DC is flashing amber/green, I checked it on the switch and it is set to "Half Duplex" 100 Mbps and has loads of Collisions.I believe this is affecting performance,setting it to Full Duplex makes it worse "Full Amber" light on the port.

Any ideas?

TLeTourneau

It would help to know how the NIC's are configured (teamed, fail-over, etc.) and if the switch supports those connections. Have you tried unpluging/disableing NIC's to see it that helps? It could be several things.

Gimmyno

Yes, I tried to unplug it and plugged it back again but no better...I even rebooted the whole switch last night...

Claymoore

Gimmyno wrote: »

Hi guys,

thanks everyone for your reply,I'm still testing.The current DC with connections was setup from another person, the DC has 3 NICs connected to the same switch, I noticed that one of the port on the switch which is connected straight to the DC is flashing amber/green, I checked it on the switch and it is set to "Half Duplex" 100 Mbps and has loads of Collisions.I believe this is affecting performance,setting it to Full Duplex makes it worse "Full Amber" light on the port.

Any ideas?

Turn the port back to auto-negotiate. Both the port and the NIC have to be manually set to the same speed/duplex setting or both have to be auto. Manually setting the port speed may have been a good recommendation in 1998, but this is 2012.