I can only assume so. The DHCP Server is a fresh install of the Win2k3 SBS server. It lives in a rack, with no one connected to it. :-(
I have no reason to believe that it is not working properly, though.
Main Topics
Browse All TopicsAfter connecting to a Server 2003 VPN, packets are not getting routed out the remote gateway because the remote gateway is not being assigned to the VPN client (MS XP VPN Client).
How do I force Routing and Remote Access to assign the gateway to the remote client?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
How did you create the VPN? You should use the SBS "Configure remote Access" wizard, not the RRAS wizard, and then download the SBS connection manager client for the users. See:
http://www.lan-2-wan.com/S
This will force all traffic through the VPN, block local traffic, configure permissions, and server routing.
However, there are only two configurations for the VPN client
1) IPv4 Address. . . . . . . . . . . : 192.168.100.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0 (sometimes displays as blank)
2) IPv4 Address. . . . . . . . . . . : 192.168.100.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 192.168.100.102 (Note: same as Virtual IP)
Option 1 occurs when "use remote default gateway" is unchecked in the VPN client and allows local and remote(VPN) connections simultaneously, known as split-tunneling.
Option 2 is with "use remote default gateway" checked and forces all traffic through the VPN tunnel.
You cannot use 192.168.100.1 (assuming remote/RRAS site) as the default gateway as it is not the "next hop". If you are trying to forward the traffic out through the RRAS site's default gateway, make sure "LAN routing" is enabled in the RRAS configuartion.
@RobWill:
You are correct. I should have put .102 as it would be the next hop.
That being said, I did use the RAC Wizard in SBS 2003 to configure it, and the default gateway displaying blank was happening.
I know that I am getting a proper IP address, because we can connect to exchange, nslookup shows that I am using the remote SBS box as the DNS server, and queries come through just fine.
I will get with the client machine to check the status of the "Use Remote Default Gateway" checkbox.
Could be all sorts of reasons but one known issue:
http://support.microsoft.c
Do you have SP1 installed? If so was it installed correctly (5 or 7 steps)? This is the most common cause of your problem.
There are very specific instructions for installing SP1 on SBS. There are actually 5 installs (7 if you have SBS premium). See the following link for details and pitfalls.
Windows Server 2003 SP1
Exchange Server 2003 SP1
Windows SharePoint Services SP1
Windows Small Business Server 2003 Update KB891193 for Windows XP Service Pack 2
Windows Small Business Server 2003 SP1
If you have SBS premium then you will also need:
ISA 2004 SP1
SQL 2000 SP4
The following article outlines this very nicely and also lists potential problems and some hardware vendor specific issues you can run into:
http://www.smallbizserver.
Do not attempt to install SP2 until the above is complete.
You may want to review some of the known issues before proceeding with SP2:
http://www.lan-2-wan.com/2
Discussion reporting log files similar to yours:
http://www.winserverhelp.c
Scary :-)
Lots of others have done it without a problems, but I hate doing so with SBS. Sounds like you are aware SBS can often "throw you for a loop".
If the Configure remote access wizard is your only problem I wouldn't go to the trouble. You can configure the VPN manually without a problem, you just have to make sure all options are properly configured on client and server.
For server see:
http://www.lan-2-wan.com/v
For client:
http://www.lan-2-wan.com/v
Name resolution:
http://msmvps.com/blogs/ro
Yes. I agree that SBS is both scary and loopy.
The Configure Remote Access wiard is not the only problem. In fact, I really don't care, because for years I have always configured VPN's manually.
The only problem I need fixed is the original gateway routing issue in this post. Other than that, everything works fine.
What's the best path to fixing this box?
Do you want to change the gateway or is the issue the client is not accessing internet through the tunnel?
If the former you can use a route add, if nothing else works, to change the default gateway:
route add 0.0.0.0 mask 0.0.0.0 192.168.100.102
If the connection to the server is OK but the traffic is not forwarded then make sure LAN routing is enabled in the RRAS console.
Business Accounts
Answer for Membership
by: greenhacksPosted on 2009-09-22 at 07:59:47ID: 25393579
Can you check the DHCP if it is properly assigning gateway to dhcp clients?