Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 526
  • Last Modified:

VPN clients not able to resolve DNS names of local objects

Hi Team

We have an issue on a client site where users could VPN to the local server but would not be able to gain access to resources.

The IP addresses given to users were in the 169.x.x.x range so that it appeared that RAS cannot pulled addresses from the DHCP range. We resolved this issue by creating a static address pull for the VPN users to access.

Now the users can login and access resources but only if they are accessed using IP values rather than local hostnames.

Looking for direction on now to enable users to access with hostname ?

Thanks
0
optimus_nz
Asked:
optimus_nz
1 Solution
 
piyushranusriCommented:
VPN clients will not be able to resolve DNS host names on the internal network if they are not assigned a DNS server address by the ISA Server firewall/VPN server. In most cases, the VPN client already has a DNS server address assigned to it. However, that DNS server address does not resolve names on the corporate network because that DNS server is intended to resolve names on the network the VPN client computer is attached to before connecting to the ISA firewall/VPN server, or to resolve only Internet host names.
what is vpn server version ??

didi you review RAS configuration ?

The Routing and Remote Access service is configured to permit incoming connections.

did this happen suddenly or from starting its like that ?

hope tthis link will assist you to understand the cause..


please share the output
0
 
Manjunath SulladTechnical ConsultantCommented:
Try adding DNS suffix at client side.

On Local Area Network Icon, Properties,click Internet Protocol Version 4 (TCP/IPv4), click Properties.

Click Advanced, and then click the DNS tab.

Specify the DNS suffix for the connection, Ok.

Now try connecting VPN and check.

Refer below URL for further troubleshooting, based on error messages.

http://technet.microsoft.com/en-us/library/cc772616(WS.10).aspx#BKMK_5
0
 
vivigattCommented:
If your VPN clients needs to be able to connect to local devices, they must "know" local name servers (DNS and potentially WINS).
This would be easier if the IP config was set by DHCP, but I think I remember that you can set it even with a "static" pool.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
optimus_nzAuthor Commented:
Hey Guys

The server is Windows server 2008, no ISA but there is a Mako modem/firewall which is the outbound connection for the site.

I have gone through and checked the settings for another site that has exactly the same setup (static IP pool for VPN and same model modem/firewall) and it is able to resolve hostnames local

Help ?
0
 
vivigattCommented:
HAve you checked DNS and WINS settings ?
0
 
optimus_nzAuthor Commented:
Hi Team

We were not able to resolve in a timely fashion so we change the login scripts to reference IP rather than hostname for drive mappings.

We were not able to identify the cause but the VPN was not able to provide DHCP address to users so assume this is somehow related to users not being able to resolve DNS/Hostname either?

In anycase we would like to close the ticket
0
 
optimus_nzAuthor Commented:
Nothing suggested was able to resolve the issue. Would like to close thread
0

Featured Post

New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now