Windows XP looses path to server

  • Thread starter Thread starter Mark C.
  • Start date Start date
M

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.
 
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.
Click to expand...

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
 
i can give that a try...however, the shortcut error is just a clue that the
systems lost the authentication to the server...if you go to my computer, and
click on the mapped F: drive which points to the data directory, the message
about it being inacessible pops up, and if you just log back in, without a
reboot, it can be accessed it, and the shortcut works again.
 
i can give that a try...however, the shortcut error is just a clue
that the systems lost the authentication to the server...if you go
to my computer, and click on the mapped F: drive which points to
the data directory, the message about it being inacessible pops
up, and if you just log back in, without a reboot, it can be
accessed it, and the shortcut works again.
Click to expand...

I tend to agree. (What can I say... I was grabbing at straws)...
I was hoping that maybe an entry in the LMHOSTS file with the #PRE and
#DOM: attributes to declare it as the DC might keep it from dropping
connection and losing authentication.

-- John
 
Back
Top