I have a virtualized network running on a dedicated server. The host is 2012 R2 Datacenter edition running four virtualized 2012 R2 Datacenter clients. I decided to completely rebuild my network after making a few changes. I have the /30 IPv4 network running via a bridge, giving me four IPs instead of two (gateway plus a client). I also have IPv6 running, which is working flawlessly (native IPv6 to my home router).
I am able to add Windows 7, Windows 8, and Windows 8.1 clients without any issues. However, I receive an error stating the network path could not be found whenever I try to add the Windows 10 client. I have verified all settings, including authentication credentials, DNS settings, and IP settings. All devices have both IPv4 and IPv6. All clients were added from the same network using the same settings (DHCP with DNS set to the IPv4 and IPv6 servers).
I have uploaded a screenshot of the error I receive.
Most of what I have read states it is a DNS issue. I have added a Windows 8.1 client using these same exact settings from this network.
I receive an error stating the network path could not be found. Any ideas?
EDIT: Also, I noticed this error appears whether I use the proper domain credentials or not. How odd.
Code:
C:\Users\Matt>net view <IP>
System error 53 has occurred.
The network path was not found.
C:\Users\Matt>net view <hostname>
System error 53 has occurred.
The network path was not found.
C:\Users\Matt>ping <hostname>
Pinging control2.ds.rikairchy.net [IP] with 32 bytes of data:
Reply from IP: time=119ms
Reply from IP: time=120ms
Code:
C:\Users\Matt>net view
System error 1231 has occurred.
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
