Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / November 2006

Tip: Looking for answers? Try searching our database.

Can Telnet to port 3389 but can't get to logon screen

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bierlyt@gmail.com - 29 Nov 2006 21:40 GMT
Most users are here in the office, and everyone can logon to TS just
fine, but there is one user about an hour's drive from here, that is
not VPN'd in, that connects to TS over the internet.  Normally, he can
connect just fine.

I had him test and he can telnet port 3389 just fine.  It seems to stay
connected, and he has to close the cmd window using the window's X
button (I couldn't figure out how else to exit the telnet session).

But when he tries to connect via the Remote Desktop Client, he doesn't
even make it to the login screen.  I don't have the exact message, but
he said it says the connection has timed out, or something like that.
I can call him back and get exact error message if that helps, but he's
out of the office for a few hours.

In the Terminal Services Manager on the server, I don't see any
disconnected sessions for him, and I never see a session pop up in the
manager while he is trying to connect.  If I do a netstat on the
server, I see 3389 port connection as Established from his ip address.

Any ideas?  I'm thinking potentially a licensing issue with his
computer?  I can login under his account from here just fine.

Thanks in advance,
Toby
Vera Noest [MVP] - 29 Nov 2006 22:04 GMT
You should be able to confirm or rule out a licensing issue by
checking the EventLog on the TS for warnings, and the TS Licensing
manager for available and issued licenses.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:  http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

bierlyt@gmail.com wrote on 29 nov 2006 in
microsoft.public.win2000.termserv.clients:

> Most users are here in the office, and everyone can logon to TS
> just fine, but there is one user about an hour's drive from
[quoted text clipped - 24 lines]
> Thanks in advance,
> Toby
bierlyt@gmail.com - 29 Nov 2006 23:30 GMT
Thanks Vera,

I had plenty of licenses available in the Termal Server Licensing
console.  I did find some 1004 Event Warnings in the Server's event
log.  It might have been the MSLicensingKey, hard to say because
without me doing anything, it is now working this afternoon.  It
doesn't seem that if his Licensing Key in the registry was corrupt this
morning that it would be fine now.  Very strange, but solved for now,
so I won't complain.

Thanks,
Toby

> You should be able to confirm or rule out a licensing issue by
> checking the EventLog on the TS for warnings, and the TS Licensing
[quoted text clipped - 37 lines]
> > Thanks in advance,
> > Toby
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.