SBS 2008 VPN DNS Issues

I'm currently running a SBS 2008 Premium server with Windows XP Pro SP3 clients. I've encountered issues with the Microsoft VPN client since upgrading to SBS 2008. My clients are able to connect, authenticate, and get DHCP settings correctly. If servers are referred to by \\servername.domain.local\share it works great but if only \\servername\share is entered the VPN'd machines are unable to resolve it. Is this inherint within the design of SBS 2008 or is there something I can adjust to provide the ability of resolving by just the servername?
Danstr1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AdoBeeboCommented:
This is a guess, but are your VPN clients going into a different subnet to the rest of the domain? Are they pulling down 192.168.1.1/24 IP addresses? This IP range is provided by Networking and Remote Access. I haven't peered into the defaults of SBS08 but I do know that the DHCP service provided by N&RA is limited compared to the full blown DHCP service that will be handing out IPs to internal clients.
Can you check that it is the SBS08 server providing DHCP services from its own DHCP service, or if it is the limited DHCP service that comes with Networking and Remote Access Role. Check to see if DHCP leases are being provided to a logged in VPN client from the main scope, and verify the DNS settings are correct within the scope.
You can certainly help your aim of single name resolution by setting up a GlobalNameZone which is populated with CNAME values. If the GNZ is included in the same DNS as is specified for clients in the DHCP scope they use you should find name resolution a little bit smarter.
Setup GNZ
From CMD:
dnscmd.exe ServerNameHere /config /enableglobalnamessupport 1
In DNS Management
Create a new Forward Lookup Zone called "GlobalNames", AD integrated, replicate forest-wide.
Populate this zone with CNAME values e.g.
"SBS08" = "SBS08.domain.local"
"Proxy" = "ISA06.domain.local"
etc
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Danstr1Author Commented:
The DHCP all checked out. DHCP was coming correctly from the server including the DNS settings. I proceeded to create the GlobalNameZone as you recommended. I am now able to connect to those machines I entered the CNAME values for. Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.