Given that you have name resolution, and that you can ping the webserver on the 172.16.x.x subnet from the 172.17.x.x subnet, I don't believe this is a DNS issue at all. Also, since pings (and likely trace routes) are successful, routing is correctly set up. That leads to the conclusion that it's a rule base or permission issue for the VPN. Your rule set may allow pings but not http, for example. Check the VPN and/or firewall rules.
From: Bob Hartung [mailto:[email protected]] Sent: Tuesday, March 15, 2011 10:19 AM To: NT System Admin Issues Subject: DNS Issue I have two locations connected via VPN. The main location LAN is 172.16.x.x and the remote location is 172.17.x.x. I'd like users on the 172.17.x.x end to access a webserver on the 172.16.x.x end but it doesn't work and I'm not sure why. The users at the 172.17.x.x end have their Win2003 server as their DNS server. I can ping both the webserver's name and IP address from the 172.17.x.x PCs without problem. The webserver's name resolves to the IP address. All our servers and users are members of a single domain, just on different subnets. What am I missing? ---------------------- Bob Hartung Wisco Industries, Inc. 736 Janesville St. Oregon, WI 53575 Tel: (608) 835-3106 x215 Fax: (608) 835-7399 e-mail: bhartung(at)wiscoind.com ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
