RE: RDP failed to access TS with none-default port

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Try telneting to that port.
Click Start/Run, type cmd, hit Enter.
Type telnet 56.123.47.254:13389 and see if you receive a succesful connection.
Do you perhaps have some extra firewall/security software installed?
Tried turning off Windows firewall just for the sake of the test?

A.

"Peter" wrote:

> I could not use WinXP Pro to connect to a terminal server (Win2K Advanced
> Server) which use a non-default port. The address is something like this:
> 56.123.47.254:13389. Everyone else in my firm can connect to it. Also I can
> connect to any Terminal Server with default port ( i.e. no port number on the
> address such as 34.63.12.34). It seems that the problem is related to the
> type of PCs. The only two laptops with this problem are HP nw8000, one is XP
> Pro SP1 and another is XP Pro SP2. The error message is:
>
> The client could not connect to the remote computer
> Remote connections might not be enabled or the computer might be too busy to
> accept new connections. It is also possible that network problems are
> preventing your connection.
>
.



Relevant Pages

  • Re: Connection Problems
    ... can you connect with the normal rdp client? ... can you ping to port 3389 on the TS? ... > still receiving the connection failed message that Marius ... >> between the client and the terminal server, ...
    (microsoft.public.windows.terminal_services)
  • Re: Correction
    ... Normally to physically disconnect is just a matter of reaching for the ... >> I have an ADSL connection which polls my computer from time to time, ... > disallow each and every port with Windows Firewall? ...
    (microsoft.public.windowsxp.messenger)
  • Re: Using Remote Desktop From an SBS Domain
    ... when you tried to RDP while attached directly to a port on your router? ... Internet to initiate an IP conversation with your computer. ... This situation is different than if you ran your own NAT connection sharing ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server User cant work unless they are administrators...
    ... > When logging into Terminal Server as an admin I can run EFT ... Port 4992 is a security layer ... > and the connection to DB1(database server that houses the ... > Sedona thinks it's a Group Policy problem. ...
    (microsoft.public.windows.terminal_services)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)