RE: Proxying RDP traffic arriving via one port to 3389




Hello PAUL, the windows server you are using with putty IS THE TERMINAL
SERVER?
if yes:

Why you not simply change the Terminal server port to 8888?

If you still want to use putty, and the terminal server is the machine form
you are running putty, then try the following:

Start, Run, Type: "mstsc /v 127.0.0.1:3389" this have to connect to the
local terminal server that is running in the same server, if not, try with
the local IP not the loopback (127...) if still not connect, maybe the
terminal server is not working well ... try reinstalling ...

If the terminal server is another server not the one you are running PUTTY,
then you can't use 127.0.0.1 to make the port forwarding, i don't know if
putty can do the port forwarding to another machine, if not, try using some
other software or a basic router like linksys.

Good luck!

--
Ing. Gonzalo Araújo C
MCP, GCSE, CCNA
SLM Sistemas


"Paul Kennedy" wrote:

> I work on an agent application which facilitates server management. One of
> the features I'd like to provide is to allow RDP traffic to be delivered
> across the network, arriving at a port, say 8888, where this agent is
> listening, and have the agent forward this traffic to port 3389.
>
> To simulate this functionality, I installed putty.exe on a W2K3 server,
> configured putty to port forward from port 8888 to 127.0.0.1:3389 and tried
> to use mstsc.exe running on the same W2K3 server to connect to port 8888. The
> connection attempt failed with the followiing message displayed by mstsc.exe
> in a dialog box:
>
> "The client could not establish a connection to the remote computer".
>
> The putty logfile states:
>
> 2005-12-21 14:56:12 Opening forwarded connection to 127.0.0.1:3389
> 2005-12-21 14:56:12 Forwarded connection refused by server: Connect failed
> [Connection refused]
>
> Why is the RDP server refusing the connection attempt ? Is there any way I
> can get the RDP server to accept the RDP traffic ?
>
.



Relevant Pages

  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: Ports and more
    ... Also, just to let you know, we just opened a support ticket with Microsoft ... KB938645 is about a situation where the COM port *is* succesfully ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • RE: RDP VS RWW to Terminal Server
    ... You would like to know the differences between RDC and RWW. ... sites often required configuring the server for VPN or dial-up connections. ... TCP port 4125, in essence keeping the connection alive. ... For how to deploy Terminal Server on in SBS 2003 network, ...
    (microsoft.public.windows.server.sbs)
  • RE: Some technical errors
    ... If the SMTP server is not running on port 25 TCP it is not a public ... Manager - Computer Assurance Services BDO Chartered Accountants & ...
    (Security-Basics)
  • Re: SRV RRs support in Internet Explorer?
    ... The port number could be implicit (i.e. ... At any point in time, a server could fail ... can't effectively LB or backup because NSs cache the records for the TTL ... I still don't see how SRV records would help backup or LB. ...
    (microsoft.public.win2000.dns)