Weird xp network problem..

[Gareee©]

Hey guys.. this is a weird one, and I haven;t found a solution for it yet.

I have 3 systems, 2 xp home, and one xp media edition (looks like pro)

I have a linksys router, and wirewalls are off on all 3 systems.

If I open my workgroup computers, I get a message that mshome is not
working, or that I need admin access.

If I search though for each of the other systems, I can access them without
any problems at all!

And this exact same behaviour occurs on each system.

I've tried the "repair" option, and that has no effect at all.

I also tried removing them, and using thw wizard again, and no luck.

Any clues what's going on, and how to fix this?

 

[Chuck]

Hey guys.. this is a weird one, and I haven;t found a solution for it yet.

I have 3 systems, 2 xp home, and one xp media edition (looks like pro)

I have a linksys router, and wirewalls are off on all 3 systems.

If I open my workgroup computers, I get a message that mshome is not
working, or that I need admin access.

If I search though for each of the other systems, I can access them without
any problems at all!

And this exact same behaviour occurs on each system.

I've tried the "repair" option, and that has no effect at all.

I also tried removing them, and using thw wizard again, and no luck.

Any clues what's going on, and how to fix this?

Gary,

Have you setup file sharing properly between the 3 otherwise? Can you open
files after searching?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>

Please provide "browstat status" and "ipconfig /all" from each computer, and
we'll diagnose the problem. Read this article, and linked articles, and follow
instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

 

[Gareee©]

Gary,

Have you setup file sharing properly between the 3 otherwise? Can you
open
files after searching?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>

Yep, without any problems at all. It's just annoying that I have to search
for the systems every time.

Please provide "browstat status" and "ipconfig /all" from each computer,
and
we'll diagnose the problem.

I get a Unrecognizable command when I try the browstat stuff. Do I need to
download and install that separately?


Here's the ipconfig from 2 of the systems. (if I can work it out on two, I'd
like to try to fix it on the 3rd myself, for the learning experience.
------------------------------------------------------------------

System 1 (xp media version/pro):


Windows IP Configuration



Host Name . . . . . . . . . . . . : HP64

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ash.nc.charter.com



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : ash.nc.charter.com

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-13-D3-21-0A-87

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.110

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 24.197.96.16

24.197.96.32

Lease Obtained. . . . . . . . . . : Tuesday, August 09, 2005 7:51:17
AM

Lease Expires . . . . . . . . . . : Wednesday, August 10, 2005
7:51:17 AM

--------------------------------------------------------------------------------------------------------------------------

Second ip config info, xp home system
(not sure why the format came in differently.)
------------------------------------------------------------------------------------------------------------------------------

Windows IP Configuration
Host Name . . . . . . . . . . . . : Nebula
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ash.nc.charter.com

Ethernet adapter Local Area Connection:


Connection-specific DNS Suffix . : ash.nc.charter.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-07-E9-AD-0D-91
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.197.96.16
24.197.96.32
Lease Obtained. . . . . . . . . . : Tuesday, August 09, 2005 7:51:52
AM
Lease Expires . . . . . . . . . . : Wednesday, August 10, 2005
7:51:52 AM

 

[Chuck]

Yep, without any problems at all. It's just annoying that I have to search
for the systems every time.


I get a Unrecognizable command when I try the browstat stuff. Do I need to
download and install that separately?


Here's the ipconfig from 2 of the systems. (if I can work it out on two, I'd
like to try to fix it on the 3rd myself, for the learning experience.

Gary,

<SNIP>

I'll give you all the learning you need. Here are articles on browstat (that
you DO need to download separately, and hopefully install into a Path folder)
and ipconfig.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html>
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
<http://nitecruzr.blogspot.com/2005/05/using-path-and-making-custom-program.html>
<http://nitecruzr.blogspot.com/2005/06/command-window.html#Redirected>

 

[Gareee©]

Gary,

<SNIP>

I'll give you all the learning you need. Here are articles on browstat
(that
you DO need to download separately, and hopefully install into a Path
folder)
and ipconfig.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html>
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
<http://nitecruzr.blogspot.com/2005/05/using-path-and-making-custom-program.html>
<http://nitecruzr.blogspot.com/2005/06/command-window.html#Redirected>

I wasn't hoping to try to figure it out myself.. I've been attempting that
for the last 6 months or so, and had given up.

If what's wrong between these two systems can be pointed out, then i should
be able to correct the third system myself.

