Can't connect via TermServ nor RDP on the LAN

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.

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" <(E-Mail Removed)> wrote in message
news:4C0684A3-95C1-4441-A198-(E-Mail Removed)...
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.

I ran it and it says "TCP Port 3389 <unknown service> : Listening"

What does this mean? I get the same response on any server I run this on
and they all have the same answer - but all other servers can teminal serve
or rdp to each other without a problem, only the one server in question can I
NOT termserv or rdp to?

Thanks for any help (could you reply to my email " (E-Mail Removed) " as
this will get to me quicker)

Monte Taylor
(E-Mail Removed)


"Todd J Heron" wrote:

> 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" <(E-Mail Removed)> wrote in message
> news:4C0684A3-95C1-4441-A198-(E-Mail Removed)...
> 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.
>
>
>

I think the terminal service may be re-mapped to listen on a different port
than 3389. Check that.

1. Start Registry Editor.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\TerminalServer\WinStations\RDP-Tcp\PortNumber
3. On the Edit menu, click Modify, and then click Decimal.
4. Type 3389, and then click OK.
5. Quit Registry Editor and restart the system.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"TTime" <(E-Mail Removed)> wrote in message
news:A73A1986-83E0-4DB4-A17C-(E-Mail Removed)...
I ran it and it says "TCP Port 3389 <unknown service> : Listening"

What does this mean? I get the same response on any server I run this on
and they all have the same answer - but all other servers can teminal serve
or rdp to each other without a problem, only the one server in question can
I
NOT termserv or rdp to?

Thanks for any help (could you reply to my email " (E-Mail Removed) " as
this will get to me quicker)

Monte Taylor
(E-Mail Removed)


"Todd J Heron" wrote:

> 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" <(E-Mail Removed)> wrote in message
> news:4C0684A3-95C1-4441-A198-(E-Mail Removed)...
> 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.
>
>
>