Solved

Mysterious Terminal Server connection prob on a XP workstation

Posted on 2003-11-28
8
1,120 Views
Last Modified: 2010-03-18
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.
---------------------------------------------------------------------------------------------------

Any ideas?

Thanxs in advnce,
sherpajj
0
Comment
Question by:sherpajj
8 Comments
 
LVL 5

Expert Comment

by:koquito
ID: 9842573
try
net sessions /disconnect  at the command prompt to disconnect all the active sessions at the server. Then try again from that XP workstation.
It looks like many sessions are open and the server has reach the limit of simultaneous connections. How many licenses do you have per seat/per server?
0
 

Author Comment

by:sherpajj
ID: 9848591
 I am going into the Terminal Server Manaager and logging everyone out, and then trying.  I am also rebooting and trying.  I bought 5 licenses for it, but only 4 people use it and not usually at the same time.
Should I still try net sessions /disconnect?
0
 

Author Comment

by:sherpajj
ID: 9883474
I did more testing an noticed 2 things:

- The troubled PC works fine on other term servers, just not the one I need (called TSon)
- Other PCs on the same subnet have no prob with Tson.
- tson has 5 licenses (cals) but only 1 or 2 users logged in

Help!
0
 

Author Comment

by:sherpajj
ID: 9883492
one more thing

- the user in question can log in fine from other PCs, so I know the acct is good.

0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 

Expert Comment

by:jafojsharp
ID: 9985643
I have the same exact problem. The only thing I can contribute is when I view the Terminal Server Licensing Manager on The Main DC it shows that the client trying to connect already has two expired licenses. I am trying to find someway of deleting those so the server will release another temp license. Mind you that I am running in Remote Administration mode so I only contend licensing with other computers I login from when on the road.

Let me know if you find the answer and I'll do the same.

jim@kcstech.com
0
 

Expert Comment

by:jafojsharp
ID: 9985665
This may help ya out!!!!!

http://support.microsoft.com/?kbid=315404
0
 

Accepted Solution

by:
jafojsharp earned 500 total points
ID: 9986061
I got it.

If you delete the WinXP key under HKLM\Software\Microsoft\MSLicensing

then it should work, at least it did for me.

here is the article I followed, except I did not mess around with the server registry like it mentions. I did the workstation first.

http://www.jsiinc.com/SUBK/tip5400/rh5407.htm
0
 

Expert Comment

by:walthert
ID: 11180989
I have similar problem, and the accepted answer has not fixed it.

Situation:
I had a Win 2k Terminal server as a member of a SBS 4.5 domain. Everything worked great.
I updated the SBS to SBS 2003 and attached the Win 2k server to its active directory. My Win2k clients and "upgraded" Win XP clients (from Win 2k) can still access the Win 2k Term server, but none of my "fresh" installs of Win XP clients can. They all get the msg listed above.

Any ideas out there?
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

Greetings, Experts! First let me state that this website is top notch. I thoroughly enjoy the community that is shared here; those seeking help and those willing to sacrifice their time to help. It is fantastic. I am writing this article at th…
A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
This video discusses moving either the default database or any database to a new volume.
Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now