Multiple RD sessions through a router
Steve Aber
a specific host PC on a LAN where the client connects via
a linksys cable modem and router. Is it possible to have
two or more simultaneous RD sessions running on this LAN
at two different host PCs from two or more external
connections?
To make the single session work I forward the following
router ports:
Forwarding
----------
Service Port
Range Protocol IP address
--------- -------- -------------
3389~3389 Both 192.168.1.102
80~80 Both 192.168.1.102
Bill Sanderson
If you are using the Remote Desktop Connection executable at the client end,
you can achieve this by changing the port used by RD.
If you've loaded UPnP capable firmware into the Linksys router, you can do
this in the router. Hit the UPnP forwarding button on the forwarding tab.
Example:
RDPeh ext port 3390, tcp int port 3389, ipaddress of machine EH
RDPga ext port 3389, tcp int port 3389, ipaddress of machine GA
"Steve Aber" <st...@canyonhouse.com> wrote in message
news:140f01c2335d$0a59d630$2ae2...@phx.gbl...
Michael Chrisco
I have this but it looks like it does the same thing as the regular
forwarding
Also, how do you change the client port for RD?
Thanks,
Michael
"Bill Sanderson" <bill_NoSpa...@msn.com> wrote in message
news:uEWuLq2MCHA.1888@tkmsftngp10...
Jeffrey Randow (MVP)
resources much easier (haven't been able to prove that, yet). For
instance, should you want to request remote assistance from a user on
the Internet. If you have a UPNP-compliant gateway, creating the
request should cause the router to automatically forward TCP Port 3389
to allow the RA session to take place (theoretically) without
requiring any other user interaction.
If Barb Bowman is lurking around here anywhere, perhaps she can post
more information on it (she is the wireless and UPNP guru).
See below for an overview of UPNP
Jeffrey Randow
Windows Client MVP - Remote Networking & Security
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
.NET Server Community -
http://www.microsoft.com/windows.netserver/community
wi...@longhornconsulting.com
Visit the XP Remote Networking Wiki
http://www.longhornconsulting.com/xpwiki
Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....
From the UPNP.ORG Website:
The Universal Plug and Play architecture offers pervasive peer-to-peer
network connectivity of PCs of all form factors, intelligent
appliances, and wireless devices. The UPnP architecture is a
distributed, open networking architecture that leverages TCP/IP and
the Web to enable seamless proximity networking in addition to control
and data transfer among networked devices in the home, office, and
everywhere in between.
What is universal about UPnP technology?
Media and device independence. UPnP technology can run on any medium
including phone line, power line, Ethernet, RF, and 1394.
Platform independence. Vendors use any operating system and any
programming language to build UPnP products.
Internet-based technologies. UPnP technology is built upon IP, TCP,
UDP, HTTP, and XML, among others.
UI Control. UPnP architecture enables vendor control over device user
interface and interaction using the browser.
Programmatic control. UPnP architecture also enables conventional
application programmatic control.
Common base protocols. Vendors agree on base protocol sets on a
per-device basis.
Extendable. Each UPnP product can have value-added services layered on
top of the basic device architecture by the individual manufacturers.
UPnP technology is broad in scope in that it targets home networks,
proximity networks, and networks in small businesses and commercial
buildings. It enables data communication between any two devices under
the command of any control device on the network. UPnP technology is
independent of any particular operating system, programming language,
or physical medium.
The UPnP architecture supports zero-configuration networking and
automatic discovery whereby a device can dynamically join a network,
obtain an IP address, announce its name, convey its capabilities upon
request, and learn about the presence and capabilities of other
devices. DHCP and DNS servers are optional and are only used if they
are available on the network. A device can leave a network smoothly
and automatically without leaving any unwanted state information
behind.
Like the creation of Internet standards, the UPnP initiative involves
a multi-vendor collaboration for establishing standard Device Control
Protocols (DCPs). Similar to Internet-based communication, these are
contracts based on wire protocols that are declarative, expressed in
XML, and communicated via HTTP.
Bill Sanderson
we are discussing, but:
In the case of the two UPnP implementations I have looked at: Microsoft's
ICF/ICS and Linksys' befsr11/befsr41, both implement the ability to specify
a different external and internal port in the forwarding dialogs.
So--instead of changing the RD listening port in the registry, you can, in
ICF or the Linksys forwarding dialogs, set a different external port and the
standard internal port for a given machine. This is very nice--it avoids
registry editing, allows you to continue to use standard ports within the
private lan, and allows access to multiple machines from the Internet.
http://support.microsoft.com/default.aspx?scid=kb;en-us;q306759
shows the hard way to do this!
"Michael Chrisco" <Michael...@Hotmail.com> wrote in message
news:u7GO1a3MCHA.2480@tkmsftngp12...
alex_k._angelopoulos_(mvp)
> It isn't immediately obvious from the concept what UPnP has to do with
what
> we are discussing, but:
>
> In the case of the two UPnP implementations I have looked at:
Microsoft's
> ICF/ICS and Linksys' befsr11/befsr41, both implement the ability to
specify
> a different external and internal port in the forwarding dialogs.
>
The el-cheapo befsr's support arbitrary port remapping????
Wow. Sell your Cisco stock.
Bill Sanderson
But then, look at their VPN router--$160 or so, able to manage 70 some IPSEC
VPN's--not for the average person, pretty much requires a static IP for the
router, but for branch offices of a small organization--pretty darn nice for
the $.
<Alex K. Angelopoulos (MVP)> wrote in message
news:#siPcp#MCHA.208@tkmsftngp12...
alex_k._angelopoulos_(mvp)
they did allow up to 8 ports, but would not change the internal port
number at all.
--
Please respond in the newsgroup so everyone may benefit.
http://www.bittnet.com/winremote
http://www.bittnet.com/scripting
"Bill Sanderson" <bill_NoSpa...@msn.com> wrote in message
news:#ceImV$MCHA.2472@tkmsftngp11...