Unable to map network drive, getting error "the mapped network drive cannot be created because the following error has occurred the specified network name no longer available"

Question

Hi, I'm unable to map network drive using hostname/IP address from Windows server 2019 after the server is joined to domain (it was working fine before domain join).

The DNS server here is Windows 2008R2. Private IP range of Server 2008 R2 and Server 2019 are different (both the servers are in different IP pool).

I have checked the possible solutions available in multiple sites,

1. SMB port is open and able to do telnet to 445.
2. Ping is working fine.
3. Turned on File and sharing options.
4. NSLOOKUP also gives proper domain server.
5. Folder permissions are also properly set.

Still getting error "the mapped network drive cannot be created because the following error has occurred, the specified network name no longer available"

What am I missing?

Please help.

Thank you.

Answer 1

Ok, well now I see there are two domain controllers. The other files are gone now but my recollection was I assumed the "homeserver01" was the domain controller and I now can see that wasn't correct.

Domain controller and all members must use the static ip address of DC listed for DNS and no others such as router or public DNS. Each domain controller must have at a minimum its own static IP address plus the loopback (127.0.0.1) listed for DNS and no others such as router or public DNS. After making corrections do an ipconfig /flushdns, ipconfig /registerdns, and restart the netlogon service.

There's a number of errors in the dcdiag but hopefully the corrections above will clear most of it up. If problems persist put up a new set of files to look at.

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

Answer 2

Hello there,

SMB protocol requires additional configuration to work on both the server and the client computers. On Windows, you'll need to open Administrative Tools to access Windows Features and make sure SMB 1.0/CIFS File Sharing Support is enabled.

The problem can be caused by your antivirus especially if you are using the Nod32. If your security application isn’t causing an issue then try to disable your real time network scanning. These 2 things have been known to cause this issue. So, try to disable both your antivirus as well as any network scanning and check if it resolves the issue.

Hope this resolves your Query !!

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

Answer 3

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on any domain controller)
ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)

Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

then put unzipped text files up on OneDrive and share a link.

Answer 4

Domain controller and all members must use the static ip address of DC listed for DNS and no others such as router or public DNS

So on Makromed1 remove the router address and add domain controller's address (192.168.1.20) listed for DNS, then do ipconfig /flushdns, ipconfig /registerdns

The dcdiag file is corrupt, might be it was copied before the script ran to completion.

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