Slow login process for Windows 2003

[mortsdeh]

Hi,

I am having a problem I hope anyone can help me with.

The company I work for deliveres an application with clients that runs on its own domain with DNS.

The production server is running Windows 2003 server and when logging on to that server using a Remote Desktop Connection the logging in process is very slow. And when logged in, some processes such as changing user rights are very slow.

Where do you recommend me to start locking to be able to solve this problem?

/M

 

[porkchopexpress]

I would check that DNS is configured correctly. Which server holds the DNS role and does the TS server use this as it's primary DNS server?





When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[mortsdeh]

Thank you for your annswer.

Our domain looks as follows: A firewall limits our domain so that all that is allowed is inbound remote desktop connections. Everything else is blocked such as e.g. outbound Internet surfing. Our domain consists of two domain controller servers with DNS (when setting up domain controllers DNS must be activated, the default settings are used), some clients and PLC. The communication in our developed application use only IP addresses and not domain names.

We have tried to turn off DNS on our two domain servers, but the login is still slow. (CPU Usage is a few percentages)

Does SQL Server replication work without any DNS servers?

Any ideas?
Best, /M

 

[porkchopexpress]

Are the terminal servers on the same net as the DC's without the firewall in the way?

If you turned the DNS off on the servers this will probably make the issue worse.

IF this is a DNS issue then you need to check if your DNS is configured correctly and that your Terminal Servers are looking to your DC/DNS servers for name resolution.

E.g if your DC holds teh DNS role and it's IP address is 192.168.0.10 then your TS servers should have 192.168.0.10 as their primary DNS server.

If you logon locally to the TS server do you get the same slow logon?






When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[mortsdeh]

Thank you for your help. We were able to find the problem smoothly thanks to your replies.

The clients don't use DHCP and there were no DNS server specified. So, we specified the DNS server on the clients and the login process is fast again.

Best,
/M

 

[porkchopexpress]

Glad to help.





When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.