Windows 8.1 cannot map to network drives

First off, this issue randomly happened out of nowhere. Nothing was changed on my system before this problem happened. I used to be able to access company server network drives no problem now I cannot.

I have seen other threads on here similar issues but not the same.

Below are some notes on my scenario and things I have done already to try and resolve it.

1. I can ping the server name and IP no problem, but cannot map it.

2. It is only local to my computer, my domain account can access them on other computers and our terminal server.

3. This same computer was an image of another windows 8.1 machine and that still runs no problem.

4. I have enabled netbios and network discovery.

5. Turned off windows firewall, even though I know that's not an issue because it was working before.

6. Anti-virus and other similar programs would not affect it.

7. Changed network connection ( different cable or cable connection somewhere else, priv wifi, etc)

8. I can RDP to the servers as well.

9. Windows updates have been run numerous times as well.

I don't know if there is any adapter or how virtual network drives work or are enabled, but if that exists maybe that's my issue?

I do have a very last resort scenario. I have a backup DR image of my system I could restore to if absolutely needed, but would very much like to not do that as it's about 3 months old and would take a while for me to configure things back to the way I have it now.

Please help!

September 11th, 2015 10:12am

If it is an image of another computer, pay attention to computer name not to be the same.

you may try some diagnostic software.

for example windows itself has a network diagnostic software and you may already ran that. "Complete Internet Repair" is a thirdparty diagnostic software which I recommends.

Free Windows Admin Tool Kit Click here and download it now
September 11th, 2015 10:51am

Thanks for your reply.

I forgot to mention afterwards that yes it is an image of another computer, but we set it up to be it's own separate entity. We took it off domain, re-named computer etc. It was working for nearly two months when it just stopped. 

I believe it's a setting somewhere that's causing my issue. Or something not running on startup/login. The log in script is still there that would auto map them for me,

I am actually restoring my old base image on another computer for a new user that will have my same AD user permissions etc so I will test it again to confirm mapping works on there. Obviously the computer name and stuff will be changed on this as well.

September 11th, 2015 3:14pm