• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7221
  • Last Modified:

windows cannot access \\SERVERNAME (Error Code: 0x80070035 - The network path was not found.)

Error Code: 0x80070035
The network path was not found.

Windows 2008 Server Standard R2

\\server.ip.addr works
\\server.name.fqdn works
\\server fails  (even though we hardcode the server IP in the local host file.)

1. I can ping server why server.ip.addr is in local host file.

C:\Users\hades666>ping serverops
Pinging serverops [] with 32 bytes of data:
Reply from bytes=32 time<1ms TTL=127
Reply from bytes=32 time<1ms TTL=127
Reply from bytes=32 time<1ms TTL=127
Reply from bytes=32 time<1ms TTL=127

Ping statistics for
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

2. I can open network share to \\serverops.domain.com

3. I can open network share to \\serverops.ip.addr

4. We have tried deleting profile, thinking corruption with no result.

5. we have flushdns cache ipconfig /flushdns

6. We have flush Netbios Cache ntbstat -R

The only fix we have right now is to reboot the server.

Any ideas?
Brad Howe
Brad Howe
  • 4
2 Solutions
Did you setup reverse lookup?
Brad HoweDevOps ManagerAuthor Commented:
Yes, As well all other servers in the environment are not experiecing this issue.  

We feel it is a problem with the snapapi connection that ACRONIS makes for is disk backups but it is strange that is only breaks the \\server name connection.

Test after each one of these:

1. Make sure NetBios over TCP/IP is enabled in the network properties
2. Restart TCP/IP Netbios Helper
3. Make sure workstation service is running
4. Apply the following hotfixes:

2444558 for Mrxsmb10.sys
982860 for Mrxsmb20.sys and Mrxsmb.sys
2383928 for Win32k.sys
2398906 - kernel files


Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Brad HoweDevOps ManagerAuthor Commented:
Now that is interesting. I'll give the hotfix a go and let you know.
Thanks a bunch,
Brad HoweDevOps ManagerAuthor Commented:
Ended up removing the entire app and upgrading. Works now. Thanks for the comment however.
- Hades666
Brad HoweDevOps ManagerAuthor Commented:
The answer was to upgrade but the hotfixes are good to know.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now