Hi all,

I have a site to site VPN setup between a remote office (3 XP Pro boxes) and HQ (SBS Server, 8 XP Pro).  I happen to be using Zywall 5's, but I believe this problem is unrelated to the VPN Hardware.

HQ's network is: 10.112.12.x  (SBS Server is 10.112.12.10)
Remote office network is: 10.112.14.x

The Zywall is handing out DHCP on the remote network - and is handing out DNS of 10.112.12.10.  The remote boxes can surf the web using the SBS DNS, but can't connect to companyweb or do /connectcomputer.  

For the solution to this issue, I have seen references to adding an IP route on the SBS box, but after an hour+ of googling and searching here and elsewhere - I'm asking for help on how to do that.  

I don't want to have each remote user (on the remote LAN) to have to use the software VPN connector as part of their daily workflow - I want them to be using a site to site VPN, so that they're not "remote users" but that they feel like they're on the network.  Also - I'd like the computers on the remote network to be accessible via RWW, and I'd like HQ to be able to print to the remote office - which also necessitates the site to site VPN.

Thanks much!

Aaron Booker

Don't know if this will help you with your problems (because we use hardware routers for our site-to-site vpn connection and the gateway to our remote offices isn't the SBS server, but a router), but to add a static route on the SBS server do the following:

 

On the SBS server go to "Start" and select "Run"

Typ "cmd" and hit the "ok" button.

 

In the cmd window typ the following:

route add 10.112.14.0 mask 255.255.255.0 10.112.12.10 -p

 

The syntax of this function is:

ROUTE [-f] [-p] [command [destination] [MASK netmask] [gateway] [METRIC metric]   [IF interface]

 

The -p is for making it permanent, without it the route will be deleted after a restart.

 

You can also typ "route" end hit enter to get an overview of the "route" function.

 

I don't know if it will work (no network specialist over here ), because I don't know if the ip-adress for the gateway is correct. You could experiment with the gateway adress using the internal NIc or external NIC of the SBS server (also with selecting the interfacecard).

Hi Aaron,

 

What error do you get when you try to run connectcomputer from the remote office? Please, post an ipconfig /all from the server, a workstation and a remote workstation. Open a command prompt by opening Start -> Run from the Start Menu and type cmd. From the command prompt type ipconfig /all >ip.txt. Attach this file to your answer.

Hi Aaron,

 

Properties of the Default Website, tab Directory Security, IP restrictions, add the remote subdomain.

Hi Aaron,

 

The remote workstation is missing the dns suffix though. Why don't you set them to dynamically grab an IP and DNS?

About IIS: have you added both subnets to the IP restrictions of the default website?

Marina,

 

What I did to solve the problem was add the WINS information in tcp/ip advanced, as well as change the default search domain...  Also I did add both subnets to the IP restrictions of the default website.  All problems got resolved then.

 

I think I found the solution to this issue on expertsexchange...

 

Aaron

Could you help me locate instructions for the configuration originally posted  above?

 

VPN connected and all pingable

Hi Brad,

 

That series of articles indeed describe the procedure where SBS is using 2 nics with ISA, so the remote DC needs to use RRAS for the vpn. If you have 1 nic in the server, you could create a hardware vpn tunnel between the two routers.