Vista and XP network - computers can't see each other

> Do a simple test. Can you ping each other by IP?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
> news:0EEBC27D-7FC7-47F2-B6DA-2DDB17A910C2@microsoft.com...

>> Hi all,
>>
>> I have a home office network with one new Dell laptop with Windows Vista
>> Home Basic which I bought a couple of weeks ago, one desktop with Windows
>> XP
>> Pro and one older laptop with Windows XP Pro. The laptops are connected
>> wirelessly, the desktop is using a wired Ethernet connection.
>>
>> Obviously, there have been never a problem with XP machines. Initially,
>> the
>> Vista machine was also able to connect to everybody else. I didn't even
>> bother to look at the settings because everything worked. Then I went to
>> a
>> business trip, and connected to other networks, including wireless public
>> ones in the airports. When I came back, I was unable to share files or
>> even
>> see other computers on the LAN. The internet connection is working fine
>> though. Oh yes, and I also installed a couple of updates, probably some
>> of
>> those constituting Service Pack 1 as well.
>>
>> When I checked the network, to my surprise, it turned out that it became
>> "Public" (could this be "guilt by association" - the airport wireless
>> networks are public, so my home network is public, too?). I changed it to
>> "Private". Didn't help. Checked shares, made sure that the users have the
>> same passwords. Ditto. I deleted the history of the airport networks.
>> Still
>> the same.
>>
>> I am not using Windows Firewalls neither Symantec stuff on any of the
>> machines.
>>
>> I went to PChuck's website at http://networking.nitecruzr.net and tweaked
>> the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
>> disabled IPv6. Nothing. On one point I was able to see the XP machines,
>> but
>> not to browse them (I think the error was "Network name not found"), and
>> then it went back to square one. I switched off both firewalls (Kerio on
>> XP,
>> Comodo on Vista) - nothing. Pinging an IP works, so this is probably
>> something about the name resolution?
>>
>> And, there was a strange event entry on one point:
>>
>> The master browser has received a server announcement from the computer
>> DEVSERVER [that's an XP machine] that believes that it is the master
>> browser
>> for the domain on transport
>> NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
>> The master browser is stopping or an election is being forced.
>>
>>
>> I attached the logs that PChuck asked for diagnosis. As you can see,
>> browstat on Vista machine doesn't work.
>>
>> Help is much appreciated.
>>
>> Best regards,
>> Vadim Berman
>>

>

> Do a simple test. Can you ping each other by IP?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
> news:0EEBC27D-7FC7-47F2-B6DA-2DDB17A910C2@microsoft.com...

>> Hi all,
>>
>> I have a home office network with one new Dell laptop with Windows Vista
>> Home Basic which I bought a couple of weeks ago, one desktop with Windows
>> XP
>> Pro and one older laptop with Windows XP Pro. The laptops are connected
>> wirelessly, the desktop is using a wired Ethernet connection.
>>
>> Obviously, there have been never a problem with XP machines. Initially,
>> the
>> Vista machine was also able to connect to everybody else. I didn't even
>> bother to look at the settings because everything worked. Then I went to
>> a
>> business trip, and connected to other networks, including wireless public
>> ones in the airports. When I came back, I was unable to share files or
>> even
>> see other computers on the LAN. The internet connection is working fine
>> though. Oh yes, and I also installed a couple of updates, probably some
>> of
>> those constituting Service Pack 1 as well.
>>
>> When I checked the network, to my surprise, it turned out that it became
>> "Public" (could this be "guilt by association" - the airport wireless
>> networks are public, so my home network is public, too?). I changed it to
>> "Private". Didn't help. Checked shares, made sure that the users have the
>> same passwords. Ditto. I deleted the history of the airport networks.
>> Still
>> the same.
>>
>> I am not using Windows Firewalls neither Symantec stuff on any of the
>> machines.
>>
>> I went to PChuck's website at http://networking.nitecruzr.net and tweaked
>> the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
>> disabled IPv6. Nothing. On one point I was able to see the XP machines,
>> but
>> not to browse them (I think the error was "Network name not found"), and
>> then it went back to square one. I switched off both firewalls (Kerio on
>> XP,
>> Comodo on Vista) - nothing. Pinging an IP works, so this is probably
>> something about the name resolution?
>>
>> And, there was a strange event entry on one point:
>>
>> The master browser has received a server announcement from the computer
>> DEVSERVER [that's an XP machine] that believes that it is the master
>> browser
>> for the domain on transport
>> NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
>> The master browser is stopping or an election is being forced.
>>
>>
>> I attached the logs that PChuck asked for diagnosis. As you can see,
>> browstat on Vista machine doesn't work.
>>
>> Help is much appreciated.
>>
>> Best regards,
>> Vadim Berman
>>

>

> A-ha!
>
> I went according to your step by step troubleshooting guide here:
> http://www.howtonetworking.com/Troub...cessibale0.htm
>
> and on this page:
> http://www.howtonetworking.com/Troub...essibalec1.htm
> with new view <IP> it stumbles and falls with error 53.
>
> I went to check the event log, and it says: "Unable to load
> C:\Windows\System32\iprtrmgr.dll." and further "The Routing and Remote
> Access service terminated with service-specific error 183 (0xB7)."
>
> Obviously, no matter how hard I try to start Routing and Remote Access, it
> doesn't start! This must be it, right?
>
> I wonder how I fix it though... I downloaded something called rarepair.exe,
> but it didn't help :-( .
>
>
>
>
> "Robert L. (MS-MVP)" <blinNoEmailPlease@mvps.org> wrote in message
> news:u6qy7DcpIHA.2292@TK2MSFTNGP03.phx.gbl...

> > Do a simple test. Can you ping each other by IP?
> >
> > --
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on
> > http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on
> > http://www.HowToNetworking.com
> > "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
> > news:0EEBC27D-7FC7-47F2-B6DA-2DDB17A910C2@microsoft.com...

> >> Hi all,
> >>
> >> I have a home office network with one new Dell laptop with Windows Vista
> >> Home Basic which I bought a couple of weeks ago, one desktop with Windows
> >> XP
> >> Pro and one older laptop with Windows XP Pro. The laptops are connected
> >> wirelessly, the desktop is using a wired Ethernet connection.
> >>
> >> Obviously, there have been never a problem with XP machines. Initially,
> >> the
> >> Vista machine was also able to connect to everybody else. I didn't even
> >> bother to look at the settings because everything worked. Then I went to
> >> a
> >> business trip, and connected to other networks, including wireless public
> >> ones in the airports. When I came back, I was unable to share files or
> >> even
> >> see other computers on the LAN. The internet connection is working fine
> >> though. Oh yes, and I also installed a couple of updates, probably some
> >> of
> >> those constituting Service Pack 1 as well.
> >>
> >> When I checked the network, to my surprise, it turned out that it became
> >> "Public" (could this be "guilt by association" - the airport wireless
> >> networks are public, so my home network is public, too?). I changed it to
> >> "Private". Didn't help. Checked shares, made sure that the users have the
> >> same passwords. Ditto. I deleted the history of the airport networks.
> >> Still
> >> the same.
> >>
> >> I am not using Windows Firewalls neither Symantec stuff on any of the
> >> machines.
> >>
> >> I went to PChuck's website at http://networking.nitecruzr.net and tweaked
> >> the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
> >> disabled IPv6. Nothing. On one point I was able to see the XP machines,
> >> but
> >> not to browse them (I think the error was "Network name not found"), and
> >> then it went back to square one. I switched off both firewalls (Kerio on
> >> XP,
> >> Comodo on Vista) - nothing. Pinging an IP works, so this is probably
> >> something about the name resolution?
> >>
> >> And, there was a strange event entry on one point:
> >>
> >> The master browser has received a server announcement from the computer
> >> DEVSERVER [that's an XP machine] that believes that it is the master
> >> browser
> >> for the domain on transport
> >> NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
> >> The master browser is stopping or an election is being forced.
> >>
> >>
> >> I attached the logs that PChuck asked for diagnosis. As you can see,
> >> browstat on Vista machine doesn't work.
> >>
> >> Help is much appreciated.
> >>
> >> Best regards,
> >> Vadim Berman
> >>

> >

>
>

> A-ha!
>
> I went according to your step by step troubleshooting guide here:
> http://www.howtonetworking.com/Troub...cessibale0.htm
>
> and on this page:
> http://www.howtonetworking.com/Troub...essibalec1.htm
> with new view <IP> it stumbles and falls with error 53.
>
> I went to check the event log, and it says: "Unable to load
> C:\Windows\System32\iprtrmgr.dll." and further "The Routing and Remote
> Access service terminated with service-specific error 183 (0xB7)."
>
> Obviously, no matter how hard I try to start Routing and Remote Access, it
> doesn't start! This must be it, right?
>
> I wonder how I fix it though... I downloaded something called
> rarepair.exe, but it didn't help :-( .
>
>
>
>
> "Robert L. (MS-MVP)" <blinNoEmailPlease@mvps.org> wrote in message
> news:u6qy7DcpIHA.2292@TK2MSFTNGP03.phx.gbl...

>> Do a simple test. Can you ping each other by IP?
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
>> news:0EEBC27D-7FC7-47F2-B6DA-2DDB17A910C2@microsoft.com...

>>> Hi all,
>>>
>>> I have a home office network with one new Dell laptop with Windows Vista
>>> Home Basic which I bought a couple of weeks ago, one desktop with
>>> Windows
>>> XP
>>> Pro and one older laptop with Windows XP Pro. The laptops are connected
>>> wirelessly, the desktop is using a wired Ethernet connection.
>>>
>>> Obviously, there have been never a problem with XP machines. Initially,
>>> the
>>> Vista machine was also able to connect to everybody else. I didn't even
>>> bother to look at the settings because everything worked. Then I went to
>>> a
>>> business trip, and connected to other networks, including wireless
>>> public
>>> ones in the airports. When I came back, I was unable to share files or
>>> even
>>> see other computers on the LAN. The internet connection is working fine
>>> though. Oh yes, and I also installed a couple of updates, probably some
>>> of
>>> those constituting Service Pack 1 as well.
>>>
>>> When I checked the network, to my surprise, it turned out that it became
>>> "Public" (could this be "guilt by association" - the airport wireless
>>> networks are public, so my home network is public, too?). I changed it
>>> to
>>> "Private". Didn't help. Checked shares, made sure that the users have
>>> the
>>> same passwords. Ditto. I deleted the history of the airport networks.
>>> Still
>>> the same.
>>>
>>> I am not using Windows Firewalls neither Symantec stuff on any of the
>>> machines.
>>>
>>> I went to PChuck's website at http://networking.nitecruzr.net and
>>> tweaked
>>> the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
>>> disabled IPv6. Nothing. On one point I was able to see the XP machines,
>>> but
>>> not to browse them (I think the error was "Network name not found"), and
>>> then it went back to square one. I switched off both firewalls (Kerio on
>>> XP,
>>> Comodo on Vista) - nothing. Pinging an IP works, so this is probably
>>> something about the name resolution?
>>>
>>> And, there was a strange event entry on one point:
>>>
>>> The master browser has received a server announcement from the computer
>>> DEVSERVER [that's an XP machine] that believes that it is the master
>>> browser
>>> for the domain on transport
>>> NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
>>> The master browser is stopping or an election is being forced.
>>>
>>>
>>> I attached the logs that PChuck asked for diagnosis. As you can see,
>>> browstat on Vista machine doesn't work.
>>>
>>> Help is much appreciated.
>>>
>>> Best regards,
>>> Vadim Berman
>>>

>>

>

> If you can ping but net view receives System error 53, it could be the
> firewall issue. You also mentioned you don't use any firewall. For
> troubleshooting, start the safe mode with network. Can you net view it?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
> news:uxV$fHepIHA.2188@TK2MSFTNGP04.phx.gbl...

>> A-ha!
>>
>> I went according to your step by step troubleshooting guide here:
>> http://www.howtonetworking.com/Troub...cessibale0.htm
>>
>> and on this page:
>> http://www.howtonetworking.com/Troub...essibalec1.htm
>> with new view <IP> it stumbles and falls with error 53.
>>
>> I went to check the event log, and it says: "Unable to load
>> C:\Windows\System32\iprtrmgr.dll." and further "The Routing and Remote
>> Access service terminated with service-specific error 183 (0xB7)."
>>
>> Obviously, no matter how hard I try to start Routing and Remote Access,
>> it doesn't start! This must be it, right?
>>
>> I wonder how I fix it though... I downloaded something called
>> rarepair.exe, but it didn't help :-( .
>>
>>
>>
>>
>> "Robert L. (MS-MVP)" <blinNoEmailPlease@mvps.org> wrote in message
>> news:u6qy7DcpIHA.2292@TK2MSFTNGP03.phx.gbl...

>>> Do a simple test. Can you ping each other by IP?
>>>
>>> --
>>> Bob Lin, MS-MVP, MCSE & CNE
>>> Networking, Internet, Routing, VPN Troubleshooting on
>>> http://www.ChicagoTech.net
>>> How to Setup Windows, Network, VPN & Remote Access on
>>> http://www.HowToNetworking.com
>>> "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
>>> news:0EEBC27D-7FC7-47F2-B6DA-2DDB17A910C2@microsoft.com...
>>>> Hi all,
>>>>
>>>> I have a home office network with one new Dell laptop with Windows
>>>> Vista
>>>> Home Basic which I bought a couple of weeks ago, one desktop with
>>>> Windows
>>>> XP
>>>> Pro and one older laptop with Windows XP Pro. The laptops are connected
>>>> wirelessly, the desktop is using a wired Ethernet connection.
>>>>
>>>> Obviously, there have been never a problem with XP machines. Initially,
>>>> the
>>>> Vista machine was also able to connect to everybody else. I didn't even
>>>> bother to look at the settings because everything worked. Then I went
>>>> to
>>>> a
>>>> business trip, and connected to other networks, including wireless
>>>> public
>>>> ones in the airports. When I came back, I was unable to share files or
>>>> even
>>>> see other computers on the LAN. The internet connection is working fine
>>>> though. Oh yes, and I also installed a couple of updates, probably some
>>>> of
>>>> those constituting Service Pack 1 as well.
>>>>
>>>> When I checked the network, to my surprise, it turned out that it
>>>> became
>>>> "Public" (could this be "guilt by association" - the airport wireless
>>>> networks are public, so my home network is public, too?). I changed it
>>>> to
>>>> "Private". Didn't help. Checked shares, made sure that the users have
>>>> the
>>>> same passwords. Ditto. I deleted the history of the airport networks.
>>>> Still
>>>> the same.
>>>>
>>>> I am not using Windows Firewalls neither Symantec stuff on any of the
>>>> machines.
>>>>
>>>> I went to PChuck's website at http://networking.nitecruzr.net and
>>>> tweaked
>>>> the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
>>>> disabled IPv6. Nothing. On one point I was able to see the XP machines,
>>>> but
>>>> not to browse them (I think the error was "Network name not found"),
>>>> and
>>>> then it went back to square one. I switched off both firewalls (Kerio
>>>> on
>>>> XP,
>>>> Comodo on Vista) - nothing. Pinging an IP works, so this is probably
>>>> something about the name resolution?
>>>>
>>>> And, there was a strange event entry on one point:
>>>>
>>>> The master browser has received a server announcement from the computer
>>>> DEVSERVER [that's an XP machine] that believes that it is the master
>>>> browser
>>>> for the domain on transport
>>>> NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
>>>> The master browser is stopping or an election is being forced.
>>>>
>>>>
>>>> I attached the logs that PChuck asked for diagnosis. As you can see,
>>>> browstat on Vista machine doesn't work.
>>>>
>>>> Help is much appreciated.
>>>>
>>>> Best regards,
>>>> Vadim Berman
>>>>
>>>

>>

>

>I have almost the same identical problem. My system (laptop using wireless
> access and running Vista, desktop using wired acess to network running XP)
> was working perfectly until last night. I was working on adding an
> extender
> to use with Windows Media Center on my laptop. I got it working just fine
> (using an Xbox 360 for the extender), but when I tried to access files on
> my
> desktop or print to either of two network printers, there was no
> connection.
> The desktop sees my laptop but cannot access it. The laptop can see the
> desktop icon but I get an error saying "check the spelling . . ." when I
> try
> to access it. Hope someone can help with these problems.
>
> "Vadim Berman" wrote:
>

>> A-ha!
>>
>> I went according to your step by step troubleshooting guide here:
>> http://www.howtonetworking.com/Troub...cessibale0.htm
>>
>> and on this page:
>> http://www.howtonetworking.com/Troub...essibalec1.htm
>> with new view <IP> it stumbles and falls with error 53.
>>
>> I went to check the event log, and it says: "Unable to load
>> C:\Windows\System32\iprtrmgr.dll." and further "The Routing and Remote
>> Access service terminated with service-specific error 183 (0xB7)."
>>
>> Obviously, no matter how hard I try to start Routing and Remote Access,
>> it
>> doesn't start! This must be it, right?
>>
>> I wonder how I fix it though... I downloaded something called
>> rarepair.exe,
>> but it didn't help :-( .
>>
>>
>>
>>
>> "Robert L. (MS-MVP)" <blinNoEmailPlease@mvps.org> wrote in message
>> news:u6qy7DcpIHA.2292@TK2MSFTNGP03.phx.gbl...

>> > Do a simple test. Can you ping each other by IP?
>> >
>> > --
>> > Bob Lin, MS-MVP, MCSE & CNE
>> > Networking, Internet, Routing, VPN Troubleshooting on
>> > http://www.ChicagoTech.net
>> > How to Setup Windows, Network, VPN & Remote Access on
>> > http://www.HowToNetworking.com
>> > "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
>> > news:0EEBC27D-7FC7-47F2-B6DA-2DDB17A910C2@microsoft.com...
>> >> Hi all,
>> >>
>> >> I have a home office network with one new Dell laptop with Windows
>> >> Vista
>> >> Home Basic which I bought a couple of weeks ago, one desktop with
>> >> Windows
>> >> XP
>> >> Pro and one older laptop with Windows XP Pro. The laptops are
>> >> connected
>> >> wirelessly, the desktop is using a wired Ethernet connection.
>> >>
>> >> Obviously, there have been never a problem with XP machines.
>> >> Initially,
>> >> the
>> >> Vista machine was also able to connect to everybody else. I didn't
>> >> even
>> >> bother to look at the settings because everything worked. Then I went
>> >> to
>> >> a
>> >> business trip, and connected to other networks, including wireless
>> >> public
>> >> ones in the airports. When I came back, I was unable to share files or
>> >> even
>> >> see other computers on the LAN. The internet connection is working
>> >> fine
>> >> though. Oh yes, and I also installed a couple of updates, probably
>> >> some
>> >> of
>> >> those constituting Service Pack 1 as well.
>> >>
>> >> When I checked the network, to my surprise, it turned out that it
>> >> became
>> >> "Public" (could this be "guilt by association" - the airport wireless
>> >> networks are public, so my home network is public, too?). I changed it
>> >> to
>> >> "Private". Didn't help. Checked shares, made sure that the users have
>> >> the
>> >> same passwords. Ditto. I deleted the history of the airport networks.
>> >> Still
>> >> the same.
>> >>
>> >> I am not using Windows Firewalls neither Symantec stuff on any of the
>> >> machines.
>> >>
>> >> I went to PChuck's website at http://networking.nitecruzr.net and
>> >> tweaked
>> >> the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
>> >> disabled IPv6. Nothing. On one point I was able to see the XP
>> >> machines,
>> >> but
>> >> not to browse them (I think the error was "Network name not found"),
>> >> and
>> >> then it went back to square one. I switched off both firewalls (Kerio
>> >> on
>> >> XP,
>> >> Comodo on Vista) - nothing. Pinging an IP works, so this is probably
>> >> something about the name resolution?
>> >>
>> >> And, there was a strange event entry on one point:
>> >>
>> >> The master browser has received a server announcement from the
>> >> computer
>> >> DEVSERVER [that's an XP machine] that believes that it is the master
>> >> browser
>> >> for the domain on transport
>> >> NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
>> >> The master browser is stopping or an election is being forced.
>> >>
>> >>
>> >> I attached the logs that PChuck asked for diagnosis. As you can see,
>> >> browstat on Vista machine doesn't work.
>> >>
>> >> Help is much appreciated.
>> >>
>> >> Best regards,
>> >> Vadim Berman
>> >>
>> >

>>
>>

> If you can ping but net view receives System error 53, it could be the
> firewall issue. You also mentioned you don't use any firewall. For
> troubleshooting, start the safe mode with network. Can you net view it?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
> news:uxV$fHepIHA.2188@TK2MSFTNGP04.phx.gbl...

>> A-ha!
>>
>> I went according to your step by step troubleshooting guide here:
>> http://www.howtonetworking.com/Troub...cessibale0.htm
>>
>> and on this page:
>> http://www.howtonetworking.com/Troub...essibalec1.htm
>> with new view <IP> it stumbles and falls with error 53.
>>
>> I went to check the event log, and it says: "Unable to load
>> C:\Windows\System32\iprtrmgr.dll." and further "The Routing and Remote
>> Access service terminated with service-specific error 183 (0xB7)."
>>
>> Obviously, no matter how hard I try to start Routing and Remote Access,
>> it doesn't start! This must be it, right?
>>
>> I wonder how I fix it though... I downloaded something called
>> rarepair.exe, but it didn't help :-( .
>>
>>
>>
>>
>> "Robert L. (MS-MVP)" <blinNoEmailPlease@mvps.org> wrote in message
>> news:u6qy7DcpIHA.2292@TK2MSFTNGP03.phx.gbl...

>>> Do a simple test. Can you ping each other by IP?
>>>
>>> --
>>> Bob Lin, MS-MVP, MCSE & CNE
>>> Networking, Internet, Routing, VPN Troubleshooting on
>>> http://www.ChicagoTech.net
>>> How to Setup Windows, Network, VPN & Remote Access on
>>> http://www.HowToNetworking.com
>>> "Vadim Berman" <vadim.berman@NOSPAMdigitalsonata.com> wrote in message
>>> news:0EEBC27D-7FC7-47F2-B6DA-2DDB17A910C2@microsoft.com...
>>>> Hi all,
>>>>
>>>> I have a home office network with one new Dell laptop with Windows
>>>> Vista
>>>> Home Basic which I bought a couple of weeks ago, one desktop with
>>>> Windows
>>>> XP
>>>> Pro and one older laptop with Windows XP Pro. The laptops are connected
>>>> wirelessly, the desktop is using a wired Ethernet connection.
>>>>
>>>> Obviously, there have been never a problem with XP machines. Initially,
>>>> the
>>>> Vista machine was also able to connect to everybody else. I didn't even
>>>> bother to look at the settings because everything worked. Then I went
>>>> to
>>>> a
>>>> business trip, and connected to other networks, including wireless
>>>> public
>>>> ones in the airports. When I came back, I was unable to share files or
>>>> even
>>>> see other computers on the LAN. The internet connection is working fine
>>>> though. Oh yes, and I also installed a couple of updates, probably some
>>>> of
>>>> those constituting Service Pack 1 as well.
>>>>
>>>> When I checked the network, to my surprise, it turned out that it
>>>> became
>>>> "Public" (could this be "guilt by association" - the airport wireless
>>>> networks are public, so my home network is public, too?). I changed it
>>>> to
>>>> "Private". Didn't help. Checked shares, made sure that the users have
>>>> the
>>>> same passwords. Ditto. I deleted the history of the airport networks.
>>>> Still
>>>> the same.
>>>>
>>>> I am not using Windows Firewalls neither Symantec stuff on any of the
>>>> machines.
>>>>
>>>> I went to PChuck's website at http://networking.nitecruzr.net and
>>>> tweaked
>>>> the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
>>>> disabled IPv6. Nothing. On one point I was able to see the XP machines,
>>>> but
>>>> not to browse them (I think the error was "Network name not found"),
>>>> and
>>>> then it went back to square one. I switched off both firewalls (Kerio
>>>> on
>>>> XP,
>>>> Comodo on Vista) - nothing. Pinging an IP works, so this is probably
>>>> something about the name resolution?
>>>>
>>>> And, there was a strange event entry on one point:
>>>>
>>>> The master browser has received a server announcement from the computer
>>>> DEVSERVER [that's an XP machine] that believes that it is the master
>>>> browser
>>>> for the domain on transport
>>>> NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
>>>> The master browser is stopping or an election is being forced.
>>>>
>>>>
>>>> I attached the logs that PChuck asked for diagnosis. As you can see,
>>>> browstat on Vista machine doesn't work.
>>>>
>>>> Help is much appreciated.
>>>>
>>>> Best regards,
>>>> Vadim Berman
>>>>
>>>

>>

>

>Hi all,
>
>I have a home office network with one new Dell laptop with Windows Vista
>Home Basic which I bought a couple of weeks ago, one desktop with Windows XP
>Pro and one older laptop with Windows XP Pro. The laptops are connected
>wirelessly, the desktop is using a wired Ethernet connection.
>
>Obviously, there have been never a problem with XP machines. Initially, the
>Vista machine was also able to connect to everybody else. I didn't even
>bother to look at the settings because everything worked. Then I went to a
>business trip, and connected to other networks, including wireless public
>ones in the airports. When I came back, I was unable to share files or even
>see other computers on the LAN. The internet connection is working fine
>though. Oh yes, and I also installed a couple of updates, probably some of
>those constituting Service Pack 1 as well.
>
>When I checked the network, to my surprise, it turned out that it became
>"Public" (could this be "guilt by association" - the airport wireless
>networks are public, so my home network is public, too?). I changed it to
>"Private". Didn't help. Checked shares, made sure that the users have the
>same passwords. Ditto. I deleted the history of the airport networks. Still
>the same.
>
>I am not using Windows Firewalls neither Symantec stuff on any of the
>machines.
>
>I went to PChuck's website at http://networking.nitecruzr.net and tweaked
>the registry as he suggested, explicitly enabled NetBIOS over TCP/IP,
>disabled IPv6. Nothing. On one point I was able to see the XP machines, but
>not to browse them (I think the error was "Network name not found"), and
>then it went back to square one. I switched off both firewalls (Kerio on XP,
>Comodo on Vista) - nothing. Pinging an IP works, so this is probably
>something about the name resolution?
>
>And, there was a strange event entry on one point:
>
>The master browser has received a server announcement from the computer
>DEVSERVER [that's an XP machine] that believes that it is the master browser
>for the domain on transport NetBT_Tcpip_{65D5631D-9BA7-4E7B-8188-8DFA3FBA.
>The master browser is stopping or an election is being forced.
>
>
>I attached the logs that PChuck asked for diagnosis. As you can see,
>browstat on Vista machine doesn't work.
>
>Help is much appreciated.
>
> Best regards,
> Vadim Berman