No network provider accepted the given network path
One of our client PC's intermittantly fails to connect to the domain correctly on a morning. This happens once or twice a week at the most and is always after the PC has been shut down overnight (restarting has never failed!)
On logging on, we get the error message:
Program Manager
"\\ServerName\RedirectedFo
No network provider accepted the given network path."
A restart or log off then back on fixes the issue - however the user sets out their icons in a particular way and has a desktop background - these get lost when this happens!
This has been happening for a while now - initially we put it down to bad network cabling / socket however the network has now been replaced with a CAT6 network, the users PC has been replaced (Running XP SP3, and Realtek based Gigabit networking card) and the server was a 2003 server when this problem started! (Now 2008 SBS)
This leads me to believe that it may be something in the users profile causing the problem - but I'm struggling to find out exactly what! Nobody else in the domain has the issue! What should I look for, and how can I trace the cause of this?
On logging on, we get the error message:
Program Manager
"\\ServerName\RedirectedFo
No network provider accepted the given network path."
A restart or log off then back on fixes the issue - however the user sets out their icons in a particular way and has a desktop background - these get lost when this happens!
This has been happening for a while now - initially we put it down to bad network cabling / socket however the network has now been replaced with a CAT6 network, the users PC has been replaced (Running XP SP3, and Realtek based Gigabit networking card) and the server was a 2003 server when this problem started! (Now 2008 SBS)
This leads me to believe that it may be something in the users profile causing the problem - but I'm struggling to find out exactly what! Nobody else in the domain has the issue! What should I look for, and how can I trace the cause of this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Paul
http://forums.techguy.org/networking/289768-solved-you-might-not-have.html
ASKER
There was no network drive mapped. There is now though.
The funny thing is that the computer can access all shares from anywhere on the network with no problems whatsoever - using unc, IP address etc it has no issues!
The only slightly odd thing I can see is that the server isn't shown in network neighborhood - though I can still access it via \\Servername or now via mapped drive!
The funny thing is that the computer can access all shares from anywhere on the network with no problems whatsoever - using unc, IP address etc it has no issues!
The only slightly odd thing I can see is that the server isn't shown in network neighborhood - though I can still access it via \\Servername or now via mapped drive!