Re: Can VPN be tested from inside the network?

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

Leon Willard wrote:
Here are the results of my PC IPCONFIG /ALL with VPN connected to the office.
Please give me an assessment. I don't really know how to interpret these results.
Thanks, Leon


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mr Bear>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : lwcs-msi
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Adapter

Physical Address. . . . . . . . . : 00-0C-76-1A-4A-D7
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Wednesday, June 14, 2006 12:15:40 PM

Lease Expires . . . . . . . . . . : Thursday, June 15, 2006 12:15:40 PM

PPP adapter WTA VPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.120
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 192.168.1.120
DNS Servers . . . . . . . . . . . : 192.168.1.2


The PPP part looks right, on the assumption that the SBS LAN IP address
is 192.168.1.2. As Simon says, both the remote client and the SBS are
set to the same subnet. The IP routing software in the remote client
is sending packets for the SBS out of the LAN NIC instead of down the
VPN.

Presumably the default IP address for the router is 192.168.1.254 and
DHCP is in use. The simplest fix (at least for this issue) is to log
on to the router configuration page and change the router's IP address
to something on another subnet e.g. 192.168.10.1. You will immediately
lose contact with the router, and the safest way to recover it is to
reboot the PC. An ipconfig will then show the Ethernet adapter settings
to be similar but based on the 192.168.10.0 network instead.

If you expect VPN to be used by other people or from other locations,
it will be better to change the SBS end. Basically, there is a wizard
to change the server IP address, but depending on the network details
there may be other things to do. If the server uses two NICs, the IP
change wizard may be all there is to it. If it uses one, then the
router at that end will also need to be changed to the new subnet.
Change that first, then the SBS with the wizard, and then to be on
the safe side, re-run the CEICW, reboot the SBS and then reboot the
LAN workstations. If you leave all the workstations shut down before
doing this, most minor issues should be avoided.

From what you've said, VPN probably should work OK after either of
these processes. Ideally do both, to different subnets, as one day
there may be two VPNs open and their local subnets must also be
different from each other.
.

Relevant Pages

  • Re: VPN and Routing in one box
    ... Any suggestions for a simple router that will do this? ... Packets originate in Subnet 1, ... The VPN is the first hop. ... should be sent through the VPN gateway at 192.168.2.0 and you ...
    (comp.dcom.vpn)
  • Re: VPN drops
    ... we can try to set up several VPN connections ... hardware (DSL router) limitation. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN and Routing in one box
    ... Packets originate in Subnet 1, ... The VPN is the first hop. ... When packets arrive via the VPN at Subnet 2, they have to be routed to a particular router / IP address on Subnet 2, which is the next hop in order to be futher routed to Subnet 3. ...
    (comp.dcom.vpn)
  • Re: 2 NIC SBS2003R2 LAN/WAN Firewall Router Connection Failure
    ... I have to admit to a preference for VMWare Server which can only be ... I've asked the other SBS MVP's to comment on the current status of SBS ... I connected directly to the router and changed its LAN side subnet ...
    (microsoft.public.windows.server.sbs)
  • Re: 2 NIC SBS2003R2 LAN/WAN Firewall Router Connection Failure
    ... but I guess that's another topic for internet searching. ... I've asked the other SBS MVP's to comment on the current status of SBS ... I connected directly to the router and changed its LAN side subnet mask ...
    (microsoft.public.windows.server.sbs)