Mysterious Terminal Server connection prob on a XP workstation
We have a problem with one workstation that is connecting to our
Windows 2000 serer terminal Services.
This one workstation (XP, sp1) suddenly cannot connect to the terminal
server with XP?s Remote Desktop Connection. All the PCs next to it
can connect fine. It used to be able to connect until one afternoon
last week.
Here is the error message
Remote Desktop Disconnected
The client could not establish a connection to the remote computer.
The most likely causes for this error are:
1) Remote connections might not be enabled at the remote computer
2) The Maximum # of connections was exceeded at the remote computer
3) A network error occurred while establishing the connection
I have tried rebooting both client and server and tried logging off
everyone else off of the server. No luck.
I tried a traceroute, but it after a few hops it is all timeouts. I
heard that ISPs are preventing traceroutes as a security measure. I
started seeing this activity since the blaster virus. I am able to
connect to the terminal server as administrator using VNC, so I know
it can get through.
I tried an ipconfig /renew, tried changing the IP number, quitting all apps, etc.
The machine does fine as far as email and web surfing. I even moved
it in front of the fireware/nat router. It is now on an static
publicly addressable IP number and still won?t work.
It is running NAV corp edition, but no firewall software, no build-in
XP firewall either. And VNC worked, so it is reaching the machine with
non-standard ports.
--------------------------------------------------------------------------------
When I try to think of what may have caused this all of a sudden, I
only came up with one idea.
We have a 2nd terminal serer. A Win 2003 server that was using the
free 120 days of terminal services that come with it.
When the 120 days expired, I bought Terminal Services CALS (licenses)
and went to Install and Activate the Term Server Licensing program.
It accepted my CALs (retail license) and said users could now connect.
They could not. It turns out that the CALs I bought are keyed to
another of our Win 2003 servers, not this one. I didn?t realize the
CALS are keyed to a specific Key.
After I realized that the 2003 server would not work with these CALs,
I uninstalled them and deactivated the Licensing Server. I rebooted
all servers and workstations but the troubled workstation still cannot
connect to the win 2000 terminal server.
These 2 servers are on separate LANs (the 2003 server is a stand alone
box that is not in the domain that the 2000 is the DC of). They are
on the same IP segment though.
After I realized that the 2003 server would not work with these CALs,
I uninstalled them and deactivated the Licensing Server. I rebooted
all servers and workstations but the troubled workstation still cannot
connect to the win 2000 terminal server.
i put up a separate question about this problem.
-------------------------------------------------------------------------------
Any ideas?
Thanxs in advnce, |
