• 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.

Windows clients taking a loooong time to logon to domain

Z

Zucarita9000

Golden Member
So, a few days ago several client computers on our network are taking waaay too long to logon to the domain. It used to be fairly fast, but now the thing just stalls at setting up network connection, loading profiles and so on. I can't seem to find a solution.

We have a SBS 2003 server controlling the domain, and nothing has changed. The only thing I can think of is that a few weeks ago we changed to our summer daylight savings time, but I don't believe that could be the reason.

I haven'e set up any GPOs besides the ones that are built-in into SBS 2003. There are no strange TCP/IP settings, the DHCP server works just fine and there's no packet loss from the clients to the server and back. The network has a gigabit backbone with 100Mbps to each client. Cisco routers, certified Cat6 installation. I can't think of anything.
 
Sounds like a DNS problem, check to make sure your client computers can resolve your domain controllers IP properly 🙂
 
Look at the client computers profile size. I once had a user with a profile over 400MB in size who complained about slow logins. Once we cleaned up his profile, everything was fine.

DNS is also a possibilty but if you have changed nothing and this just started happening, it probably is not DNS.
 
Originally posted by: dphantom
Look at the client computers profile size. I once had a user with a profile over 400MB in size who complained about slow logins. Once we cleaned up his profile, everything was fine.

DNS is also a possibilty but if you have changed nothing and this just started happening, it probably is not DNS.
Click to expand...

Just because he didn't change anything doesn't mean someone else didn't change something 😛
 
Originally posted by: MedicBob
Check the Event logs on both the AD DC and on the clients.
Click to expand...
Also, check the SBS Licensing screen, just in case. And, yeah, a DNS resolution problem (can't find the Domain Controller) is a "normal" cause of this problem.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top