>I have one computer {call it A} in my network that others {B and C} are
>unable to see.  While B and C can successfully ping A using the IP address,
>pinging using the computer name returns a "53 error".  Additionally, when
>addressing A from B or C using the net view command, an invalid path message
>results.  This is true using either A's IP address or its name.
>
>A is able to see all the files/folders/printers in B and C that are enabled
>for sharing -- and works exactly as expected.
>
>All three computers have been set to "Broadcast" node; NetBT has been
>enabled on each computer; and there are no problem entries in either the Host
>or LMHost files.
>
>Finally, I have a Linksys BEFSR 41 v 1 with the latest firmware -- for what
>it's worth.
>
>Computer A is a Lenovo T60 notebook on a docking station running XP Pro; B
>is an eMachine desktop running XP Home; and C is a Dell desktop running ME.
>
>Thanks........

"Chuck" wrote:

> On Sun, 15 Oct 2006 11:59:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>
> >I have one computer {call it A} in my network that others {B and C} are
> >unable to see.  While B and C can successfully ping A using the IP address,
> >pinging using the computer name returns a "53 error".  Additionally, when
> >addressing A from B or C using the net view command, an invalid path message
> >results.  This is true using either A's IP address or its name.
> >
> >A is able to see all the files/folders/printers in B and C that are enabled
> >for sharing -- and works exactly as expected.
> >
> >All three computers have been set to "Broadcast" node; NetBT has been
> >enabled on each computer; and there are no problem entries in either the Host
> >or LMHost files.
> >
> >Finally, I have a Linksys BEFSR 41 v 1 with the latest firmware -- for what
> >it's worth.
> >
> >Computer A is a Lenovo T60 notebook on a docking station running XP Pro; B
> >is an eMachine desktop running XP Home; and C is a Dell desktop running ME.
> >
> >Thanks........
>
> Lee,
>
> An "error 53" is name resolution error, which typically comes from SMBs being
> blocked somewhere, ie by a personal firewall (not the BEFSR41, which is a switch
> on the LAN).
> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
> http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html
>
> Let's look 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
>
> --
> 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 Sun, 15 Oct 2006 11:59:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>
> >I have one computer {call it A} in my network that others {B and C} are
> >unable to see.  While B and C can successfully ping A using the IP address,
> >pinging using the computer name returns a "53 error".  Additionally, when
> >addressing A from B or C using the net view command, an invalid path message
> >results.  This is true using either A's IP address or its name.
> >
> >A is able to see all the files/folders/printers in B and C that are enabled
> >for sharing -- and works exactly as expected.
> >
> >All three computers have been set to "Broadcast" node; NetBT has been
> >enabled on each computer; and there are no problem entries in either the Host
> >or LMHost files.
> >
> >Finally, I have a Linksys BEFSR 41 v 1 with the latest firmware -- for what
> >it's worth.
> >
> >Computer A is a Lenovo T60 notebook on a docking station running XP Pro; B
> >is an eMachine desktop running XP Home; and C is a Dell desktop running ME.
> >
> >Thanks........
>
> Lee,
>
> An "error 53" is name resolution error, which typically comes from SMBs being
> blocked somewhere, ie by a personal firewall (not the BEFSR41, which is a switch
> on the LAN).
> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
> http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html
>
> Let's look 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
>
> --
> 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 Sun, 15 Oct 2006 11:59:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>
> >I have one computer {call it A} in my network that others {B and C} are
> >unable to see.  While B and C can successfully ping A using the IP address,
> >pinging using the computer name returns a "53 error".  Additionally, when
> >addressing A from B or C using the net view command, an invalid path message
> >results.  This is true using either A's IP address or its name.
> >
> >A is able to see all the files/folders/printers in B and C that are enabled
> >for sharing -- and works exactly as expected.
> >
> >All three computers have been set to "Broadcast" node; NetBT has been
> >enabled on each computer; and there are no problem entries in either the Host
> >or LMHost files.
> >
> >Finally, I have a Linksys BEFSR 41 v 1 with the latest firmware -- for what
> >it's worth.
> >
> >Computer A is a Lenovo T60 notebook on a docking station running XP Pro; B
> >is an eMachine desktop running XP Home; and C is a Dell desktop running ME.
> >
> >Thanks........
>
> Lee,
>
> An "error 53" is name resolution error, which typically comes from SMBs being
> blocked somewhere, ie by a personal firewall (not the BEFSR41, which is a switch
> on the LAN).
> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
> http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html
>
> Let's look 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
>
> --
> 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 Sun, 15 Oct 2006 11:59:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>>
>> >I have one computer {call it A} in my network that others {B and C} are
>> >unable to see.  While B and C can successfully ping A using the IP address,
>> >pinging using the computer name returns a "53 error".  Additionally, when
>> >addressing A from B or C using the net view command, an invalid path message
>> >results.  This is true using either A's IP address or its name.
>> >
>> >A is able to see all the files/folders/printers in B and C that are enabled
>> >for sharing -- and works exactly as expected.
>> >
>> >All three computers have been set to "Broadcast" node; NetBT has been
>> >enabled on each computer; and there are no problem entries in either the Host
>> >or LMHost files.
>> >
>> >Finally, I have a Linksys BEFSR 41 v 1 with the latest firmware -- for what
>> >it's worth.
>> >
>> >Computer A is a Lenovo T60 notebook on a docking station running XP Pro; B
>> >is an eMachine desktop running XP Home; and C is a Dell desktop running ME.
>> >
>> >Thanks........
>>
>> Lee,
>>
>> An "error 53" is name resolution error, which typically comes from SMBs being
>> blocked somewhere, ie by a personal firewall (not the BEFSR41, which is a switch
>> on the LAN).
>> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>> http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html
>>
>> Let's look 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

