On a Windows Server 2008 R2 Domain Controller we can no longer connect to it using a UNC path from another server or desktop which is causing problems for people printing on the printers shared on that server.
The error is "The specified network name is no longer available "
This DC is also the FSMO role holder, DHCP, RRAS and Veeam Proxy Server, no other network related issues seem to be effected at the moment.
Here's what we know/have tried:
1) The server can connect to its own UNC path and other UNC paths.
2) Other devices CAN connect to the UNC path using its static IP address and they can ping the server name successfully indicating DNS is working
3) The NIC is using domain profile (not private or public)
4) No configuration changes have taken place
5) Nothing in the event logs indicate a serious issue
6) Workstation, Server and Netlogon services along with all other Automatic services are started on the problem server
7) We've tried a reboot of the server
8) We have disabled the Windows Firewall and AV to test
Temporarily we are adding the printers for the user connecting to the IP address
There are loads of links out there but there are various reasons why this could be the case?
Thanks for any advice