Re: VPN Problem

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 10/02/04

  • Next message: Mustang: "Re: Remote Assistance, One Way Connect" 
    Date: Sat, 2 Oct 2004 17:53:13 -0400

    Roger wrote:
    > Hi,
    > I am trying to set up a VPN to connect to an office computer from a
    > home computer. The configuration is as follows:
    >
    > Home Network: Consists of a desktop and a laptop, both running XP
    > Home, cable broadband access and a wireless router. The laptop has a
    > wireless connection. The workgroup name is "Workgroup". The router's
    > firewall is disabled.

    Why? I'd leave it enabled....you can initiate a VPN connection behind a
    router with no inbound ports open at all. Of course, since you're using
    wireless, you also need to secure that - even 128-bit WEP is better than
    nothing. But I digress...
    >
    > Office Network: Consists of 4 desktops - 2 running ME, 1 XP home and
    > 1 XP Professional, DSL broadband access and all computers connected
    > via wired ethernet. The DSL modem cum access point is connected to a
    > ethernet switch as are all the computers. The workgroup name is again
    > "Workgroup". The firewall of the DSL modem cum access point is set to
    > allow PPTP connections to the computer with XP Professional.

    Meaning:
    TCP port 1723
    Protocol 47 ( GRE )
    ?

    >
    > I set up a "Incoming Connection" on the office computer with XP
    > Professional (say Computer B-the computer name is "Roger") and an
    > outgoing VPN connection from the home laptop (say Computer A-the
    > computer name is "Sam") to Computer B using the Internet IP address
    > (not the IP address of computer B assigned via DHCP) of the Office
    > modem cum access point.
    >
    > Case 1: With NIS 2004 disabled on computer B, the connection is
    > successful, but I cannot access resources on the office network from
    > computer A. I cannot even access the shareddocs folder on computer B.
    > Only my home network computers show up in windows explorer on
    > computer A. Note that the second computer (the desktop) in my home
    > network also has the name "Roger". In TCP/IP properties of the
    > incoming connection item on computer B, the "Allow callers to access
    > my LAN" is checked and "Assign TCP/IP addresses automatically using
    > DHCP" is selected.
    >
    > Case 2: With NIS 2004 enabled on computer B, the connection fails and
    > I get error #800.
    >
    > I will appreciate any help resolving the above problems. Note that
    > Remote Desktop connections and TCP/IP connection via PC Anywhere work
    > fine even with NIS 2004 enabled everywhere.
    >
    > Thanks.
    > Roger

    What did you open up in NIS for inbound ports?

    What IP networks are you on at home and at work? For VPN to work, you need
    to have two different networks - can't connect if you are using, for example
    say, 192.168.0.0 in both places.

    Presuming that isn't the issue, can you ping the LAN IP of the computer you
    want to connect to, once you're connected as in case#1 above?
    If so, but you can't ping by name, you'll need an LMHOSTS file to do name
    resolution. See
    http://support.microsoft.com/default.aspx?scid=kb;en-us;150800

    Again, I'm not an expert on PPTP as I usually use IPSec with a proprietary
    client through a firewall.

  • Next message: Mustang: "Re: Remote Assistance, One Way Connect"

    Relevant Pages

    • Re: OT By a mile in parts comments on Viet Nam
      ... check bank accouts etc etc whilst away but is safe to do so over wireless and using the hotel network.. ... you should regard your connection as insecure and use some ... form of encryption to protect your passwords and privacy. ... My recommendation would be to set up a VPN endpoint in the UK that you ...
      (uk.comp.sys.mac)
    • Re: OT By a mile in parts comments on Viet Nam
      ... compared with the risks already inherent in the average hotel network. ... you should regard your connection as insecure and use some ... form of encryption to protect your passwords and privacy. ... My recommendation would be to set up a VPN endpoint in the UK that you ...
      (uk.comp.sys.mac)
    • Re: Remote Client Configuration
      ... > remote computer to SBS 2003 domain via VPN connection after the remote ... > connection when user logon to the remote computer. ... I dont think that the Network Configuration website would work to connect to ... "The Small Business Server Network Configuration Wizard ...
      (microsoft.public.windows.server.sbs)
    • Re: VPN issues on SBS2003 with ISA 2004 installed
      ... I had to create a VPN connection using the network connection wizard on ... Based on our work above, it seems the problem in client side, so I suggest ...
      (microsoft.public.windows.server.sbs)
    • RE: VPNs - Firewalls and Security
      ... we turned off sysopt connection permit ipsec and then added the ... VPN connections. ... VPN's - Firewall's and Security ... You had configured that vpn users access internal network, ...
      (Security-Basics)