"Chuck" wrote:

> On Sun, 15 Oct 2006 19:00:02 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>
> >
> >
> >"Chuck" wrote:
> >
> >> On Sun, 15 Oct 2006 11:59:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
> >>
> >> >I have one computer {call it A} in my network that others {B and C} are
> >> >unable to see.  While B and C can successfully ping A using the IP address,
> >> >pinging using the computer name returns a "53 error".  Additionally, when
> >> >addressing A from B or C using the net view command, an invalid path message
> >> >results.  This is true using either A's IP address or its name.
> >> >
> >> >A is able to see all the files/folders/printers in B and C that are enabled
> >> >for sharing -- and works exactly as expected.
> >> >
> >> >All three computers have been set to "Broadcast" node; NetBT has been
> >> >enabled on each computer; and there are no problem entries in either the Host
> >> >or LMHost files.
> >> >
> >> >Finally, I have a Linksys BEFSR 41 v 1 with the latest firmware -- for what
> >> >it's worth.
> >> >
> >> >Computer A is a Lenovo T60 notebook on a docking station running XP Pro; B
> >> >is an eMachine desktop running XP Home; and C is a Dell desktop running ME.
> >> >
> >> >Thanks........
> >>
> >> Lee,
> >>
> >> An "error 53" is name resolution error, which typically comes from SMBs being
> >> blocked somewhere, ie by a personal firewall (not the BEFSR41, which is a switch
> >> on the LAN).
> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
> >> http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html
> >>
> >> Let's look 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
>
> <SNIP>
>
> >C. I did not run either for the 3rd computer, the Dell Desktop running ME. 
> >The command window disappears immediately after opening...
>
> Well, "ipconfig /all" for the 3rd might be useful, and you might yet end up
> running it.  Let's see what we can diagnose from the other 2 though.
> # Both computers are on the same subnet (192.168.1.0/24), and both are using
> Broadcast name resolution.
> # Both computer browsers see 2 computers. ("There are 2 servers in domain").
> # Here's a possible problem:
> > Windows IP Configuration
> >        Host Name . . . . . . . . . . . . : eMachine
> > Ethernet adapter Local Area Connection:
> >        Connection-specific DNS Suffix  . : hsd1.fl.comcast.net.
> >        Description . . . . . . . . . . . : NVIDIA nForce MCP Networking
> > Controller
> The nVidia nForce is a known problem here.
> <http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
> http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html
> # You also might want to make sure that the browse master is NOT running on the
> Windows ME computer.
> <http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
> http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.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 Sun, 15 Oct 2006 19:00:02 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>>
>> >
>> >
>> >"Chuck" wrote:
>> >
>> >> On Sun, 15 Oct 2006 11:59:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>> >>
>> >> >I have one computer {call it A} in my network that others {B and C} are
>> >> >unable to see.  While B and C can successfully ping A using the IP address,
>> >> >pinging using the computer name returns a "53 error".  Additionally, when
>> >> >addressing A from B or C using the net view command, an invalid path message
>> >> >results.  This is true using either A's IP address or its name.
>> >> >
>> >> >A is able to see all the files/folders/printers in B and C that are enabled
>> >> >for sharing -- and works exactly as expected.
>> >> >
>> >> >All three computers have been set to "Broadcast" node; NetBT has been
>> >> >enabled on each computer; and there are no problem entries in either the Host
>> >> >or LMHost files.
>> >> >
>> >> >Finally, I have a Linksys BEFSR 41 v 1 with the latest firmware -- for what
>> >> >it's worth.
>> >> >
>> >> >Computer A is a Lenovo T60 notebook on a docking station running XP Pro; B
>> >> >is an eMachine desktop running XP Home; and C is a Dell desktop running ME.
>> >> >
>> >> >Thanks........
>> >>
>> >> Lee,
>> >>
>> >> An "error 53" is name resolution error, which typically comes from SMBs being
>> >> blocked somewhere, ie by a personal firewall (not the BEFSR41, which is a switch
>> >> on the LAN).
>> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>> >> http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html
>> >>
>> >> Let's look 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
>>
>> <SNIP>
>>
>> >C. I did not run either for the 3rd computer, the Dell Desktop running ME. 
>> >The command window disappears immediately after opening...
>>
>> Well, "ipconfig /all" for the 3rd might be useful, and you might yet end up
>> running it.  Let's see what we can diagnose from the other 2 though.
>> # Both computers are on the same subnet (192.168.1.0/24), and both are using
>> Broadcast name resolution.
>> # Both computer browsers see 2 computers. ("There are 2 servers in domain").
>> # Here's a possible problem:
>> > Windows IP Configuration
>> >        Host Name . . . . . . . . . . . . : eMachine
>> > Ethernet adapter Local Area Connection:
>> >        Connection-specific DNS Suffix  . : hsd1.fl.comcast.net.
>> >        Description . . . . . . . . . . . : NVIDIA nForce MCP Networking
>> > Controller
>> The nVidia nForce is a known problem here.
>> <http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
>> http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html
>> # You also might want to make sure that the browse master is NOT running on the
>> Windows ME computer.
>> <http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
>> http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.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.
>>
>
>Hi again, Chuck.
>
>I read the procedure about de/reinstalling the NVIDIA Controller drivers and
>am a little nervous about this activity.  With eMachine tech support help I
>was able to locate the driver, so I am ready to go.  During my conversation
>with the tech he told me that the settings for the hardware firewall were set
>by the antivirus program -- in my case, Norton Antivirus 2005.  The only
>"non-virus" component of that system is a worm protector which Security
>Center identified as a firewall.  I turned it off, and Windows Firewall, with
>no luck.  So, I'm not sure the tech was right about resetting the hardware
>firewall.  However, before I plunge into this terrain, I want to be sure
>there isn't something else we might first try.
>
>Here is an idea...
>
>In your articles you comment that one should not "host" the browser in an XP
>Home OS machine.  And that's exactly what I have done.  How do I switch the
>hosting to the Lenovo with the XP Pro?  And might that not fix my problem?
>
>Maybe it's important to remember that the Lenovo can see and manipulate the
>shared resources in the eMachine computer and in the Dell running ME.  The
>eMachine and Dell are able to see and manipulate each other's shared
>resources.  While the eMachine and the Dell lists the Lenovo's presence (in
>Network Neighborhood), neither can see the Lenovo's shared resources, much
>less access them. 
>
>I just want to explore anything else before I fiddle with drivers and create
>a non-standard configuration in an otherwise totally standard machine.