Since I work online, and use these two systems for my work, I will NOT just
be tinkering around myself hoping I can figure things out. I'd about given
up on correcting the network a few months ago, but adding a third system has
brought the issue up again here.

What I don't get (and this seems pretty basic), is if the network wizard
completes properly (which it appears to), then why aren't the networks on
these set up properly?

It just seems like bad form to build a wizard for creating a network into
XP, and then on 3 complete installs of the network, to have it not work
properly on every single one.

If it doesn't work, fix the dang thing.

At any rate, from looking at the ipconfig info I previously posted, can you
see what the problem is, and what the cure is?

 

[Chuck]

I wasn't hoping to try to figure it out myself.. I've been attempting that
for the last 6 months or so, and had given up.

If what's wrong between these two systems can be pointed out, then i should
be able to correct the third system myself.

Since I work online, and use these two systems for my work, I will NOT just
be tinkering around myself hoping I can figure things out. I'd about given
up on correcting the network a few months ago, but adding a third system has
brought the issue up again here.

What I don't get (and this seems pretty basic), is if the network wizard
completes properly (which it appears to), then why aren't the networks on
these set up properly?

It just seems like bad form to build a wizard for creating a network into
XP, and then on 3 complete installs of the network, to have it not work
properly on every single one.

If it doesn't work, fix the dang thing.

At any rate, from looking at the ipconfig info I previously posted, can you
see what the problem is, and what the cure is?

Gary,

What I see so far:
# Both computer on the same subnet (192.168.1/24).
# Neither computer have IPV6.
# Both computers with Node Type Hybrid.
# Both computers getting DHCP settings, from same server 192.168.1.1.
# Both computers have the same DNS settings.

IOW, inconclusive determination. Maybe some clues in browstat. Maybe some
clues in diagnostics from the other computer.

Now, I have written dozens of times in various discussions how simple file
sharing looks, and how fscking complex it really is. I guess it's time for me
to write something definitive so you can read it.

A couple times / week, somebody gets in here and screams how messed up file
sharing is (her / his file sharing anyway) and implies the problem would be
really simple to fix, if Microsoft would get it right.

It isn't simple at all.

Anyway, work with me, and once we figure out YOUR problem we'll see if you think
it's simple then.

But read my browstat and ipconfig articles, and read about CDiag, that we'll run
soon. And read about Windows Networking, and about File Sharing.
<http://nitecruzr.blogspot.com/2005/05/using-cdiag-without-assistance.html>
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>
Then post "ipconfig /all" for the other computer, and "browstat status" for all
3 computers, and we'll see what we see.

 

[Gareee©]

What I see so far:
# Both computer on the same subnet (192.168.1/24).
# Neither computer have IPV6.
# Both computers with Node Type Hybrid.
# Both computers getting DHCP settings, from same server 192.168.1.1.
# Both computers have the same DNS settings.

IOW, inconclusive determination. Maybe some clues in browstat. Maybe
some
clues in diagnostics from the other computer.

Now, I have written dozens of times in various discussions how simple file
sharing looks, and how fscking complex it really is. I guess it's time
for me
to write something definitive so you can read it.

A couple times / week, somebody gets in here and screams how messed up
file
sharing is (her / his file sharing anyway) and implies the problem would
be
really simple to fix, if Microsoft would get it right.

It isn't simple at all.

Sorry if I came off harsh, but it must be fairly common to have exact same
systems with the exact same install, hooked up through a linksys router.
(Two of the systems are literally ideantical, with the exception of
installed new non network specific software.) The network was the first
thing we setup, and it had the same issue right off the bat.

it might be a common issue for linksys owners, but googling at trying to
follow web page assistance hasn't hlped at all.

Anyway, work with me, and once we figure out YOUR problem we'll see if you
think
it's simple then.

Will do. I'll download browstat tonight, install it properly on all 3
systems, and grab all the details from it and reply with everything in one
post, to try to make it easier to troubleshoot.

I *do* appreciate the assistance Chuck, and don't want you to think I was
just flaming off my arse.

 

[Chuck]

Sorry if I came off harsh, but it must be fairly common to have exact same
systems with the exact same install, hooked up through a linksys router.
(Two of the systems are literally ideantical, with the exception of
installed new non network specific software.) The network was the first
thing we setup, and it had the same issue right off the bat.

it might be a common issue for linksys owners, but googling at trying to
follow web page assistance hasn't hlped at all.


Will do. I'll download browstat tonight, install it properly on all 3
systems, and grab all the details from it and reply with everything in one
post, to try to make it easier to troubleshoot.

