Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win 2k laptop can not TS into server; other PCs can

Status
Not open for further replies.

j93saturn

Technical User
May 8, 2003
91
US
Here's the deal:

Windows 2000 laptop has on-board NIC and modem, 3 dial-up accounts (AOL, SBC, Net-Zero), and is currently connected to DSL.

Server is Windows 2000 Server with Terminal Services running. PCs at the location of the server connect via LAN without any issues. PCs on the other side of town, on a different network, mixed OS (Windows 2000 and XP) can also connect without a problem.

Laptop had connected to Server at one time (about a year ago). It was used a couple of times and then put away. Tried to connect today and I get an error message of "The Terminal Server has ended this session". Tried all three different dial-up accounts and useing DSL. Always get the same error.

I have gone to windowsupdate.com on the laptop and made sure that it has all neccesary updates. Downloaded and installed Remote Desktop Connection app from MS. I still am not haveing any luck. If anyone could piont me in the right direction, that would be great. Thank you.
 
Do you get to the point where it prompts for a user name and password?
Does the terminal server have at least one free license?

Matt
 
On other PCs (offsite) I can get to the logon prompt. The laptop gives me the error shortly after I hit the connect button.

As for Licenseing, I have no idea.
 
Can you ping the IP address??? Sounds like its not making the initial connection...

Matt
 
No, I can not ping it from the laptop. But then again, I can not ping it from the PC I am at right now either, but I can TS to it.

Tracert from both machines, takes about 13 hops and quits, if that helps any.
 
Ok, then it sounds like an issue with your client software. Verify the encryption level is proper, and forgive me if this offends you, but make sure the IP address is accurate in the RDP client. If not, try reinstalling the client.

Matt
 
Don't worry about offending me, I know what it is like. Anyways, IP is good, cause PC I am on will connect to the Server just fine. I'll check the encryption level and try re-installing the client software and then the OS. Thanks. I am glad to know I am not the only one who can not figure out this weird problem in 15 minutes of less.
 
hi,

have a look at client registry using regedit:
see if there are, any entries under

HKLM\SOFTWARE\Microsoft\MSLicensing\Store

If there are, remove them .

bye
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top