> >Hi again, Chuck.
> >
> >I read the procedure about de/reinstalling the NVIDIA Controller drivers and
> >am a little nervous about this activity.  With eMachine tech support help I
> >was able to locate the driver, so I am ready to go.  During my conversation
> >with the tech he told me that the settings for the hardware firewall were set
> >by the antivirus program -- in my case, Norton Antivirus 2005.  The only
> >"non-virus" component of that system is a worm protector which Security
> >Center identified as a firewall.  I turned it off, and Windows Firewall, with
> >no luck.  So, I'm not sure the tech was right about resetting the hardware
> >firewall.  However, before I plunge into this terrain, I want to be sure
> >there isn't something else we might first try.
> >
> >Here is an idea...
> >
> >In your articles you comment that one should not "host" the browser in an XP
> >Home OS machine.  And that's exactly what I have done.  How do I switch the
> >hosting to the Lenovo with the XP Pro?  And might that not fix my problem?
> >
> >Maybe it's important to remember that the Lenovo can see and manipulate the
> >shared resources in the eMachine computer and in the Dell running ME.  The
> >eMachine and Dell are able to see and manipulate each other's shared
> >resources.  While the eMachine and the Dell lists the Lenovo's presence (in
> >Network Neighborhood), neither can see the Lenovo's shared resources, much
> >less access them. 
> >
> >I just want to explore anything else before I fiddle with drivers and create
> >a non-standard configuration in an otherwise totally standard machine.
>
> Lee,
>
> I recommend not using XP Home for the browser, if you have a choice, simply
> because diagnosing browser problems is slightly easier using XP Pro.  XP Home
> will run as a browser if there are no problems.  I highly recommend ensuring
> that any Windows 9x (95, 98, ME) computer not run the browse master.
>
> Both seeing a computer (as a server in browstat status, and in Network
> Neighbourhood) and enumerating them, both involve SMBs.  The former, though,
> involves SMBs broadcast by the computer being seen.  The latter involves a
> direct exchange of SMBs.
> 1) eMachine to Lenovo: "Please list your shares".
> 2) Lenovo to eMachine: "Here is the list".
> So the latter is more susceptible to interference by any problem that blocks
> SMBs.  This could be the hardware firewall (which also involves software
> components in the LSP - and I don't know why that is), or it could be NAV and
> the anti worm.
>
> The nVidia nForce has been known in various forums for causing problems with
> file sharing.  If you read some of the linked articles, and the posts from other
> folks seeking help, you'll note that some versions of the nForce just don't
> work.  I'm not going to condemn the nForce point blank though, as I'm not sure
> that the problems are totally caused by their drivers.  Unfortunately, I can't
> exonerate them either.
>
> And you have NAV 2005, and the anti worm protection.  Did you configure that
> properly?  That's also been found to be a problem.  If you can't configure it,
> then you may have to un install NAV.  And there are two problems there.
> 1) Un installing NAV is a major pain in the butt.
> 2) You are un protected when you do this.
> <http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html>
> http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html
>
> So let's discuss these issues, but in the end, it's your computer.  I'll advise
> you with all that I know.
>
> --
> 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.
>

