Cant access terminal server but other clients can

raylward102 · 11-04-2005, 04:38 PM

We have MS Windows 2000 server running terminal services in application mode. The terminal server is on the same LAN as the client that connects to it. I was always able to connect to the server in the past. I am able to access all other servers/workstations via rdp except for the terminal server. The only thing that has changed in the last two weeks is that I have re-installed my os on my workstation. Fresh install of xp-pro. I had no problems re-joining it back to the domain. I can ping the terminal server, connect to shares on the terminal server but no rdp. To get around this, I have been connecting via rdp to another workstation on our network and in turn using it to connect to the terminal server. (Dbl rdp connect). As soon as I press connect from my workstation, it immediately tells me that it’s not possible. No delay's either. Instant denial. Any ideas? All 25 terminal service clients that are currently using the server have not complained. I just want to figure it out before it happens to someone else.

crazijoe · 11-08-2005, 05:38 AM

I don't know how your AD is setup but does your computer (not user) need to be in an OU that gives it permissions?

11-04-2005, 04:38 PM	#1 (permalink)
raylward102 Registered User Join Date: Nov 2005 Posts: 1 OS: XP	Cant access terminal server but other clients can We have MS Windows 2000 server running terminal services in application mode. The terminal server is on the same LAN as the client that connects to it. I was always able to connect to the server in the past. I am able to access all other servers/workstations via rdp except for the terminal server. The only thing that has changed in the last two weeks is that I have re-installed my os on my workstation. Fresh install of xp-pro. I had no problems re-joining it back to the domain. I can ping the terminal server, connect to shares on the terminal server but no rdp. To get around this, I have been connecting via rdp to another workstation on our network and in turn using it to connect to the terminal server. (Dbl rdp connect). As soon as I press connect from my workstation, it immediately tells me that it’s not possible. No delay's either. Instant denial. Any ideas? All 25 terminal service clients that are currently using the server have not complained. I just want to figure it out before it happens to someone else.

11-08-2005, 05:38 AM	#2 (permalink)
crazijoe Registered User Join Date: Oct 2004 Location: Omaha, The Center of the Universe Posts: 7,632 OS: WinXP, Win2K3 My System	I don't know how your AD is setup but does your computer (not user) need to be in an OU that gives it permissions? __________________ Microsoft MCSA + Messaging, MVP, A+, Network+ http://i16.photobucket.com/albums/b3...other/Help.jpg Do you want a real Republican? HDD diagnostic tools / HDD data recovery software