Login issues on Terminal Server

[superco7]

I am running Server 2003 SP1 Standard Edition with Terminal Services installed. Everything has been running great for about 6 months or so, that is until today. When a user try’s to login into the server using rdp, it takes an insane amount of time, it just sits at the login screen (a blank blue window) forever. I tried rebooting the server, and when I logged back onto the server itself with the administrative account, I experienced the same problem (took approx 6 mins to get to the desktop and was very slow once in there). I have also restarted using the selective startup (with DCOM Service Disabled), everything works great, only not all the programs will run without the DCOM service started. No major changes have been done to this server within the last week. Any help would be greatly appreciated. If you need any more information, please let me know.

Thanks in advace

 

[porkchopexpress]

When you get on as an admin can you run taskmanager and see if the processor is running full tilt of lots of memory being used?

 

[superco7]

Yeah that was one of the first things I checked, and everything seems to be running just fine; I should have probably mentioned that in my previous post, sorry about that. I have 2 Gb of memory installed with less than 1 Gb being used and the processor isnt pinged either. I also checked out what processes are running and nothing seems out of the ordinary.

 

[porkchopexpress]

This shouldn't really affect you now but if you use an APC UPS then take a look at this.

http://nam-en.apc.com/cgi-bin/nam_en.cfg/php/enduser/std_adp.php?p_faqid=7202

 

[porkchopexpress]

Is this an Active Directory domain?

Any chance you are having DNS problems?

Check DNS settings on the TS and make sure they all point to a local DNS server as its primary DNS server.

 

[superco7]

I do have the server connected to an APC UPS but I dont have the powerchute software installed on it.

I checked the DNS settings on the server just to make sure they are still correct, and it appears that they are. The only way I could check it was through the command prompt using ipconfig command, I couldnt get to it using network connection properties, as no connections were displayed.

 

[superco7]

Yes this server is part of an Active Directory Domain, its only role is to be a terminal server.

 

[porkchopexpress]

Did you say that you had tried logging on to the physical console and got the same result?

 

[superco7]

Yeah, when I have it selected to normal startup, it boots fine but after I enter my login credentials, it hangs at the blue windows screen for about 6 o 7 minutes before it brings my desktop up.

 

[porkchopexpress]

If this isn't a DC can you logon to the local admin acc?

 

[porkchopexpress]

Also can you use computer management to connect to the server event viewer from a workstation to check for any errors?

 

[lyndy]

Having the same problem with one of our hosted servers....we moved clients to new server and the problem repeated. Separated one of the clients onto a third machine and problem happened again....but now the other servers are OK....We think it is a Printer Driver issue. Trying to narrow down the potential drivers...looks like HP but not sure. Problem surfaces just a little while after installing the new printer driver...(we think).

 

[blakey2]

Hi All,

I checked the DNS settings on the server just to make sure they are still correct, and it appears that they are. The only way I could check it was through the command prompt using ipconfig command, I couldnt get to it using network connection properties, as no connections were displayed.

Does this not mean that perhaps the NIC is knackered or that the IP stack has become corrupted in windows?

That is the path i would investigate...

Goodluck.

 

[lyndy]

...other item that I neglected to mention, that causes us to think it is printer driver related....cannot access the Printer and Fax configuration through the Control Panel, once the desktop finally opens (after 6-10 minutes or even longer).

 

[lyndy]

We think that the printer driver in question is for the HP Color Laser Jet 2600n. AFter removing this printer driver (not just uninstalling the printer). The problem seems to have been eliminated....Does anybody else have that driver installed?

 

[JGALEY]

superco7, I noticed you said that when you stopped the DCOM service, logons were fine, but some apps would not work. I get occasional DCOM errors in my Event Viewer --> System log. Do you get any DCOM-related errors there?

Jason

http://www.catotek.com

 

[superco7]

Yes I did get one particular DCOM error quite a few times in my event viewer, that is what tipped me off that it might have something DCOM, so I did a selective boot and disabled the dcom service...

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 3/6/2006
Time: 5:40:25 PM
User: N/A
Computer: ServerName
Description:
The server {<GUID of the component>} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

I also have a HP2600 on my network, but do not believe that I have the driver installed on this Server.

 

[jgolde00]

I am having a different issue with Terminal Server \ remote desktop running on 2003. Everything will be running fine, then for what ever reason I can't remote into the server.

Check all of the services everything is OK. Try the reboot and pray but no luck.

When I run NMAP on the server and an identical testing server. Port 3389 is running on one but not the other, all updates and programs being the same on both.

Thanks for any help you can give.