>
>
>< stuff removed>
>
>> >Hi again, Chuck.
>> >
>> >I read the procedure about de/reinstalling the NVIDIA Controller drivers and
>> >am a little nervous about this activity.  With eMachine tech support help I
>> >was able to locate the driver, so I am ready to go.  During my conversation
>> >with the tech he told me that the settings for the hardware firewall were set
>> >by the antivirus program -- in my case, Norton Antivirus 2005.  The only
>> >"non-virus" component of that system is a worm protector which Security
>> >Center identified as a firewall.  I turned it off, and Windows Firewall, with
>> >no luck.  So, I'm not sure the tech was right about resetting the hardware
>> >firewall.  However, before I plunge into this terrain, I want to be sure
>> >there isn't something else we might first try.
>> >
>> >Here is an idea...
>> >
>> >In your articles you comment that one should not "host" the browser in an XP
>> >Home OS machine.  And that's exactly what I have done.  How do I switch the
>> >hosting to the Lenovo with the XP Pro?  And might that not fix my problem?
>> >
>> >Maybe it's important to remember that the Lenovo can see and manipulate the
>> >shared resources in the eMachine computer and in the Dell running ME.  The
>> >eMachine and Dell are able to see and manipulate each other's shared
>> >resources.  While the eMachine and the Dell lists the Lenovo's presence (in
>> >Network Neighborhood), neither can see the Lenovo's shared resources, much
>> >less access them. 
>> >
>> >I just want to explore anything else before I fiddle with drivers and create
>> >a non-standard configuration in an otherwise totally standard machine.
>>
>> Lee,
>>
>> I recommend not using XP Home for the browser, if you have a choice, simply
>> because diagnosing browser problems is slightly easier using XP Pro.  XP Home
>> will run as a browser if there are no problems.  I highly recommend ensuring
>> that any Windows 9x (95, 98, ME) computer not run the browse master.
>>
>> Both seeing a computer (as a server in browstat status, and in Network
>> Neighbourhood) and enumerating them, both involve SMBs.  The former, though,
>> involves SMBs broadcast by the computer being seen.  The latter involves a
>> direct exchange of SMBs.
>> 1) eMachine to Lenovo: "Please list your shares".
>> 2) Lenovo to eMachine: "Here is the list".
>> So the latter is more susceptible to interference by any problem that blocks
>> SMBs.  This could be the hardware firewall (which also involves software
>> components in the LSP - and I don't know why that is), or it could be NAV and
>> the anti worm.
>>
>> The nVidia nForce has been known in various forums for causing problems with
>> file sharing.  If you read some of the linked articles, and the posts from other
>> folks seeking help, you'll note that some versions of the nForce just don't
>> work.  I'm not going to condemn the nForce point blank though, as I'm not sure
>> that the problems are totally caused by their drivers.  Unfortunately, I can't
>> exonerate them either.
>>
>> And you have NAV 2005, and the anti worm protection.  Did you configure that
>> properly?  That's also been found to be a problem.  If you can't configure it,
>> then you may have to un install NAV.  And there are two problems there.
>> 1) Un installing NAV is a major pain in the butt.
>> 2) You are un protected when you do this.
>> <http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html>
>> http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html
>>
>> So let's discuss these issues, but in the end, it's your computer.  I'll advise
>> you with all that I know.

