Solved Network path was not found 0x80070035

BertieS

New Member
Messages
5
Hi
I have a network of 10 windows 8.1 (pro) desktop computers - all identical PCs - all set up about 6 weeks ago.
All computers show on the network. I have one drive mounted on one computer, which is shared with all other computers. I have mapped this drive as I:
All has worked fine until today.
Today one of the computers "FB" has consistently come up with the following error:

0x80070035 The network path was not found.

It also shows An error occurred while reconnecting I: to \\servername\folder

MicrosoftWindowsNetwork: the local device name is already in use.
This connection has not been restored.

All other computers can connect fine.

This computer FB will potentially connect for a short time and then has the above errors. (prior to today it was totally fine).

I have tried resetting the network adapter, switching off firewall, flushing dns.

I have seen lots of similar errors in forums, but no-one seems to have a resolution other than reinstall windows.

Any ideas?
Thanks.
 
Check the power management tab of the adapter properties, it may be going to sleep and losing the address. Why not try connecting the drive to the router instead of one of the PC's... :cool:
 
Thank you DMHolt57 - I have tried changing the power management of the adapter properties this does not seem to make any difference.
Unfortunately I can not connect the drive to the router, as my router does not have USB connectivity. (I am also a bit concerned about security of USB drives connected directly to router, as I have read that this is not as secure as via the PC).

Thanks for trying though.
 
the best way to setup your network would be to assign (static IP addresses) to the 10 PC's on your network.. Right now (it appears away) that the router is assigning dynamic IP addresses to the PC's and the mapped network drive
 
Thank you both. The drive is not in power saver mode as far as I can tell.
I will try to set up a static ip network as the next option - I am hopeful that this may work. I will not be able to do this until Thursday, as I am not in the office now until then. I will post back then. As a workround for the misbehaving computer I have set up a VPN which connects fine to the shared drive! Hence why I think it is something more to do with the misbehaving computer rather than the shared drive (all the others manage to stay connected OK).
Thanks so much for your help to date.
 
Thanks for your help. I have ended up setting all the PCs on the network as DHCP reserved ip addresses (I did lots of searching last evening and the consensus seemed to come down in favour of DHCP reservation over static ip). I won't speak too loudly, but at this point 5 hours after the change, all is well. Thanks again.
 
Back
Top