Home All Groups Group Topic Archive Search About

Windows XP looses path to server

Author
24 Mar 2009 1:41 PM
Mark C.
I have a customer that has windows xp pro workstations, service pack 3, in a
domain connecting to a small business server 2003 system.  Throughout the day
he clicks on a shortcut that points to a program on the server and gets the
message path not found, and sure enough, if you go into network neighborhood,
the server is not available.  He started rebooting and connection works again
for a while, then same thing occurs.  After i was called, i asked him not to
reboot, just simply go to the start button, and logoff...he logs back in
without a reboot and hes back in the system.  I have already disabled the
power management feature of the device.

Author
24 Mar 2009 7:53 PM
John Wunderlich
=?Utf-8?B?TWFyayBDLg==?= <Ma***@discussions.microsoft.com> wrote in
Show quoteHide quote
news:63EDAD77-34F2-449E-8210-EB3024C40DC3@microsoft.com:

> I have a customer that has windows xp pro workstations, service
> pack 3, in a domain connecting to a small business server 2003
> system.  Throughout the day he clicks on a shortcut that points to
> a program on the server and gets the message path not found, and
> sure enough, if you go into network neighborhood, the server is
> not available.  He started rebooting and connection works again
> for a while, then same thing occurs.  After i was called, i asked
> him not to reboot, just simply go to the start button, and
> logoff...he logs back in without a reboot and hes back in the
> system.  I have already disabled the power management feature of
> the device.
>

The symptoms sound like a Browse Master issue (entries in your Network
Neighborhood come from the Browse Master).  I am assuming that there is
no WINS server and all machines are on the same subnet.  If just one
machine on the subnet has a firewall enabled that is unfriendly to
Microsoft Networking, it can affect the entire subnet.

Some things to try:
1) Can you access the server by IP address instead of name?
   (e.g.   \\192.168.1.10\Share)
   If this works, modify your shortcut.
2) Place an entry for the server in the "lmhosts" file...
   Usually in directory \Windows\System32\drivers\etc\
   (Hint: modify the lmhost.sam file and save without the '.sam')
3) Check the response to an "nbtstat" command
   Bring up command window (Start -> Run -> "Cmd")
   Enter the command:   nbtstat -a \\servername
   If this works, the server might be cached and may be accessible for
a while.

Microsoft's information on this issue:
"Internet firewalls can prevent browsing and file sharing"
  <http://support.microsoft.com/kb/298804>

HTH,
  John
Author
24 Mar 2009 7:59 PM
John Wunderlich
John Wunderlich <jwunderl***@lycos.com> wrote in
news:Xns9BD88329831D8wunderpsdrscray@138.126.254.210:

>    Enter the command:   nbtstat -a \\servername
>

.... sorry, this won't work with the "\\'
     Enter the command:   nbtstat -a servername

-- John