>Thanks for that explanation.  How do I establish a particular computer as
>the host for the browser?  Think I'll try to set the XP Pro machine as the
>browser host as an initial step and see what that does.  Takin' baby steps
>here..... ;-)
>
>BTW, during the past several diagnostic sessions the machine running ME has
>been turned off.  ( Doesn't effect the remaining machines' behaviors. )  And
>it has not been listed as the browser host at any point.

"Chuck" wrote:

> On Mon, 16 Oct 2006 17:11:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>
> >
> >
> >< stuff removed>
> >
> >> >Hi again, Chuck.
> >> >
> >> >I read the procedure about de/reinstalling the NVIDIA Controller drivers and
> >> >am a little nervous about this activity.  With eMachine tech support help I
> >> >was able to locate the driver, so I am ready to go.  During my conversation
> >> >with the tech he told me that the settings for the hardware firewall were set
> >> >by the antivirus program -- in my case, Norton Antivirus 2005.  The only
> >> >"non-virus" component of that system is a worm protector which Security
> >> >Center identified as a firewall.  I turned it off, and Windows Firewall, with
> >> >no luck.  So, I'm not sure the tech was right about resetting the hardware
> >> >firewall.  However, before I plunge into this terrain, I want to be sure
> >> >there isn't something else we might first try.
> >> >
> >> >Here is an idea...
> >> >
> >> >In your articles you comment that one should not "host" the browser in an XP
> >> >Home OS machine.  And that's exactly what I have done.  How do I switch the
> >> >hosting to the Lenovo with the XP Pro?  And might that not fix my problem?
> >> >
> >> >Maybe it's important to remember that the Lenovo can see and manipulate the
> >> >shared resources in the eMachine computer and in the Dell running ME.  The
> >> >eMachine and Dell are able to see and manipulate each other's shared
> >> >resources.  While the eMachine and the Dell lists the Lenovo's presence (in
> >> >Network Neighborhood), neither can see the Lenovo's shared resources, much
> >> >less access them. 
> >> >
> >> >I just want to explore anything else before I fiddle with drivers and create
> >> >a non-standard configuration in an otherwise totally standard machine.
> >>
> >> Lee,
> >>
> >> I recommend not using XP Home for the browser, if you have a choice, simply
> >> because diagnosing browser problems is slightly easier using XP Pro.  XP Home
> >> will run as a browser if there are no problems.  I highly recommend ensuring
> >> that any Windows 9x (95, 98, ME) computer not run the browse master.
> >>
> >> Both seeing a computer (as a server in browstat status, and in Network
> >> Neighbourhood) and enumerating them, both involve SMBs.  The former, though,
> >> involves SMBs broadcast by the computer being seen.  The latter involves a
> >> direct exchange of SMBs.
> >> 1) eMachine to Lenovo: "Please list your shares".
> >> 2) Lenovo to eMachine: "Here is the list".
> >> So the latter is more susceptible to interference by any problem that blocks
> >> SMBs.  This could be the hardware firewall (which also involves software
> >> components in the LSP - and I don't know why that is), or it could be NAV and
> >> the anti worm.
> >>
> >> The nVidia nForce has been known in various forums for causing problems with
> >> file sharing.  If you read some of the linked articles, and the posts from other
> >> folks seeking help, you'll note that some versions of the nForce just don't
> >> work.  I'm not going to condemn the nForce point blank though, as I'm not sure
> >> that the problems are totally caused by their drivers.  Unfortunately, I can't
> >> exonerate them either.
> >>
> >> And you have NAV 2005, and the anti worm protection.  Did you configure that
> >> properly?  That's also been found to be a problem.  If you can't configure it,
> >> then you may have to un install NAV.  And there are two problems there.
> >> 1) Un installing NAV is a major pain in the butt.
> >> 2) You are un protected when you do this.
> >> <http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html>
> >> http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html
> >>
> >> So let's discuss these issues, but in the end, it's your computer.  I'll advise
> >> you with all that I know.
>
> >Thanks for that explanation.  How do I establish a particular computer as
> >the host for the browser?  Think I'll try to set the XP Pro machine as the
> >browser host as an initial step and see what that does.  Takin' baby steps
> >here..... ;-)
> >
> >BTW, during the past several diagnostic sessions the machine running ME has
> >been turned off.  ( Doesn't effect the remaining machines' behaviors. )  And
> >it has not been listed as the browser host at any point.
>
> If either one of the Windows XP computers stays up and online 7 x 24, or at
> least when the other 2 computers need resources from each other, then you can
> use that computer as the browser exclusively.  And all that you need to do is
> shut off the browser on the other 2.  See my article for a good explanation of
> why all this is necessary, and of how to do this.
> <http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
> http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-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.
>

>"Chuck" wrote:
>
>> On Mon, 16 Oct 2006 17:11:01 -0700, LeeB <L***@discussions.microsoft.com> wrote:
>>
>> >
>> >
>> >< stuff removed>
>> >
>> >> >Hi again, Chuck.
>> >> >
>> >> >I read the procedure about de/reinstalling the NVIDIA Controller drivers and
>> >> >am a little nervous about this activity.  With eMachine tech support help I
>> >> >was able to locate the driver, so I am ready to go.  During my conversation
>> >> >with the tech he told me that the settings for the hardware firewall were set
>> >> >by the antivirus program -- in my case, Norton Antivirus 2005.  The only
>> >> >"non-virus" component of that system is a worm protector which Security
>> >> >Center identified as a firewall.  I turned it off, and Windows Firewall, with
>> >> >no luck.  So, I'm not sure the tech was right about resetting the hardware
>> >> >firewall.  However, before I plunge into this terrain, I want to be sure
>> >> >there isn't something else we might first try.
>> >> >
>> >> >Here is an idea...
>> >> >
>> >> >In your articles you comment that one should not "host" the browser in an XP
>> >> >Home OS machine.  And that's exactly what I have done.  How do I switch the
>> >> >hosting to the Lenovo with the XP Pro?  And might that not fix my problem?
>> >> >
>> >> >Maybe it's important to remember that the Lenovo can see and manipulate the
>> >> >shared resources in the eMachine computer and in the Dell running ME.  The
>> >> >eMachine and Dell are able to see and manipulate each other's shared
>> >> >resources.  While the eMachine and the Dell lists the Lenovo's presence (in
>> >> >Network Neighborhood), neither can see the Lenovo's shared resources, much
>> >> >less access them. 
>> >> >
>> >> >I just want to explore anything else before I fiddle with drivers and create
>> >> >a non-standard configuration in an otherwise totally standard machine.
>> >>
>> >> Lee,
>> >>
>> >> I recommend not using XP Home for the browser, if you have a choice, simply
>> >> because diagnosing browser problems is slightly easier using XP Pro.  XP Home
>> >> will run as a browser if there are no problems.  I highly recommend ensuring
>> >> that any Windows 9x (95, 98, ME) computer not run the browse master.
>> >>
>> >> Both seeing a computer (as a server in browstat status, and in Network
>> >> Neighbourhood) and enumerating them, both involve SMBs.  The former, though,
>> >> involves SMBs broadcast by the computer being seen.  The latter involves a
>> >> direct exchange of SMBs.
>> >> 1) eMachine to Lenovo: "Please list your shares".
>> >> 2) Lenovo to eMachine: "Here is the list".
>> >> So the latter is more susceptible to interference by any problem that blocks
>> >> SMBs.  This could be the hardware firewall (which also involves software
>> >> components in the LSP - and I don't know why that is), or it could be NAV and
>> >> the anti worm.
>> >>
>> >> The nVidia nForce has been known in various forums for causing problems with
>> >> file sharing.  If you read some of the linked articles, and the posts from other
>> >> folks seeking help, you'll note that some versions of the nForce just don't
>> >> work.  I'm not going to condemn the nForce point blank though, as I'm not sure
>> >> that the problems are totally caused by their drivers.  Unfortunately, I can't
>> >> exonerate them either.
>> >>
>> >> And you have NAV 2005, and the anti worm protection.  Did you configure that
>> >> properly?  That's also been found to be a problem.  If you can't configure it,
>> >> then you may have to un install NAV.  And there are two problems there.
>> >> 1) Un installing NAV is a major pain in the butt.
>> >> 2) You are un protected when you do this.
>> >> <http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html>
>> >> http://nitecruzr.blogspot.com/2005/08/un-install-security-products-carefully.html
>> >>
>> >> So let's discuss these issues, but in the end, it's your computer.  I'll advise
>> >> you with all that I know.
>>
>> >Thanks for that explanation.  How do I establish a particular computer as
>> >the host for the browser?  Think I'll try to set the XP Pro machine as the
>> >browser host as an initial step and see what that does.  Takin' baby steps
>> >here..... ;-)
>> >
>> >BTW, during the past several diagnostic sessions the machine running ME has
>> >been turned off.  ( Doesn't effect the remaining machines' behaviors. )  And
>> >it has not been listed as the browser host at any point.
>>
>> If either one of the Windows XP computers stays up and online 7 x 24, or at
>> least when the other 2 computers need resources from each other, then you can
>> use that computer as the browser exclusively.  And all that you need to do is
>> shut off the browser on the other 2.  See my article for a good explanation of
>> why all this is necessary, and of how to do this.
>> <http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
>> http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

