Re: Connect to Small Business Server VPN

Actually the subnet is correct on a VPN

can you got to a workstation that is connected by VPN and go to command prompt and run
IPCONFIG /all and post the results here

Please don't mask the addresses. These are "private" not routeable so it doesn't matter.

--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so all can take advantage
"TNGUYEN" <tommyboy_nguyen@xxxxxxxxxxx> wrote in message news:OqAjoI%23uGHA.3500@xxxxxxxxxxxxxxxxxxxxxxx
Cris,

Thanks for the response. The internal network is using 192.168.X.1. The remote clients are assigned IP address and gateways that are identical. The subnet is also wrong. For instance this is what a client will be assigned once connected via VPN:

IP Address. . . . . . . . . . . . : 192.168.X.10

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 192.168.X.10

DNS Servers . . . . . . . . . . . : 192.168.X.2

"Cris Hanna (SBS-MVP)" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:e9Klo09uGHA.4756@xxxxxxxxxxxxxxxxxxxxxxx
Is your internal SBS network using 192.168.0.X or 192.168.1.X?
I ask because most home users are going to all be on these same subnets when connecting remotely and this causes all kinds of browsing/connecting issues.

--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so all can take advantage
"TNGUYEN" <tommyboy_nguyen@xxxxxxxxxxx> wrote in message news:e9C2T88uGHA.4384@xxxxxxxxxxxxxxxxxxxxxxx
When using the Connection Manager packaged with SBS2003 to establish a VPN,
clients are assigned invalid subnets and gateway addresses. Clients are
then unable to access or ping computers on the internal network. I had this
working fine some time ago, but somewhere along the line it went haywire.
I've tried re-running the "Configure Remote Access" on the To Do List in
Server Management, but that did not resolve the issue. I've been
researching and I have made sure that the Router setting within the Scope
Options in DHCP are set to the server's internal IP address. Any help or
suggestions is much appreciated.

TNGUYEN

Relevant Pages

  • Re: Event 5807 and VPN Clients
    ... into a local subnet of any kind. ... we are currently migrating away from was Safenet Soft Remote, ... >> network via our hardware VPN. ... Those clients, therefore, have undefined ...
    (microsoft.public.win2000.active_directory)
  • Re: vpn configuration question
    ... Yes, we have tried using a static range vs. the dhcp, but the same problem ... Likewise, if I create a pool from 192.168.1.200-192.168.1.225, clients can ... Windows automatically assumes a class 'C' subnet on some internal level. ... > range for you VPN in there vs. using the DHCP. ...
    (microsoft.public.isa.vpn)
  • Re: Unable to see subnets
    ... The VPN server has 2 NIC's and only one of them was registered with the Wins ... > Are the remote clients domain members? ... >> '192.168.200' subnet and vice versa. ...
    (microsoft.public.win2000.ras_routing)
  • VPN - Outside and Inside using same subnet
    ... I can VPN from inside the network and connect, so the server appears to be ... One problem is that the clients (two different clients ... I've tried) both use the same internal 192.168.2.0 subnet, ...
    (microsoft.public.windows.server.sbs)
  • Inet over VPN dns problem
    ... Anyone know how to make it so that a person connecting ... Here's my ipconfig /all of the VPN ... clients on the LAN but the LAN clients have no problem ...
    (microsoft.public.windows.server.general)
Loading