Re: Allowing multiple users to connect to multiple desktops

Tech-Archive recommends: Fix windows errors by optimizing your registry

The downside with the XP PPTP VPN server is that you can only have one
incoming connection at a time. That's why I like either the SSH or SSL-VPN
solution if your not going to run a W2003 VPN server.

In the case of SSH you only need TCP Port 22 open. All incoming connections
go through that and each user can access her/his PC via the SSH tunnel. The
same with the SSL-VPN solution. In that case you only need TCP Port 443 open
to the server PC.

You would not need TCP Port 3389 open if you use either SSH, the SSL-VPN or
a W2003 VPN solution. All traffic goes through the tunnel...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"FWS" <FWS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CEC73D21-C385-4C02-A69F-5459438F55AF@xxxxxxxxxxxxxxxx
> Also, since we aren't running a server, can we create the VPN without any
> additional equipment/software? Just create the connection like the second
> link shows? Once you establish the VPN connection, you then create the
> Remote Desktop connection? Using the local IP address since you're
> alaready
> connected? Does using the VPN connection still require forwarding port
> 3389?
>
> Thanks for your help.
>
> FWS
>
> "Sooner Al [MVP]" wrote:
>
>> There are various strategies available...Not in any particular order...
>>
>> * You could setup a VPN and tunnel all of your RDP requests through that.
>>
>> http://www.microsoft.com/windowsserver2003/technologies/networking/vpn/default.mspx
>> http://www.onecomputerguy.com/networking/xp_vpn_server.htm
>> http://www.onecomputerguy.com/networking/xp_vpn.htm
>>
>> Do you run any type of server on your network now?
>>
>> An alternative to the above is to use a VPN end-point router and have
>> your
>> remote clients connect to that. Here are some examples of those...
>>
>> http://www.zyxel.com/product/category1.php?indexcate1=1085450410&indexFlagvalue=1021873683
>> http://www.linksys.com/servlet/Satellite?childpagename=US%2FLayout&packedargs=c%3DL_Product_C1%26cid%3D1117775454480&pagename=Linksys%2FCommon%2FVisitorWrapper
>>
>> * Open multiple ports on the firewall to the different machines...
>>
>> http://theillustratednetwork.mvps.org/RemoteDesktop/Multiple_PC_RD.html
>>
>> * Use a SSH tunnel to access multiple machines through one hole in the
>> firewall, ie. TCP Port 22...I use this to access my home LAN...In my case
>> I
>> use a 2048-bit RSA private/public key pair for authentication...
>>
>> http://sshwindows.sourceforge.net/
>> http://www.bitvise.com/tunnelier.html
>>
>> How I did that with PuTTY...
>>
>> http://theillustratednetwork.mvps.org/RemoteDesktop/SSH-RDP-VNC/RemoteDesktopVNCandSSH.html
>>
>> * Use this SSL-VPN solution...This is very easy to setup and use...
>>
>> http://3sp.com/showSslExplorer.do
>> http://www.broadbandreports.com/forum/remark,13775231
>>
>> --
>>
>> Al Jarvi (MS-MVP Windows Networking)
>>
>> Please post *ALL* questions and replies to the news group for the mutual
>> benefit of all of us...
>> The MS-MVP Program - http://mvp.support.microsoft.com
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights...
>>
>>
>> "FWS" <FWS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:1EB5BC0C-CAE8-420A-8B00-BECDA6043278@xxxxxxxxxxxxxxxx
>> >I configured and got remote access to work for connecting myself to my
>> >office
>> > computer. I conigured our router to forward port 3389 to my office's
>> > internal IP address. Question being, how do I let others at my office
>> > do
>> > the same. Do I forward port 3389 to their IP address at the same time?
>> > That
>> > doesn't seem right to me. Or should I forward different port numbers
>> > to
>> > their respective IP's? If so, what port numbers? Does it make a
>> > difference
>> > which ports? Pleaes advise.
>>
>>
>>


.

Relevant Pages

  • Re: Setting up Windows VPN
    ... successfully use VPN connection within the home network. ... >> Thanks if anyone can help me to set up a home VPN network trough Internet ... The desktop is connected to LAN port, ...
    (microsoft.public.isa.vpn)
  • Re: VPN Client
    ... Thanks for the help on losing the remote connection when you connect to VPN. ... Regarding the router port forward issue, you should point the port 1723 to ...
    (microsoft.public.windows.server.sbs)
  • UPDATE: Re: Question regarding SSH via Lantronix SCS100
    ... to do SSH and to authenticate the SSH connection with a local ... unexpectedly closed connection'. ... CONSOLE or AUX port on the router, or does it matter, and what ...
    (comp.dcom.sys.cisco)
  • Re: SSH options re: NAT
    ... No, SSH is two-fold, a call to it on the client side results in a call ... port, meaning that any connections that come into that port are answered ... programming practice for daemons) Once the connection is established, ... don't want to execute a command on the remote side and you use -N. ...
    (comp.security.ssh)
  • Re: VPN woes
    ... >up as a VPN server here in the office, using my DSL broadband connection. ... >a different DSL connection that also uses a Belkin 54g wireless router. ... for a PPTP VPN you need not only port 1723 but protocol 47. ...
    (microsoft.public.windows.server.sbs)