2003 Terminal Server no longer accepting RDP connections

[avallach]

We have 3 WS 2003 Terminal Servers in our environment, one of which
has been sitting idle for years because of an Office error. I took it
upon myself to fix that problem today. Office was installed
improperly (possibly before the server was made a terminal server) by
a predecessor, and could not be removed gracefully. I removed it via
the registry then deleted the Office folders, rebooted, reinstalled
Office properly, all was well.

Then I tried to Remote Desktop to the server (named TERM3), which has
always worked. It won't connect. I try to telnet to 3389, I get
"Could not open connection to the host, on port 3389: Connect
failed." I go to the server's physical console, everything looks
normal. I delete and recreate the RDP listener using TERM1 and TERM2
as a model, reboot, still won't connect.

I can remote desktop from the server's physical console to itself and
it works fine. There is no firewall running on the system. I didn't
do any service packs or other updates, just brute-force-removal of
Office and then reinstall.

TERM1 is the licensing server, when I go to Terminal Server Licensing
I can see it's online and activated.

Any help would be greatly appreciated.

 

[Roman Gallauner]

Re: 2003 Terminal Server no longer accepting RDP connections

When you do a

netstat -an | find ":3389"

what line do you get?


Regards
Roman

"avallach" <avallach@gmail.com> wrote in message
news:acd167ad-5c43-40bc-b4db-52610a636ca5@a35g2000prf.googlegroups.com...
> We have 3 WS 2003 Terminal Servers in our environment, one of which
> has been sitting idle for years because of an Office error. I took it
> upon myself to fix that problem today. Office was installed
> improperly (possibly before the server was made a terminal server) by
> a predecessor, and could not be removed gracefully. I removed it via
> the registry then deleted the Office folders, rebooted, reinstalled
> Office properly, all was well.
>
> Then I tried to Remote Desktop to the server (named TERM3), which has
> always worked. It won't connect. I try to telnet to 3389, I get
> "Could not open connection to the host, on port 3389: Connect
> failed." I go to the server's physical console, everything looks
> normal. I delete and recreate the RDP listener using TERM1 and TERM2
> as a model, reboot, still won't connect.
>
> I can remote desktop from the server's physical console to itself and
> it works fine. There is no firewall running on the system. I didn't
> do any service packs or other updates, just brute-force-removal of
> Office and then reinstall.
>
> TERM1 is the licensing server, when I go to Terminal Server Licensing
> I can see it's online and activated.
>
> Any help would be greatly appreciated.