Re: Connect to Small Business Server VPN

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 ID 5807 / Netlogon
    ... The IPs that appearsin the netlogon.log file are IPs from remote VPN ... clients and also IPs from another different Windows domains in which we ... What I have done by now is to simply create subnets for the "unclassified" ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 5807 / Netlogon
    ... You don't have to define a seperate site but you should have subnets defined ... for the sites that will have clients authenticating to your domain. ... your clients to authenticate to. ... The IPs that appearsin the netlogon.log file are IPs from remote VPN ...
    (microsoft.public.windows.server.active_directory)
  • Event ID 5807 / Netlogon
    ... The IPs that appearsin the netlogon.log file are IPs from remote VPN clients ... What I have done by now is to simply create subnets for the "unclassified" ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 5807 / Netlogon
    ... The IPs that appearsin the netlogon.log file are IPs from remote VPN ... clients and also IPs from another different Windows domains in which we ... What I have done by now is to simply create subnets for the "unclassified" ...
    (microsoft.public.windows.server.active_directory)
  • Re: Virtual LAN Problem
    ... > connectivity with the remote LAN and from the remote LAN. ... It collapsed after trying to allow it to have a remote DNS address ... Confirm a decent tunnel by pinging the remote site internal clients. ... > But I had full access to the files shares on the SBS box! ...
    (microsoft.public.windows.server.sbs)