If so, we replace that PC. It's far cheaper than letting staff tinker with it for days.
Bob
I have two systems, both windows XP SP 3. On one system is a share with read/write rights for everyone. On the other system I try to connect to that share with windows explorer using an UNC path, and this always failes the first time (after reboot). The message is that the system is not accessible, possibly because of incorrect rights. The message ends with "cannot find the network path".
After I have pinged the system once, or try it with explorer for the second (or third) time, the system and share are accessible. Then after some time of no activity, the system is suddenly not accessible anymore with explorer.
One of the systems has ip 172.168.100.10, the other has 172.168.110.20. Other systems like 172.168.120.30 are continuously accessible.
Accessing the system from windows 7 sometimes takes a little more time then expected, but it seems that this works fine everytime.
I've tried everything to get the share working. I.e. a script that starts pinging as soon as the computer boots and creating a netwerk drive. Nothing works because the system will become unavailable after some time.
My application that needs information every now and then from this system fails. Retrieving the information from other systems works fine.
Now I'm stuck. Is there anything I can do to get this working? Do I miss something? I've got full control over the systems and the application. Users, shares etc is setup correctly.

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic