troubleshooting Question

Possible DNS Resolution Issues on SBS 2003 Server and no luck browsing shares over VPN

Avatar of philodendrin
philodendrin asked on
30 Comments1 Solution1056 ViewsLast Modified:
We've got a SBS 2003 box that will not resolve http://localhost/exchange & http://servername/exchange or http://localhost/remote & http://servername/remote. Same results for https://

Client PCs connected to the server can resolve to http://servername/exchange and any other of the Web pages hosted on the SBS. We have split DNS configured so that clients can also resolve to the FQDN on the internal LAN. So, resolves internally for the client PCs... but will not resolve on the server.    

The problem is isolated to the server itself. When we're at the console we cannot resolve http://localhost/exchange. Putting in the complete domain name doesn't make any difference. The internal domain is setup with a .com and not a .local. When we try http://servername/exchange ...we get "Internet Explorer cannot display the Webpage".

Additionally, we can VPN to this server remotely and remote desktop over VPN and also ping IP addresses while on VPN but absolutely  cannot browse shares while on VPN by using the UNC. This seems related to the above issues, but we're not having any luck figuring out the common denominator between the two problems.

The error we get over VPN when we try to browse shares via UNC is "\\servername is not available. You might not have permission to view this network resource. Access is denied." We're authenticating over VPN as administrators with full access rights. The VPN connection is working fine... GRE is enabled on the firewall... it's not a connection issue. We're using the VPN client built into the server to serve VPN... not a thrid party firewall product. The firewall we're using is a Zyxel and it just passes the traffic over port 1723 to the server.

Could the problem be in the DNS Lookup Zones? We've looked at the LMHosts file... which is clean. WINS is running without issue. By the way... we get exactly the same behavior when we try by IP address instead of server name or UNC.

We've run out of ideas... any help to put us back on track would be appreciated.

Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 30 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 30 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros