"Chuck" wrote:

> On Tue, 15 Nov 2005 23:33:04 -0800, "Slice" <Slice@discussions.microsoft.com>
> wrote:
>
> >
> >
> >"Chuck" wrote:
> >
> >> On Sat, 12 Nov 2005 23:08:02 -0800, "Slice" <Slice@discussions.microsoft.com>
> >> wrote:
> >> Slice,
> >>
> >> See if any information in my troubleshooting guide is of any use:
> >> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
> >> http://nitecruzr.blogspot.com/2005/1...isibility.html
> >>
> >> --
> >> Cheers,
> >> Chuck, MS-MVP [Windows - Networking]
> >> http://nitecruzr.blogspot.com/
> >> Paranoia is not a problem, when it's a normal response from experience.
> >> My email is AT DOT
> >> actual address pchuck mvps org.
> >>
> >
> >I looked through the info you provided in that link and I think it is one of
> >two things that is causing my problems. First and the more likely offender is
> >that it has something to do with the configuration of my Windows XP
> >Professional x64 Edition box, or second, it is a browser problem. I for one
> >think it is more likely to be a problem with my x64 box. This is because;
> >when it is totally unplugged from the network it does not recognize its own
> >shared folders (even after being restarted with no connection to the network
> >which would eliminate the possibility of a browser problem in my opinion).
> >Now that said, what could be causing this behavior?
> >
> >Thanks,
> >Slice
>
> Slice,
>
> One of the challenges of the browser is having enough browsers, but not too
> many, on any LAN. When you disconnect any server that's NOT a browser from a
> LAN, it has no browser to receive Network Neighborhood information from and
> won't see any computers, including itself.
>
> You need to look at "browstat status" and "ipconfig /all" from each computer, as
> a start. Read this article, and linked articles, and follow instructions
> precisely:
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
> http://nitecruzr.blogspot.com/2005/0...#AskingForHelp
>
> And make sure that all computers are running the right services, protocols and
> transports:
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
> http://nitecruzr.blogspot.com/2005/0...tml#Components
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My email is AT DOT
> actual address pchuck mvps org.
>

here is the results from my browstat...

??not sure what it tells me though??

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{23BBB183-E93A-43EC
-A7F6-A8EEC95B4169}
Browsing is active on domain.
Master browser name is: MOMS-DELL
Could not connect to registry, error = 53 Unable to determine build
of br
owser master: 53
\\\\MOMS-DELL . Version:05.01 Flags: 51203 NT POTENTIAL MASTER
1 backup servers retrieved from master MOMS-DELL
\\MOMS-DELL
There are 2 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{23
BBB183-E93A-43EC-A7F6-A8EEC95B4169}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{23
BBB183-E93A-43EC-A7F6-A8EEC95B4169}