Community Record
8
Posts
3
Kudos
1
Solution
Badges
Dec 19 2019
5:03 AM
3 Kudos
Ulitmately the issue was a datacenter routing problem. Our impacted clients could not reach a Network Location Service and tried to activate DirectAccess (IPv6) over the site-to-site VPN. This changes the internal routing tables on the affected computers. We did not see this, because IPv6 was not in the default PacketDumps..... Added the correct routes and problem solved. Thanks everyone for helping out!
... View more
Dec 16 2019
8:51 AM
It's a new deployment, strange thing is that other domains laptops are connecting just fine. On the test laptop disabling/enabling IPv6 makes no difference. Strange thing is that using the MX'es PacketTrace, when opening it in WireShark we see 4 DNS queries (on the 4 least interesting DNS domain names) and the 2 main ones, nu query is sent out on the wire..... Within the datacenter, or - for that matter - on all of our MPLS connected locations the same machine's are working fine. That is what puzzles me the most....
... View more
Dec 16 2019
6:53 AM
Unfortunately, my non-working laptop is joined to the non working domain, resulting in all kinds of issues. We are looking into the DNS stuff at the moment. For the record, it is a site-to-site VPN (and not a client VPN).
... View more
Dec 15 2019
10:39 AM
Result is still the same.... ping servername.company.lan results in: Ping request could not find host servername.company.lan.. Please check the name and try again. The weird thing is we have 5 or 6 dns suffixes configured in our clients. Of three of those the hostname resolves in ping, the other 2 do not..... Wireshark traces show only DNS requests of the last three DNS domain names, the first two (unfortunatly the most important) do not work.... All DNS sufixes resolve correctly using nslookup.
... View more
Dec 15 2019
6:15 AM
Windows 10 clients connected to a site-to-site VPN into our datacenter are experiencing DNS issues. We cannot ping using hostname or FQDN (all our AD domain suffixes are added to the clients search list using GPO). However nslookup resolves the correct hostname. On our MPLS network everything is working fine, so I suspect somethiong wrong with DNS in the AutoVPN. Ping using IP address works as wel to all our routed subnets behind the datacenter MX. Traceroutes on the clients to all destinations show the correct route. So there is L3 connectivity, but all DNS related stuff (logging in to AD, mapping network drives, loading GPO's, etc.) fails. I am a bit stuck on this one......
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 7605 | Dec 19 2019 5:03 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 3 | 7605 |