I *do* appreciate the assistance Chuck, and don't want you to think I was
just flaming off my arse.

Gary,

We've all been there, believe me. I curse at my computer daily. It doesn't fix
the problems though - I have to figure them out myself, which makes me feel
better about myself. And helps me understand my customers just a bit.

And I know your frustration with Googling. The jerks who love to answer every
post with "Google is your friend" are right at the top of my shite list.

The Linksys is just a piece of the network, though we shouldn't ignore it.
We'll see what the other diagnostics show though.

 

[Gareee©]

OK Chuck, here's all the info. More Weirdness gets even weirder though,
because for the first time ever, all 3 systems are showing all available
computers and shared folders! (in other words, it looks like everything is
working properly for the first time!)

Go figger. Maybe it's something to do with all three systems needing to be
on at the same time? Or in a certain order? Maybe something is set
incorrectly, so if all 3 systems are NOT on, the network has some issue?


Here's the ipconfig from the systems.

--------------------------------------------------------------------------------------------------------------------------
System 1 (xp media version/pro):
Windows IP Configuration



Host Name . . . . . . . . . . . . : HP64

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ash.nc.charter.com



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : ash.nc.charter.com

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-13-D3-21-0A-87

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.110

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 24.197.96.16

24.197.96.32

Lease Obtained. . . . . . . . . . : Tuesday, August 09, 2005 7:51:17
AM

Lease Expires . . . . . . . . . . : Wednesday, August 10, 2005
7:51:17 AM

--------------------------------------------------------------------------------------------------------------------------
Second ip config info, xp home system


Windows IP Configuration
Host Name . . . . . . . . . . . . : Nebula
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ash.nc.charter.com

Ethernet adapter Local Area Connection:


Connection-specific DNS Suffix . : ash.nc.charter.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-07-E9-AD-0D-91
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.197.96.16
24.197.96.32
Lease Obtained. . . . . . . . . . : Tuesday, August 09, 2005 7:51:52
AM
Lease Expires . . . . . . . . . . : Wednesday, August 10, 2005
7:51:52 AM

-----------------------------------------------------------------------------------------------------------------------------------
System 3:
Host Name . . . . . . . . . . . . : eeyore

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ash.nc.charter.com



Ethernet adapter Marci's connect:



Connection-specific DNS Suffix . : ash.nc.charter.com

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-07-E9-A6-71-DE

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 24.197.96.16

24.197.96.32

Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2005
1:26:11 PM

Lease Expires . . . . . . . . . . : Thursday, August 11, 2005
1:26:11 PM

------------------------------------------------------------------------------------------------------------------------------------------------------

Browstat information:

System 1:

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{F3C96597-AE21-4139-BDAD-527B447B3599}
Browsing is active on domain.
Master browser name is: HP64
Master browser is running build 2600
1 backup servers retrieved from master HP64
\\HP64
There are 3 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{F3C96597-AE21-4139-BDAD-527B447B3599}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{F3C96597-AE21-4139-BDAD-527B447B3599}

------------------------------------------------------------------------------------------------------------------------------------------------------

Browstat system 2:



Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{96D6CD1A-1C3C-469F-A495-11415A2E7EEA}
Browsing is active on domain.
Master browser name is: HP64
Could not open key in registry, error = 5 Unable to determine build
of browser master: 5
\\\\HP64 . Version:05.01 Flags: 51003 NT POTENTIAL MASTER
1 backup servers retrieved from master HP64
\\HP64
There are 3 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{96D6CD1A-1C3C-469F-A495-11415A2E7EEA}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{96D6CD1A-1C3C-469F-A495-11415A2E7EEA}

------------------------------------------------------------------------------------------------------------------------------------------------------

Browstat system 3:


Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{295F6B0E-B5E3-4A0E-B660-9FBD57EB6AE8}
Browsing is active on domain.
Master browser name is: HP64
Could not open key in registry, error = 5 Unable to determine build
of browser master: 5
\\\\HP64 . Version:05.01 Flags: 51003 NT POTENTIAL MASTER
1 backup servers retrieved from master HP64
\\HP64
There are 3 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{295F6B0E-B5E3-4A0E-B660-9FBD57EB6AE8}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{295F6B0E-B5E3-4A0E-B660-9FBD57EB6AE8}

 

[Gareee©]

Oh, and I SWEAR to you, I've never seen any of the systems show in when I
view workgroup computers.. I didn;t even now what the icon looked like until
a few minutes ago!

 

[Chuck]

