Well,
I am running a small home network with 3 desktops and 2 laptops. Both
laptops are running Windows XP Home w/ SP2 and I have a desktop running
Windows XP Pro w/ SP2, another running Windows XP Pro x64 Edition, and
another running Windows XP Home w/ SP2. All the systems are completely
updated and configured properly (I am running in a workgroup configuration)
but some funny crap is happening. The My Network Places on all the machines
seem to be on the fritz. First, the x64 machine sees every thing but its own
shared resources (it doesn’t even see itself in the “view workgroup
computers�). All the rest of the regular xp machines see their own shared
resources as well as each other but not the x64 machine. How can I force a
refresh of the My network places on all the machines? I can access all the
shares on the x64 system by typing the share address manually (aka \\computer
name\) but the x64 system doesn’t show in My network Places, not even in its
own my network places. I can go into command prompt and type the command “net
view� and all the computers come up except the x64 machine (this is true on
every computer). The x64 machine doesn’t even display itself when “net view�
is executed but is sees the rest. What could the problem be? I have double
checked all the configuration and windows firewall settings and every thing
is ok. What is wrong?

Thanks,
Slice

On Sat, 12 Nov 2005 23:08:02 -0800, "Slice" <Slice@discussions.microsoft.com>
wrote:

>Well,
>I am running a small home network with 3 desktops and 2 laptops. Both
>laptops are running Windows XP Home w/ SP2 and I have a desktop running
>Windows XP Pro w/ SP2, another running Windows XP Pro x64 Edition, and
>another running Windows XP Home w/ SP2. All the systems are completely
>updated and configured properly (I am running in a workgroup configuration)
>but some funny crap is happening. The My Network Places on all the machines
>seem to be on the fritz. First, the x64 machine sees every thing but its own
>shared resources (it doesn’t even see itself in the “view workgroup
>computers”). All the rest of the regular xp machines see their own shared
>resources as well as each other but not the x64 machine. How can I force a
>refresh of the My network places on all the machines? I can access all the
>shares on the x64 system by typing the share address manually (aka \\computer
>name\) but the x64 system doesn’t show in My network Places, not even in its
>own my network places. I can go into command prompt and type the command “net
>view” and all the computers come up except the x64 machine (this is true on
>every computer). The x64 machine doesn’t even display itself when “net view”
>is executed but is sees the rest. What could the problem be? I have double
>checked all the configuration and windows firewall settings and every thing
>is ok. What is wrong?
>
>Thanks,
>Slice

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.

"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

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.

"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}

well,
i tried disabling the browser service on all the computers but the x64 box
but still no go(the x64 box sees all the other computers and they see each
other but they dont see the x64 box and the x64 box still doesnt see itself).
the x64 box just refuses to see itself. some one in another forum said that
it may have something to do with me not installinf the nvidia firewall that
comes with my chipset drivers but i when i installed that it made no
difference. so i am going to reinstall windows and see if that helps.
although at this rate it wont.

On Wed, 16 Nov 2005 13:25:00 -0800, "Slice" <Slice@discussions.microsoft.com>
wrote:

>
>
>"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}

That's a start. Which computer is that from? It would help to see the same for
all the computers. Also "ipconfig /all" for all computers.

There are several possible reasons for an "error = 53".
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
http://nitecruzr.blogspot.com/2005/0...not-found.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.

Also is there any way to make my x64 box the preferred master browser?

That way I could run the computer browser service on all the computers so if
my x64 box goes down browsing services will still function when the x64 box
is down but they will always default to using the x64 box as the master
browser when it is present or when it comes back on-line.

Slice

Whould this do what i am discribing?
http://www.windowsnetworking.com/kba...erBrowser.html

On Wed, 16 Nov 2005 16:46:05 -0800, "Slice" <Slice@discussions.microsoft.com>
wrote:

>Well,
>Just finished reinstalling and reconfiguring windows on my x64 box and all
>seems to be working now. But I do have a few questions.
>
>I have gone around to all my computers on my network except the x64 box and
>disabled the computer browsing service. My question is should I have this
>service enabled on more then one computer, for redundancy (for example if I
>have to take down my x64 box for maintenance). How many computers should I
>have the browsing service enabled on?
>
>Slice

You're asking the questions that you should have asked before reinstalling
Windows.

If you have 2 browsers (computers running the service), and they both elect
themselves master browsers, you will have a segmented workgroup, and you will
have computers that can't see each other. If you have just 1 browser, and it
goes down, you will have computers that can't see each other.

In any domain or workgroup, you can only have 1 master browser. You have to
have a master browser if you are going to use Network Neighborhood. You need a
backup browser, to take over from the master browser if it ever goes down.

Confused? Read this article for details.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/0...lways-see.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.

On Wed, 16 Nov 2005 16:57:01 -0800, "Slice" <Slice@discussions.microsoft.com>
wrote:

>Also is there any way to make my x64 box the preferred master browser?
>
>That way I could run the computer browser service on all the computers so if
>my x64 box goes down browsing services will still function when the x64 box
>is down but they will always default to using the x64 box as the master
>browser when it is present or when it comes back on-line.
>
>Slice
>
>Whould this do what i am discribing?
>http://www.windowsnetworking.com/kba...erBrowser.html

Read my article, and my explanation above.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/0...lways-see.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.