Re: Can't connect via TermServ nor RDP on the LAN
- From: "Todd J Heron" <todd_heron_no_spam@xxxxxxxxxxx>
- Date: Mon, 12 Sep 2005 21:52:52 -0400
Use portqry.exe to tell you if it's listening on tcp 3389.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
"TTime" <TTime@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4C0684A3-95C1-4441-A198-B750AB4E9EC2@xxxxxxxxxxxxxxxx
For some reason simple RDP or Terminal Services will not connect to one
particular server (not running licensed TermServ - just std version) whereas
I could before. I can terminal serv to another server from this one
unavailable server but cannot connect to it from any other server on the
network, nor remotely from home.
The knowlege base doesn't give any good answers whatsoever.
Connecting via Terminal Services get "The Terminal Server has ended the
connection"
Trying with Remote Desktop I get "The connection was ended because of a
network error"
All TCP/IP is correct, DNS is correct, and all network connectivity with
applications, etc. are all just fine. Everything works and has worked
without issues with the exception of simply trying to TermServ to this
particular server in question.
I had this problem long ago and fixed it but cannot for the life of me
recall what I did nor did I document it (shame on me I know!!!)
Any help would be appreciated.
.
- References:
- Can't connect via TermServ nor RDP on the LAN
- From: TTime
- Can't connect via TermServ nor RDP on the LAN
- Prev by Date: Re: can't browse domain
- Next by Date: Re: Can't get default gateway
- Previous by thread: Can't connect via TermServ nor RDP on the LAN
- Next by thread: Can't get default gateway
- Index(es):
Relevant Pages
|