Re: Still not able to connect

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 01/17/05 

Date: Mon, 17 Jan 2005 13:53:05 -0500

Gkeep wrote:
> Al and Robin, Thank you.
> I follow the directions and still the problem persists.
> Within my office network I am able to access all computers(within)
> through remote desktop by inserting the correct IP addresses.
> Ports 3389 in all computers are listening.
> Doing the same steps, checking the same options, with all 3389
> listening, from home I am not able to connect to the office

What host are you trying to connect to from home? You have to use the
network's public IP address(es) that are forwarded to the private ones,
presuming NAT as I hope you're using - if you have only one public IP, you
need to configure each computer to listen on a different port, as they can't
all answer on 3389. And each workstation needs a static private IP (or a
DHCP reservation) so that it never changes.

> and I
> just tried from the office I am not able to connect to home. I am
> taking exactly the same steps.

Since you haven't quoted any of the original text in this message, I don't
know what you've tried. However, the same applies for your home network.

EDITED BEFORE SENDING: I just found your original post, which is quite
recent and has current activity in it. Please keep all replies in the same
thread so everyone can keep track.

> After trying RD in the office and
> seeing how it works, I am salivating to the possibility of working
> nights from home, now that tax time is here. I am an accountant.
> Another piece of information!

> In the office where RD is working within the network computers I am
> not able to connect to the same computers through VPN! Is this
> telling me my internet connection is not configured properly?????? Is
> this the problem???

Not sure what you're trying to connect to in the office via VPN. What's
handling VPN there?
If you do get VPN working, you can just use the private IP address of the
workstation you want to connect to, instead of the public one/multiple
ports.

Relevant Pages

  • Re: SITE-To-SITE VPN using Windows Server 2003 Standard
    ... Why are you surprised that VPN expects that you use private IPs? ... For site to site VPN to work there must be a connection between the two sites to carry the encrypted and encapsulated data. ... Each router now has a static route to the "other" site through the VPN link. ...
    (microsoft.public.windows.server.networking)
  • Re: SITE-To-SITE VPN using Windows Server 2003 Standard
    ... Its quite surprising to read that SITE-To-SITE VPN will work only when both ... we select that and leave private interface intact. ... how can a calling router detect answering when both are using PRIVATE ... SERVERS BE IN WORKGROUP MODEL TO CONFIGURE SITE-TO-SITE VPN? ...
    (microsoft.public.windows.server.networking)
  • specify an ip to use for outgoing traffic on a multi ip machine
    ... each having a local lan privately addressed and a linux internet gateway. ... A pptp vpn is set up between the two gateways. ... Routing is set up on both sites so that traffic to public addresses is nat'ed and sent directly on internet, and traffic to private adresses is sent over the vpn. ...
    (Fedora)
  • Re: VPN client address range question
    ... The VPN client address range should never be the same as the Internal ... Use a private range that is not duplicated in any network seen by TMG. ...
    (microsoft.public.isa.vpn)
  • Cant login multiple computers from home...
    ... I have our office network set up so that users can login and work from home ... via VPN. ... There are no problems and many users login simultaneously. ... connect any of my other PC's unless I disconnect the office workstation first. ...
    (microsoft.public.win2000.ras_routing)