Forum Discussion
19603 - VPN Client Doesn't Show Domain Prefix At Bottom Anymore?
Upgraded to 19608 last night, this problem still is present.
RedBeta
Are you still having this problem as well?
I noticed that it is also affecting RasPhone; if I use that to start a VPN connection, I still have to provide the full DNS name of a network machine in order to reach it (I.E. MachineName.DomainName instead of just MachineName).
Yes issue is still present in 19608 and I made sure that all the components of name resolution are proper.
I have veeam backups / remote desktop / WSD Samba file shares that all used to work with past builds, still work with non insider builds that require raw IPs or hosts file entries to work with the latest builds
This is troubling. I am almost certain then this problem is going to have a wide effect on particular types of DNS resolution when 20h1 goes live if this doesn't get fixed.
Have you been able to find any work arounds for this on the machine running the fast ring build?
Also on a side note - I tested this on the DNS server we have for my company and the DNS server isn't even receiving any requests from my 19608 machine when I try to access a resource by machine name. It's like the fast ring Windows is doing something weird and the request is bad and dropping before it can make it to the DNS server.