On Jan 12, 10:10 am, bxd... DeleteThis @shaw.ca wrote:
> On Jan 12, 1:28 am, bxd... DeleteThis @shaw.ca wrote:
>
>
>
>
>
> > On Jan 11, 8:24 pm, "Shenan Stanley" <newshel... DeleteThis @gmail.com> wrote:
>
> > > bxd... DeleteThis @shaw.ca wrote:
> > > > I have been searching for an answer to this question with very
> > > > little luck.
>
> > > > Basically I have been able to connect to ONE PC thru a router either
> > > > via TSWEB (requires IIS loaded and 2 ports forwarded 80 (or an
> > > > alternate) and 3389) or using RDP from an XP PRO PC (using port 3389
> > > > forwarded). The problem is I have several XP Pro machines that I
> > > > would like to connect to thru this Router.
>
> > > > There was some suggestion from a local IT person that I could
> > > > possibly forward ports like:
>
> > > > 52101 -> 3389 PC 1
> > > > 52102 -> 3389 PC 2
> > > > 52103 -> 3389 PC 3
> > > > etc.
>
> > > > However I haven't been able to figure out how to tell the RDP Client
> > > > that I want it to use an alternate port
>
> > > > There is apparently a registry key under Terminal Services that
> > > > marks 3389 as the TCP Port but I would rather not change this
> > > > setting. If this did work that would mean having to modify the
> > > > registry every time I needed to connect to a different pc
>
> > > > Is any of this possible?
>
> > > The client?
>
> > > Well - I cannot remember the web-based methodology - but can I ask why you
> > > are not just using the actual RDP client (6.0)? Then - in the address field
> > > for the remote computer - you could (in your case - because you decided to
> > > forward incoming requests on the router to port 52101 to 3389 on PC1) just
> > > type in ip.address.of.router:52101 and connect.
>
> > > --
> > > Shenan Stanley
> > > MS-MVP
> > > --
> > > How To Ask Questions The Smart Wayhttp://www.catb.org/~esr/faqs/smart-questions.html-Hidequoted text -
>
> > > - Show quoted text -
>
> > Yes the client
>
> > I downloaded the RDP 6.0 client just in case the version I had was
> > older (no help about in the RDP) ... <IP>:<port> is not working for
> > either version- Hide quoted text -
>
> > - Show quoted text -
>
> I found a section in Help for RDP that suggests this is possible ...
> so now wondering if perhaps there is a setting in Norton Securities
> 2k6 on the Host that is preventing this working via a different port- Hide quoted text -
>
> - Show quoted text -
OK found a solution ... I suspect the router was confusing all the
port 3389 traffic so I changed all of the PC's except one to use other
ports for Terminal Services. To do this I went into the registry and
changed the RDP portnumber to a unique new address then mapped that
address thru the router. then RDP can call that PC by using the <ip
address>:<port> ... This appears not to be an option if you want to
use TSWEB as TSWEB requires 2 Ports and the Active X driver for the
client doens't provide an option to redirect port 3389 that I am aware
of The IIS Default WEB port can be changed.
Hot
Bloated Email? DetachPipe for Outlook
Mac
Linux
Games
PDA
Mobile
FAQ
Search
Profile
Private Messages
Log in
Windows Forums
RSS