Oh, and I SWEAR to you, I've never seen any of the systems show in when I
view workgroup computers.. I didn;t even now what the icon looked like until
a few minutes ago!

Gary,

So did you reboot any of the computers just before it all started working?
There's nothing interesting in any of the diagnostics to show a problem either.

Which OS edition (XP Home / XP Pro / XP MCE) do you have on each computer? And
if XP Pro / MCE, is it using Simple or Classic File Sharing?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>

 

[Gareee©]

Gary,

So did you reboot any of the computers just before it all started working?

We usually turn them off every night, and turn them on as needed during the
day. In this case, I turned on system 1 new xp media center pro), then
system 2 (xp home) and then system 3 (xp home)

There's nothing interesting in any of the diagnostics to show a problem
either.
Drat!

Which OS edition (XP Home / XP Pro / XP MCE) do you have on each computer?
And
if XP Pro / MCE, is it using Simple or Classic File Sharing?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>

The new system (xp media center pro) is using the default simple file
sharing.

Before I got this new system (xp pro) we always had the same issue.. with
systems not showing up in workgroup computers, and having to search for
them.

I'll try just booting 2 systems, and see what happens.

Maybe having the pro system on the network somehow resolved the issues
between the two older systems?

 

[Chuck]

We usually turn them off every night, and turn them on as needed during the
day. In this case, I turned on system 1 new xp media center pro), then
system 2 (xp home) and then system 3 (xp home)


The new system (xp media center pro) is using the default simple file
sharing.

Before I got this new system (xp pro) we always had the same issue.. with
systems not showing up in workgroup computers, and having to search for
them.

I'll try just booting 2 systems, and see what happens.

Maybe having the pro system on the network somehow resolved the issues
between the two older systems?

Is HP64 the newer system? It appears to be running the browser, with neither
Eeyore nor Nebula running it. This would mean that neither of the latter could
see each other in Network Neighborhood.

Please read my articles, then check the status of the Browser Service on all 3
computers.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
<http://nitecruzr.blogspot.com/2005/06/services-running-on-your-computer.html>

How long has HP64 been online?

If HP64 is running SFS, that will account for the "error = 5" in browstat on
Eeyore and Nebula.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html>

 

[Gareee©]

On Wed, 10 Aug 2005 15:37:21 -0400, "Gareee©"
<[email protected]>
wrote:
Is HP64 the newer system? It appears to be running the browser, with
neither
Eeyore nor Nebula running it. This would mean that neither of the latter
could
see each other in Network Neighborhood.

I just shut down nebula, and now ms home does not work (as usual) unless I
search.. and again, then it works.

(this is the same on both the hp64 and eeyore systems.)

I'll read your linked articles, and see if there's anything there that will
help.

 

[Gareee©]

I just shut down nebula, and now ms home does not work (as usual) unless I
search.. and again, then it works.

(this is the same on both the hp64 and eeyore systems.)

I'll read your linked articles, and see if there's anything there that
will help.

Oh, and hop64 is brand new, less then a week old.

I just brought nebula back up, (all 3 systems are up), and mshome is not
accessable on any of them, but again, searching locates the accessable
systems.

 

[Chuck]

Oh, and hop64 is brand new, less then a week old.

I just brought nebula back up, (all 3 systems are up), and mshome is not
accessable on any of them, but again, searching locates the accessable
systems.

Gary,

Please list the status (started / stopped) and startup type (auto / manual /
disabled) of the following services on each of the 3 computers:
Computer Browser
Server
TCP/IP NetBIOS Helper
Windows Firewall
Workstation
<http://nitecruzr.blogspot.com/2005/06/services-running-on-your-computer.html>

 

[Gareee©]

On Wed, 10 Aug 2005 18:05:22 -0400, "Gareee©"
<[email protected]>

Please list the status (started / stopped) and startup type (auto / manual
/
disabled) of the following services on each of the 3 computers:

Computer Browser

on each system, it's

started, and automatic

Server

started automatic

TCP/IP NetBIOS Helper

started automatic

Windows Firewall

started automatic

Workstation

started automatic

Also, windows firewall is off on all systems.

 

[Chuck]

on each system, it's

started, and automatic


started automatic


started automatic


started automatic


started automatic

Also, windows firewall is off on all systems.

Is HP64 a domain controller?

 

[Gareee©]

Also, right now all systems are on, and if I open network places, all
folders on every system that are accessable are showing, and can be selected
and browsed.

However if I select workgroup computers, I get the mshome not available
message on nebula and hp64, but eeyore can see all three systems.

color me baffled.


