Strange network share problem

Question

Hi,

I have a few Windows 2016 servers in a same domain. The network shares are on a server (Server1, static IP 192.168.1.2), the servers try to access the network shares are one (Server2, Static IP 192.168.100.2) and another (Server3, Static IP192.168.100.3). Server 2 can access the network shares by IP \192.168.1.2 and by name \Server1 without issues. Server 3 only can access the network shares by IP \192.168.1.2 but NOT by name \Server1.

Here is what I checked:

1. Server1, Server2 and Server3 can ping each other by IP and by name
2. Run nslookup can resolve name from one to another.
3. Network discovery and File and printer sharing are enabled on Server1, Server2 and Server3
4. NetBIOS setting is default on Server1, Server2 and Server3
5. No Windows/Web credentials are saved on Server1, Server2 or Server3
6. Server1 and Server3 has been rebooted for a few times.
7. TCP port 445 is opened
8. From Server3 - run \Server1 I got this message [Windows cannot access \Server1. Error code: 0x8004005 Unspecified error]
9. From Server3 - run net view Server1 I got this message [System Error 53 has occurred. The network path was not found]
10. From Server3 - run \192.168.1.2 I got all network shares without issues.
11. From Server3 - run net view 192.168.1.2 I got all network shares without issues.

No more ideas what else I can do.. really need your help now. Thanks in advance!

Answer 1

I'd check the domain controller and problem members all have the static ip address of DC listed for DNS and no others such as router or public DNS.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

@Anonymous ,

The DNS IP address is the local DNS server (Domain Controller)'s IP for all servers.

Answer 3

Hello HB-6254

In this case I would recommend to check the DNS suffixes of the connection both in Server3 and the others, as they may be registered differently.

You can also try to flush the DNS and re-register with the next commands through Administrator command prompt:

ipconfig /flushdns
ipconfig /registerdns

Additionally, since you have covered most of the troubleshooting with no luck, I can recommend the workaround of adding a static route in the HOSTS file of Server3, to directly point the IPs to FQDNs of Server1 and Server2
https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings-winpc/how-to-edit-host-file-in-windows-10/7696f204-2aaf-4111-913b-09d6917f7f3d

---

--If the reply is helpful, please Upvote and Accept as answer--

Answer 4

Hi @H B

The error suggests that you have name resolution issues on server3. You can use this test option to confirm the status of the share and which element in the UNC path is not working. I would test the UNC path with both the short name i.e. \server3\share and the FQDN i.e. \server3.domain\share, and see what results you get.

Gary.