Host not displayed in explorer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a network of four computers, three running XP, one Windows 2000, all
on the same subnet. Almost everything works fine, I can access any computer
from any other and share folders without problem. However, one XP computer
is not shown in the network explorer by any of the computers, including
itself.
Analysing the packet flows around the network show that the offending
host only advertises itself to the master browser upon startup and then
never issues another advertisement - hence it is shown on the domain for a
short period of time, never to be seen again until it is restarted.

Any suggestions on how I can resume normal operations?
 
I have a network of four computers, three running XP, one Windows 2000, all
on the same subnet. Almost everything works fine, I can access any computer
from any other and share folders without problem. However, one XP computer
is not shown in the network explorer by any of the computers, including
itself.
Analysing the packet flows around the network show that the offending
host only advertises itself to the master browser upon startup and then
never issues another advertisement - hence it is shown on the domain for a
short period of time, never to be seen again until it is restarted.

Any suggestions on how I can resume normal operations?
Click to expand...

Does the offending computer have shares defined? Are you actually accessing
this computer successfully, even though you can't see it?

I'd start by looking at "browstat status" and "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
 
Hi Chuck,

Thanks for your response. The offending host does have shares defined, and
these work just fine. I can access everything on the offending computer that
I should, and the offending computer can access everything it is allowed to.
I can Search for the offending computer and it is found correctly. The only
thing that I cannot do is browse for the offending computer.

I have been through all your suggestest tests and used browstat, which I had
already downloaded to try to get to the bottom of the issue; everything seems
to be okay.

I have narrowed the problem down (I believe) to the Server service. When the
Server service is started (or restarted), a Browse announcement is broadcast
correctly and the Master Browse Server correctly adds the host to its list -
at this point the offending computer is seen correctly in the network
browser. However, a second (or subsequent) Browse announcement is never
issued from the offending host, so the Master Browse Server ages out the host
- never to be seen on the network browser again, unless the Server service is
restarted. There are no errors logged in the Event log and the Server service
is shown as running.

Are there any logs that I could post that would help narrow down the problem
to lead to an eventual resolution?

Thanks

David
 
Hi Chuck,

Thanks for your response. The offending host does have shares defined, and
these work just fine. I can access everything on the offending computer that
I should, and the offending computer can access everything it is allowed to.
I can Search for the offending computer and it is found correctly. The only
thing that I cannot do is browse for the offending computer.

I have been through all your suggestest tests and used browstat, which I had
already downloaded to try to get to the bottom of the issue; everything seems
to be okay.

I have narrowed the problem down (I believe) to the Server service. When the
Server service is started (or restarted), a Browse announcement is broadcast
correctly and the Master Browse Server correctly adds the host to its list -
at this point the offending computer is seen correctly in the network
browser. However, a second (or subsequent) Browse announcement is never
issued from the offending host, so the Master Browse Server ages out the host
- never to be seen on the network browser again, unless the Server service is
restarted. There are no errors logged in the Event log and the Server service
is shown as running.

Are there any logs that I could post that would help narrow down the problem
to lead to an eventual resolution?

Thanks

David
Click to expand...

David,

The Event Log is where all problems get logged, as far as I know.

Why not post the "browstat status" logs for all 4 computers. Every now and
then, what "seems to be okay" at first glance turns out not to be. Start from
what you have, and work forward.
 
Hi Chuck,

I will post the logs in the next couple of days to see if anyone can spot
the problem. Meanwhile, I have found one other anomaly: The command "Browstat
Stats" on the offending host yields the error #87 - all other commands seem
to work fine. I have tried the LSP/Winsock fixes, rebuilt the registry, and
reset the TCP/IP stack as instructed on your web site but both problems
(Server service issuing repeat host announcement packets and Browstat Stats =
#87) still exist.

Nothing else appears to be at fault with inter-host connectivity or with any
shares.

David
 
Hi Chuck,

I will post the logs in the next couple of days to see if anyone can spot
the problem. Meanwhile, I have found one other anomaly: The command "Browstat
Stats" on the offending host yields the error #87 - all other commands seem
to work fine. I have tried the LSP/Winsock fixes, rebuilt the registry, and
reset the TCP/IP stack as instructed on your web site but both problems
(Server service issuing repeat host announcement packets and Browstat Stats =
#87) still exist.

Nothing else appears to be at fault with inter-host connectivity or with any
shares.

David
Click to expand...

C:\>net helpmsg 87

The parameter is incorrect.

Try "browstat status".
 
"Browstat status" works just fine... as do all the other Browstat options.
Even "Browstat stats \\host reset" does not return an error, although I
cannot see if it has worked correctly.
 
"Browstat status" works just fine... as do all the other Browstat options.
Even "Browstat stats \\host reset" does not return an error, although I
cannot see if it has worked correctly.
Click to expand...

OK, if they work fine, why not post the logs. They are diagnostic tools, and
they may be useful to diagnose your problem.

If you have "browstat status" returning the error 87, you have a problem on that
computer, so start there. If the error 87 has gone away, then let's look at
"browstat status" logs from all 4 computers.
 
Back
Top