Since things are working weird again, here are new ipconfig and browstat
info for each system.

Typically eeyore is the lest used system (wife's) and is typically not on
during the day, unless I'm testing something.

The boot order for these were:
hp64
nebula
eeyore

nebula shut down, and then restarted.



HP64:
--------------------------------------------------------------------------------------------------------------------------------------
Windows IP Configuration



Host Name . . . . . . . . . . . . : HP64

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ash.nc.charter.com



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : ash.nc.charter.com

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-13-D3-21-0A-87

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.110

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 24.197.96.16

24.197.96.32

Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2005
3:48:56 PM

Lease Expires . . . . . . . . . . : Thursday, August 11, 2005
3:48:56 PM




Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{F3C96597-AE21-4139-BDAD-527B447B3599}
Browsing is active on domain.
Master browser name is: EEYORE
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\EEYORE . Version:05.01 Flags: 71203 NT POTENTIAL BACKUP
MASTER
1 backup servers retrieved from master EEYORE
\\EEYORE
Unable to retrieve server list from EEYORE: 1


--------------------------------------------------------------------------------------------------------------------------------
EEYORE SYSTEM:


Windows IP Configuration



Host Name . . . . . . . . . . . . : eeyore

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ash.nc.charter.com



Ethernet adapter Marci's connect:



Connection-specific DNS Suffix . : ash.nc.charter.com

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-07-E9-A6-71-DE

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 24.197.96.16

24.197.96.32

Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2005
1:26:11 PM

Lease Expires . . . . . . . . . . : Thursday, August 11, 2005
1:26:11 PM




Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{295F6B0E-B5E3-4A0E-B660-9FBD57EB6AE8}
Browsing is active on domain.
Master browser name is: EEYORE
Master browser is running build 2600
1 backup servers retrieved from master EEYORE
\\EEYORE
Unable to retrieve server list from EEYORE: 1

------------------------------------------------------------------------------------------------------------------



Windows IP Configuration



Host Name . . . . . . . . . . . . : Nebula

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : ash.nc.charter.com



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : ash.nc.charter.com

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-07-E9-AD-0D-91

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.101

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 24.197.96.16

24.197.96.32

Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2005
6:02:02 PM

Lease Expires . . . . . . . . . . : Thursday, August 11, 2005
6:02:02 PM



Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{96D6CD1A-1C3C-469F-A495-11415A2E7EEA}
Browsing is active on domain.
Master browser name is: EEYORE
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\EEYORE . Version:05.01 Flags: 71203 NT POTENTIAL BACKUP
MASTER
1 backup servers retrieved from master EEYORE
\\EEYORE
Unable to retrieve server list from EEYORE: 1

 

[Chuck]

Also, right now all systems are on, and if I open network places, all
folders on every system that are accessable are showing, and can be selected
and browsed.

However if I select workgroup computers, I get the mshome not available
message on nebula and hp64, but eeyore can see all three systems.

color me baffled.


Since things are working weird again, here are new ipconfig and browstat
info for each system.

Typically eeyore is the lest used system (wife's) and is typically not on
during the day, unless I'm testing something.

The boot order for these were:
hp64
nebula
eeyore

nebula shut down, and then restarted.



HP64:

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{F3C96597-AE21-4139-BDAD-527B447B3599}
Browsing is active on domain.
Master browser name is: EEYORE
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\EEYORE . Version:05.01 Flags: 71203 NT POTENTIAL BACKUP
MASTER
1 backup servers retrieved from master EEYORE
\\EEYORE
Unable to retrieve server list from EEYORE: 1

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{295F6B0E-B5E3-4A0E-B660-9FBD57EB6AE8}
Browsing is active on domain.
Master browser name is: EEYORE
Master browser is running build 2600
1 backup servers retrieved from master EEYORE
\\EEYORE
Unable to retrieve server list from EEYORE: 1

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{96D6CD1A-1C3C-469F-A495-11415A2E7EEA}
Browsing is active on domain.
Master browser name is: EEYORE
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\EEYORE . Version:05.01 Flags: 71203 NT POTENTIAL BACKUP
MASTER
1 backup servers retrieved from master EEYORE
\\EEYORE
Unable to retrieve server list from EEYORE: 1

OK, as long as all 3 computers are acknowledging the same master browser, then
they'll all be able to see each other. When you get multiple master browsers is
when you have problems.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>

That "error = 53" says that HP64 and Nebula can't resolve Eeyore name to
address. Check:
Misconfigured / overlooked firewalls:
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
Registry setting restrictanonymous:
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>