Mysterious Terminal Server connection prob on a XP workstation

We have a problem with one workstation that is connecting to our
Windows 2000 server running 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.  I tried removing NAVCE, still does it.

I even restored the mahcine from a backup using PowerQuest V2i.  I had
taken a snapshop of the machine sometime after it was installed, so i
wiped the HD, and restored that snapshop.  Still does it.

I don't want to have to wipe XP and reinstall everything from scratch.
 We have a very detailed config with lots of settings done just right.
 Lots of email accts programmed in.

I'm getting desperate to get this working.. 

Any ideas? 

Thanxs in advnce,

http://support.microsoft.com/default.aspx?scid=kb;EN-US;328930

Try uninstalling and resintalling SP1 (if you can).

Other things to try:
-Start > All Programs > Accesories > System Tools > System Restore
-Start > Run > scf /scannow
-Boot from the OS cd, run the Recovery Console, at prompt type: chkdsk /r
-Boot from the OS cd, run the the System repair (Start the Install,
Repair should be prompted for right after the Licensing Agreement)

ooops spelling mistake...
2nd line should be:

Start > Run > sfc /scannow

It runs the System File Checker which checks for any corrupt files in
the OS (which I'm thinking is the case)

I have seen this...

Open Regedit
Navigate to the follwing
HKey_Local_Machine->Software->Microsoft
Find the MSLicensing Key
Highlight it..
File->export.. give the file a name

With the MSLicensing Key highlighted, Hit delete and delete the whole key.

You shoul now be able to log on using Terminal Services.

CompBL

sherpaj:

To go with compbl-ga's comment, see:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;323597

http://www.winnetmag.com/Article/ArticleID/21535/21535.html

Read this second article carefully.

Regards,

aht-ga
Google Answers Researcher

I'll try and let you know.  thanks.

Every Remote desktop client has a license assigned by the terminal
server , you must clean your actual invalid license and re-request a
new license.

you can clean the license with this secuence

run the regedit.exe program Start->run->regedit

Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\

and delete the MSLicensing node.

With this, your problem must be solved.

If everything is OK with the Server and the client OS and if you can
see (ping ~ip~) the server from the client check this:
Do you have free TS connections - start,programms, administrative
tools,terminal services manager;
Did you install software on the server between the point that it was
working and when it stoped?
Do you have Norton WinFax on the server?
Do you have any services starting/loging with an user account? -
Default is "local System Account" if you have you will have to change
it back to the default and try TS then. The reason is that the
services can be "counted" for users and this will lower your # of
avaible TS sessions. I used to have a software that starts when
somebady logs onto the server ut never shut down when the user logs
out/restart so after few days I had :"The Maximum # of connections was
exceeded at the remote computer" even when nobady was loged in. The
only solution was to unistall the software and boot (once) in safe
mode to clean the sessions!
BTW Win2k is shiped with 2 TS license e.g. 2 people can be loged in at
the same time; You can buy more licenses but they sell the by 5,12 or
25 I think.

i tired all the above.  No luck.

Problem resolved.

I deleted all my RDC bookmarks, created new ones, and now it works. 
very very strange.   I had previously tried restoring these bookmarks
from a known good backup, but that didn't work.

Maybe something in what you guys posted was a factor after all.  

Not sure what to do with awarding the answer.  I feel like several of
you helped alot, even if it wasn't the whole answer in this case.  Can
I split the answer?  If not, please advise what the fiar thing to do
it.

thanks!

sherpaj-ga:

With the exception of my 'two-bits' above, none of the commentors on
this question are Researchers. Since your problem is now gone, just go
ahead and cancel the question, you found your Answer on your own. :)

Regards,

aht-ga
Google Answers Researcher