>Hello Chuck -- My problem seems to be solved.  And, boy, did I go around the
>barn to find the problem!  To try to isolate the problem computer I ran the
>network with 2 computers at a time, turning off the master browser on one
>computer.  Then checked browstat and network neighborhood.  I then did the
>same for the three computer network.  The results seemed very consistent --
>pointing to the Lenovo as the machine blocking access.  For example, whenever
>the Lenovo browser was the only browser available to the network, the only
>server the Lenovo saw was itself and the other computers saw none. 
>
>I then began experimenting with firewall settings and -- lo and behold --
>when I turned off the Windows Firewall on the Lenovo, everything behaved; no
>problems in this configuration.  I tried reconfiguring the Firewall to permit
>all things that might be permitted using the advanced tab to no avail.  The
>only solution seems to be turning the thing off.  This is not a terrible
>situation -- I have a built-in firewall in the router and my computer also
>has a Symantic firewall available.  The Symantic firewall had previously been
>turned off -- didn't want two of these alive at a time.  But after turning
>the Symantic firewall on, I continued to have no trouble with the network. 
>So I think I'll leave things this way.
>
>Wonder what's going on with the Windows Firewall?  I remember reading a line
>in one of your articles that said turning it off was not advised and could
>cause {neetwork??} problems. 
>
>Thanks for the help; I've certainly learned a great deal in this acitivity
>-- just enough to make me dangerous because I still lack a fundamental
>understanding for how networks operate -- you know, the services, processes,
>whatever necessary to keep them healthy. 
>
>But at least I'm up and operating for now...............