<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I hope someone can help. I have an issue whereby, when clients connect to the VPN, I cannot ping them or access them via their computer name. This means that when the helpdesk are trying to troubleshoot issues, they have to get end-users to find out their VPN IP address.<br />
<br />
I have just tested it with a new client (XP but most are Windows 7). I joined the client to the domain then disconnected it from the corporate network. I connected it to a broadband connection then connected to the VPN. I then tried to ping it by its name from my machine. When I do this I get:<br />
<br />
Reply from 10.132.1.185: Destination host unreachable.<br />
<br />
10.132.1.185 is my machine that I'm pinging it from so I'm a bit confused by that. So I then tried pinging from another internal server on our network, and it just times out.<br />
<br />
I did an NSLookup on the client and it is using our internal DNS server and resolving names correctly. I also checked the bindings and the VPN adaptor is at the top.<br />
<br />
Does anyone have any ideas how to resolve this?<br />
<br />
DCDiag /test:DNS checks out fine.<br />
<br />
Thanks.
</div>
</div>


Hi,

I hope someone can help. I have an issue whereby, when clients connect to the VPN, I cannot ping them or access them via their computer name. This means that when the helpdesk are trying to troubleshoot issues, they have to get end-users to find out their VPN IP address.

I have just tested it with a new client (XP but most are Windows 7). I joined the client to the domain then disconnected it from the corporate network. I connected it to a broadband connection then connected to the VPN. I then tried to ping it by its name from my machine. When I do this I get:

Reply from 10.132.1.185: Destination host unreachable.

10.132.1.185 is my machine that I'm pinging it from so I'm a bit confused by that. So I then tried pinging from another internal server on our network, and it just times out.

I did an NSLookup on the client and it is using our internal DNS server and resolving names correctly. I also checked the bindings and the VPN adaptor is at the top.

Does anyone have any ideas how to resolve this?

DCDiag /test:DNS checks out fine.

Thanks.

DNS issues with clients connected via AT&amp;T VPN

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

A virtual private network (VPN) is a network that uses a public telecommunication infrastructure, such as the Internet, to provide remote offices or travelling users access to a central organizational network securely. VPNs encapsulate data transfers using secure cryptographic methods and other security mechanisms to ensure that only authorized users can access the network and that the data cannot be intercepted.

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

DNS issues with clients connected via AT&amp;T VPN

DNS issues with clients connected via AT&T VPN