Mshome is not accessible

  • Thread starter Thread starter techcoor
  • Start date Start date
T

techcoor

When I go into Windows XP SP2 Windows Explorer, My network places, Microsoft
Windows Network, and select the workgroup (MSHOME) I get:

Mshome is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions. The list of servers for this workgroup is not currently
available.

What can I do so I get a list of workgroup computers.

All computers are running Windows XP SP2 and are members of the MSHOME
workgroup with Internet connection through DLINK DI914+ home router.
 
When I go into Windows XP SP2 Windows Explorer, My network places, Microsoft
Windows Network, and select the workgroup (MSHOME) I get:

Mshome is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions. The list of servers for this workgroup is not currently
available.

What can I do so I get a list of workgroup computers.

All computers are running Windows XP SP2 and are members of the MSHOME
workgroup with Internet connection through DLINK DI914+ home router.

You can see your other thread for more advice. Please don't multi-post.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#MultiPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#MultiPosting

--
Cheers,
Chuck, MS-MVP 2005-2007 [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 said:
When I go into Windows XP SP2 Windows Explorer, My network places, Microsoft
Windows Network, and select the workgroup (MSHOME) I get:

Mshome is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions. The list of servers for this workgroup is not currently
available.

What can I do so I get a list of workgroup computers.

All computers are running Windows XP SP2 and are members of the MSHOME
workgroup with Internet connection through DLINK DI914+ home router.

You can see your other thread for more advice. Please don't multi-post.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#MultiPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#MultiPosting

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.
 
(No Reply)

So I'll repeat my advice from the other thread.

Windows XP, as with most other Windows editions, will indeed show the actual
shares, when the computers are setup properly.

You, most likely, have a NetBT setting or personal firewall, problem on one or
more computers.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

You can probably diagnose the problem, using logs from "browstat status",
"ipconfig /all", "net config server", and "net config workstation", from each
computer. 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 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
I don't know what happened to my last response. I didn't keep a record so I
have to go through the steps again.

I looked at the
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#MultiPosting
The link What is cross-posting? How do I do it?
(http://www.uwasa.fi/~ts/http/crospost.html) seems to be broke.
Thanks for the original link. Since I combined what I thought were separate
issues, I will move on.

Currently there are 4 computers which I will name A,B,C and D. D is a
wireless link and the rest are hardwired.
Since we are talking about the Dlink home router, I went and started
clicking the box for Enable NetBIOS over TCP/IP.
Computer C was off. That change didn't help.

When I first ran Browstat Status, the wireless link Computer D was shown to
be the master browser. Both Computer B and D were turned off.
Then Computer B was turned on. At this point, when Browstat Status was run,
I did get the "Could not open key in registry, error = 5
Unable to determine build of brower master: 5.

I tried to go to
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
but it was unavailable. As I remember, Error 5
isn't necessarily a problem.

I checked status. In Windows Explorer My Network Places, I could get to the
Computer A and B shares using either Computer A or B suggesting
the problem is one of the other two computers.

Turned on Computer C and Verified the Enable NetBIOS over TCP/IP box was
checked. Still no MSHOME message.

Turned on Computer D and could see Computer A and B but not C. Went to
Computer A and got the MSHome not accessible meaning Computer D is
the problem. Computer D has Norton Internet Security 2007. Decided to
uninstall Norton Internet Security 2007. Now I can see Computers A,B,C,D.
When I click on Computer D in Computer A I get Dialog box asking for a
password. The Dialog box is a different problem.

I bought in 5th wireless computer E and verified that that Enable NetBIOS
over TCP/IP was checked. That only showed computer D.

Decided to reinstall Norton Internet Security 2007. Now no other computers
show in Computer D network neighborhood. However all other computers
have all five computers. From E can not open computer B and D shares.



Still don't have the MSHOME not accessible message so there is some progress.



Still have computer D doesn't show any other computers.
When Norton Internet security 2007 wasn't installed, computer D wanted a
password.
Computer D and B shares are not accessible.
My Network Places doesn't show the correct shares.

I decided to uninstall Norton Internet security again to try to clear the
dialog box asking for a password. Computer C is turned off and computer
D moved in C's location. Found that still can't access Computer D. Went into
the Windows Firewall and checked File and Printer Sharing. That didn't help.
Turned off Windows firewall. Tried running Network Setup Wizard. That only
got me the Mshome is not accessable message. Deleted the Networking Services.
rechecked Enable NetBios over TCP/IP. That didn't help and I am back to
square one. It will take time to wander around in the reference web site.

Chuck said:
(No Reply)

So I'll repeat my advice from the other thread.

Windows XP, as with most other Windows editions, will indeed show the actual
shares, when the computers are setup properly.

You, most likely, have a NetBT setting or personal firewall, problem on one or
more computers.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

You can probably diagnose the problem, using logs from "browstat status",
"ipconfig /all", "net config server", and "net config workstation", from each
computer. 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 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
I don't know what happened to my last response. I didn't keep a
record so I have to go through the steps again.

I looked at the
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-enc
ourage.html#MultiPosting The link What is cross-posting? How do I
do it? (http://www.uwasa.fi/~ts/http/crospost.html) seems to be
broke. Thanks for the original link. Since I combined what I
thought were separate issues, I will move on.

Currently there are 4 computers which I will name A,B,C and D. D
is a wireless link and the rest are hardwired.
Since we are talking about the Dlink home router, I went and
started clicking the box for Enable NetBIOS over TCP/IP.
Computer C was off. That change didn't help.

When I first ran Browstat Status, the wireless link Computer D was
shown to be the master browser. Both Computer B and D were turned
off. Then Computer B was turned on. At this point, when Browstat
Status was run, I did get the "Could not open key in registry,
error = 5 Unable to determine build of brower master: 5.

I tried to go to
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-u
sing.html but it was unavailable. As I remember, Error 5
isn't necessarily a problem.

I checked status. In Windows Explorer My Network Places, I could
get to the Computer A and B shares using either Computer A or B
suggesting the problem is one of the other two computers.

Turned on Computer C and Verified the Enable NetBIOS over TCP/IP
box was checked. Still no MSHOME message.

Turned on Computer D and could see Computer A and B but not C.
Went to Computer A and got the MSHome not accessible meaning
Computer D is the problem. Computer D has Norton Internet Security
2007. Decided to uninstall Norton Internet Security 2007. Now I
can see Computers A,B,C,D. When I click on Computer D in Computer
A I get Dialog box asking for a password. The Dialog box is a
different problem.

I bought in 5th wireless computer E and verified that that Enable
NetBIOS over TCP/IP was checked. That only showed computer D.

Decided to reinstall Norton Internet Security 2007. Now no other
computers show in Computer D network neighborhood. However all
other computers have all five computers. From E can not open
computer B and D shares.



Still don't have the MSHOME not accessible message so there is
some progress.



Still have computer D doesn't show any other computers.
When Norton Internet security 2007 wasn't installed, computer D
wanted a password.
Computer D and B shares are not accessible.
My Network Places doesn't show the correct shares.

I decided to uninstall Norton Internet security again to try to
clear the dialog box asking for a password. Computer C is turned
off and computer D moved in C's location. Found that still can't
access Computer D. Went into the Windows Firewall and checked File
and Printer Sharing. That didn't help. Turned off Windows
firewall. Tried running Network Setup Wizard. That only got me the
Mshome is not accessable message. Deleted the Networking Services.
rechecked Enable NetBios over TCP/IP. That didn't help and I am
back to square one. It will take time to wander around in the
reference web site.

Wow, what a mess. It sounds like your Norton Internet security is
preventing browsing on the network. Microsoft has a vague reference to
the problem here:

"Internet firewalls can prevent browsing and file sharing"
<http://support.microsoft.com/kb/298804/en-us>

From my experience, you can detect this problem by using browstat to
first find the Master browser using the command:
browstat fm 1
(where "1" is the interface from the "browstat dn" output)
Once you find the master, give the command:
browstat vw 1 \\master 0x40000000
If the output has more than one computer with the "MBR" property, then
one of them has a firewall and is killing the network.
(a similiar test can be run by doing a
nbtstat -a computername
for each 'computername' in your network. Only one should have a line
reading "..__MSBROWSE__." )
If you can't get a master browser, try entering the
"browstat tic 1 MSHome" and/or "browstat el 1 MSHome"
command and wait several seconds to half-minute and try again. The
state where two computers have "MBR" status is not stable and won't
last. The legitimate one invariably drops out and the problem one ends
up winning.

When you remove Norton, you actually get a step closer with the login
screen. What you do not inform us is which of your machines are XP
Home and which are XP Pro and, if XP Pro, is it joined to a domain
(e.g. at work)? Permissions is handled differently between Home and
Pro. When you get the login screen, for username try entering
Computername\Username and the proper password for a valid *local* user
on the Target computer.

Good Luck
HTH,
John
 
I don't know what happened to my last response. I didn't keep a record so I
have to go through the steps again.

I looked at the
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#MultiPosting
The link What is cross-posting? How do I do it?
(http://www.uwasa.fi/~ts/http/crospost.html) seems to be broke.
Thanks for the original link. Since I combined what I thought were separate
issues, I will move on.

Currently there are 4 computers which I will name A,B,C and D. D is a
wireless link and the rest are hardwired.
Since we are talking about the Dlink home router, I went and started
clicking the box for Enable NetBIOS over TCP/IP.
Computer C was off. That change didn't help.

When I first ran Browstat Status, the wireless link Computer D was shown to
be the master browser. Both Computer B and D were turned off.
Then Computer B was turned on. At this point, when Browstat Status was run,
I did get the "Could not open key in registry, error = 5
Unable to determine build of brower master: 5.

I tried to go to
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
but it was unavailable. As I remember, Error 5
isn't necessarily a problem.

I checked status. In Windows Explorer My Network Places, I could get to the
Computer A and B shares using either Computer A or B suggesting
the problem is one of the other two computers.

Turned on Computer C and Verified the Enable NetBIOS over TCP/IP box was
checked. Still no MSHOME message.

Turned on Computer D and could see Computer A and B but not C. Went to
Computer A and got the MSHome not accessible meaning Computer D is
the problem. Computer D has Norton Internet Security 2007. Decided to
uninstall Norton Internet Security 2007. Now I can see Computers A,B,C,D.
When I click on Computer D in Computer A I get Dialog box asking for a
password. The Dialog box is a different problem.

I bought in 5th wireless computer E and verified that that Enable NetBIOS
over TCP/IP was checked. That only showed computer D.

Decided to reinstall Norton Internet Security 2007. Now no other computers
show in Computer D network neighborhood. However all other computers
have all five computers. From E can not open computer B and D shares.



Still don't have the MSHOME not accessible message so there is some progress.



Still have computer D doesn't show any other computers.
When Norton Internet security 2007 wasn't installed, computer D wanted a
password.
Computer D and B shares are not accessible.
My Network Places doesn't show the correct shares.

I decided to uninstall Norton Internet security again to try to clear the
dialog box asking for a password. Computer C is turned off and computer
D moved in C's location. Found that still can't access Computer D. Went into
the Windows Firewall and checked File and Printer Sharing. That didn't help.
Turned off Windows firewall. Tried running Network Setup Wizard. That only
got me the Mshome is not accessable message. Deleted the Networking Services.
rechecked Enable NetBios over TCP/IP. That didn't help and I am back to
square one. It will take time to wander around in the reference web site.

OK, since you say that you did have Norton Internet Security un installed at one
time, and you were able to see all 4 computers, that's where you start. Leave
NIS un installed, until you get this fixed.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

A box asking for a password is another issue. That's authentication. Are your
computers running XP Home, XP Pro with Simple File Sharing, XP Pro with Advanced
File Sharing and Guest access, or XP Pro with AFS and non-Guest access?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
On hom200of002 using net view \\hom200of002 per
http://support.microsoft.com/kb/298804/en-us completes without error.

I get the following with C:\Tmp>browstat fm 1:
Browser: Unable to determine master for network \device\1: 2
Unable to get Master: The system cannot find the file specified.

I get the following with C:\Tmp>browstat vw 1 \\master 0x40000000:
Remoting NetServerEnum to \\master on transport \device\1 with flags 40000000
Unable to remote API to \\master on transport \device\1: The network
location ca
nnot be reached. For information about network troubleshooting, see Windows
Help
..
(0 milliseconds)

I get the following with C:\Tmp>nbtstat -a hom200of002:
Local Area Connection:
Node IpAddress: [192.168.1.100] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
HOM200OF002 <00> UNIQUE Registered
MSHOME <00> GROUP Registered
HOM200OF002 <20> UNIQUE Registered
MSHOME <1E> GROUP Registered
MSHOME <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

MAC Address = 00-13-20-02-43-DD
I don’t see the master browser but browstat status shows it:
Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-98
60-103410E72B58}
Browsing is active on domain.
Master browser name is: HOM200OF002
Master browser is running build 2600
1 backup servers retrieved from master HOM200OF002
\\HOM200OF002
There are 4 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A154
00B-A5AC-407E-9860-103410E72B58}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A154
00B-A5AC-407E-9860-103410E72B58}

All computers are Windows XP Pro SP2 and are in the default windows
workgroup MSHOME.

Tomorrow I will work on taking Norton out again.
 
Using cpsserv as suggested on
http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html, I got the following results:

Computer A
Start CPSServ V1.10 - HOM200OF001

Find Computer Browser ("browser")
Error browsing network:
No active service named browser found.


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named dhcp found.


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named lmhosts found.


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named remoteregistry found.


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named server found.


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named sharedaccess found.


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named workstation found.

End CPSServ V1.10 - HOM200OF001

Computer B

Start CPSServ V1.10 - HOM200OF002

Find Computer Browser ("browser")
Error browsing network:
No active service named browser found.


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found dhcp on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found lmhosts on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Checking \\P933III...Unable to open Service
Control Manager database on \\\P933III:
No active service named remoteregistry found.


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found server on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found sharedaccess on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found workstation on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:

End CPSServ V1.10 - HOM200OF002

Computer C

Start CPSServ V1.10 - P933III

Find Computer Browser ("browser")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found browser on:
\\P933III


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found dhcp on:
\\P933III


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found lmhosts on:
\\P933III


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found remoteregistry on:
\\P933III


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found server on:
\\P933III


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found sharedaccess on:
\\P933III


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found workstation on:
\\P933III

End CPSServ V1.10 - P933III

Computer D

Start CPSServ V1.10 - P933III

Find Computer Browser ("browser")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found browser on:
\\P933III


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found dhcp on:
\\P933III


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found lmhosts on:
\\P933III


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found remoteregistry on:
\\P933III


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found server on:
\\P933III


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found sharedaccess on:
\\P933III


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found workstation on:
\\P933III

End CPSServ V1.10 - P933III

Start CPSServ V1.10 - HOM100FR001

Find Computer Browser ("browser")
Error browsing network:
No active service named browser found.


Find DHCP Client ("dhcp")
Error browsing network:
No active service named dhcp found.


Find TCP/IP NetBIOS Helper ("lmhosts")
Error browsing network:
No active service named lmhosts found.


Find Remote Registry ("remoteregistry")
Error browsing network:
No active service named remoteregistry found.


Find Server ("server")
Error browsing network:
No active service named server found.


Find WF / ICS ("sharedaccess")
Error browsing network:
No active service named sharedaccess found.


Find Workstation ("workstation")
Error browsing network:
No active service named workstation found.

End CPSServ V1.10 - HOM100FR001

I probably should at this point establish a baseline

My Network Places
Hom200of001
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\P933iii\SharedDocs
\\P933iii\tmp

Hom200of002
\\Hom200of001\Image Library (doesn’t exist)
\\Hom200of001\PictureProject (doesn’t exist)
\\Hom200of001\SharedDocs (doesn’t exist)
\\Hom200of001\Storage (doesn’t exist)
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\P933iii\SharedDocs
\\P933iii\tmp
\\Hom200of003\Tmp (Computer is off)

P933iii

\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\P933iii\SharedDocs
\\P933iii\tmp

Hom100fr001
(nothing shows)

My network Places/Entire Network/Microsoft Windows Network/Mshome

Hom200of001, Hom200of002, P933iii show all four computers.
Hom100fr001 gives Mshome is not accessable.

Will plan to remove the Norton’s tomorrow.

All computers are running Windows XP Professional SP2 and are in workgroup
mshome





Chuck said:
I don't know what happened to my last response. I didn't keep a record so I
have to go through the steps again.

I looked at the
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#MultiPosting
The link What is cross-posting? How do I do it?
(http://www.uwasa.fi/~ts/http/crospost.html) seems to be broke.
Thanks for the original link. Since I combined what I thought were separate
issues, I will move on.

Currently there are 4 computers which I will name A,B,C and D. D is a
wireless link and the rest are hardwired.
Since we are talking about the Dlink home router, I went and started
clicking the box for Enable NetBIOS over TCP/IP.
Computer C was off. That change didn't help.

When I first ran Browstat Status, the wireless link Computer D was shown to
be the master browser. Both Computer B and D were turned off.
Then Computer B was turned on. At this point, when Browstat Status was run,
I did get the "Could not open key in registry, error = 5
Unable to determine build of brower master: 5.

I tried to go to
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
but it was unavailable. As I remember, Error 5
isn't necessarily a problem.

I checked status. In Windows Explorer My Network Places, I could get to the
Computer A and B shares using either Computer A or B suggesting
the problem is one of the other two computers.

Turned on Computer C and Verified the Enable NetBIOS over TCP/IP box was
checked. Still no MSHOME message.

Turned on Computer D and could see Computer A and B but not C. Went to
Computer A and got the MSHome not accessible meaning Computer D is
the problem. Computer D has Norton Internet Security 2007. Decided to
uninstall Norton Internet Security 2007. Now I can see Computers A,B,C,D.
When I click on Computer D in Computer A I get Dialog box asking for a
password. The Dialog box is a different problem.

I bought in 5th wireless computer E and verified that that Enable NetBIOS
over TCP/IP was checked. That only showed computer D.

Decided to reinstall Norton Internet Security 2007. Now no other computers
show in Computer D network neighborhood. However all other computers
have all five computers. From E can not open computer B and D shares.



Still don't have the MSHOME not accessible message so there is some progress.



Still have computer D doesn't show any other computers.
When Norton Internet security 2007 wasn't installed, computer D wanted a
password.
Computer D and B shares are not accessible.
My Network Places doesn't show the correct shares.

I decided to uninstall Norton Internet security again to try to clear the
dialog box asking for a password. Computer C is turned off and computer
D moved in C's location. Found that still can't access Computer D. Went into
the Windows Firewall and checked File and Printer Sharing. That didn't help.
Turned off Windows firewall. Tried running Network Setup Wizard. That only
got me the Mshome is not accessable message. Deleted the Networking Services.
rechecked Enable NetBios over TCP/IP. That didn't help and I am back to
square one. It will take time to wander around in the reference web site.

OK, since you say that you did have Norton Internet Security un installed at one
time, and you were able to see all 4 computers, that's where you start. Leave
NIS un installed, until you get this fixed.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

A box asking for a password is another issue. That's authentication. Are your
computers running XP Home, XP Pro with Simple File Sharing, XP Pro with Advanced
File Sharing and Guest access, or XP Pro with AFS and non-Guest access?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.
 
Using cpsserv as suggested on
http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html, I got the following results:

Computer A
Start CPSServ V1.10 - HOM200OF001

Find Computer Browser ("browser")
Error browsing network:
No active service named browser found.


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named dhcp found.


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named lmhosts found.


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named remoteregistry found.


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named server found.


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named sharedaccess found.


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:
No active service named workstation found.

End CPSServ V1.10 - HOM200OF001

Computer B

Start CPSServ V1.10 - HOM200OF002

Find Computer Browser ("browser")
Error browsing network:
No active service named browser found.


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found dhcp on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found lmhosts on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Checking \\P933III...Unable to open Service
Control Manager database on \\\P933III:
No active service named remoteregistry found.


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found server on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found sharedaccess on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002... Found workstation on:
\\HOM200OF002
Checking \\P933III...Unable to open Service Control Manager database on
\\\P933III:

End CPSServ V1.10 - HOM200OF002

Computer C

Start CPSServ V1.10 - P933III

Find Computer Browser ("browser")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found browser on:
\\P933III


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found dhcp on:
\\P933III


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found lmhosts on:
\\P933III


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found remoteregistry on:
\\P933III


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found server on:
\\P933III


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found sharedaccess on:
\\P933III


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found workstation on:
\\P933III

End CPSServ V1.10 - P933III

Computer D

Start CPSServ V1.10 - P933III

Find Computer Browser ("browser")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found browser on:
\\P933III


Find DHCP Client ("dhcp")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found dhcp on:
\\P933III


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found lmhosts on:
\\P933III


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found remoteregistry on:
\\P933III


Find Server ("server")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found server on:
\\P933III


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found sharedaccess on:
\\P933III


Find Workstation ("workstation")
Checking \\HOM100FR001...Unable to open Service Control Manager database on
\\\HOM100FR001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Checking \\P933III... Found workstation on:
\\P933III

End CPSServ V1.10 - P933III

Start CPSServ V1.10 - HOM100FR001

Find Computer Browser ("browser")
Error browsing network:
No active service named browser found.


Find DHCP Client ("dhcp")
Error browsing network:
No active service named dhcp found.


Find TCP/IP NetBIOS Helper ("lmhosts")
Error browsing network:
No active service named lmhosts found.


Find Remote Registry ("remoteregistry")
Error browsing network:
No active service named remoteregistry found.


Find Server ("server")
Error browsing network:
No active service named server found.


Find WF / ICS ("sharedaccess")
Error browsing network:
No active service named sharedaccess found.


Find Workstation ("workstation")
Error browsing network:
No active service named workstation found.

End CPSServ V1.10 - HOM100FR001

I probably should at this point establish a baseline

My Network Places
Hom200of001
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\P933iii\SharedDocs
\\P933iii\tmp

Hom200of002
\\Hom200of001\Image Library (doesn’t exist)
\\Hom200of001\PictureProject (doesn’t exist)
\\Hom200of001\SharedDocs (doesn’t exist)
\\Hom200of001\Storage (doesn’t exist)
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\P933iii\SharedDocs
\\P933iii\tmp
\\Hom200of003\Tmp (Computer is off)

P933iii

\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\P933iii\SharedDocs
\\P933iii\tmp

Hom100fr001
(nothing shows)

My network Places/Entire Network/Microsoft Windows Network/Mshome

Hom200of001, Hom200of002, P933iii show all four computers.
Hom100fr001 gives Mshome is not accessable.

Will plan to remove the Norton’s tomorrow.

All computers are running Windows XP Professional SP2 and are in workgroup
mshome

You have definite problems with Computer A ("No active service named xxxxxxx
found.") and E ("Error browsing network: No active service named xxxxxxx
found.").

Is Norton (or any other personal firewall) installed on either of those? If so,
un install it. If not, look at LSP / Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
On hom200of002 using net view \\hom200of002 per
http://support.microsoft.com/kb/298804/en-us completes without
error.

I get the following with C:\Tmp>browstat fm 1:
Browser: Unable to determine master for network \device\1: 2
Unable to get Master: The system cannot find the file specified.

It looks like you might have an old version of browstat.exe.
If you give the following command and it results in an error, then you have an old version:
browstat dn
In that case, you'll have to do a "browstat sta" as you did below
and record the network name and put that in place of the "1".
For example:
browstat fm NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
I get the following with C:\Tmp>browstat vw 1 \\master 0x40000000:
Remoting NetServerEnum to \\master on transport \device\1 with
flags 40000000 Unable to remote API to \\master on transport
\device\1: The network location ca
nnot be reached. For information about network troubleshooting,
see Windows Help

You were supposed to replace "master" with the name of your browse
master... assuming the older browstat, your command will look
something like:

browstat vw NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58} \\hom200of002 0x40000000

It's a pain to put that network ID in... you might want to look
for a newer browstat...

HTH,
John
I get the following with C:\Tmp>nbtstat -a hom200of002:
Local Area Connection:
Node IpAddress: [192.168.1.100] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
HOM200OF002 <00> UNIQUE Registered
MSHOME <00> GROUP Registered
HOM200OF002 <20> UNIQUE Registered
MSHOME <1E> GROUP Registered
MSHOME <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

MAC Address = 00-13-20-02-43-DD
I don’t see the master browser but browstat status shows it:
Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-98
60-103410E72B58}
Browsing is active on domain.
Master browser name is: HOM200OF002
Master browser is running build 2600
1 backup servers retrieved from master HOM200OF002
\\HOM200OF002
There are 4 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}

All computers are Windows XP Pro SP2 and are in the default
windows workgroup MSHOME.
 
Browstat dn gets me:
List of transports currently bound to the browser

1 \Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}

Therefore I will assume the next step is Browstat fm
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58} which gets me:

Browser: Unable to determine master for network
\Device\NetBT_Tcpip_{6A15400B-A5
AC-407E-9860-103410E72B58}: 234
Unable to get Master: More data is available.
browstat vw NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58} \\hom200of002
0x40000000 gets me:
Remoting NetServerEnum to \\hom200of002 on transport
\device\NetBT_Tcpip_{6A1540
0B-A5AC-407E-9860-103410E72B58} with flags 40000000
4 entries returned. 4 total. 0 milliseconds

\\HOM100FR001 NT 05.01 (W,S,NT,PBR,MBR)
\\HOM200OF001 NT 05.01 (W,S,PQ,NT,PBR)
\\HOM200OF002 NT 05.01 (W,S,DL,NT,PBR,MBR)
\\P933III NT 05.01 (W,S,PQ,NT,PBR) test

Browstat status gets me:

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-98
60-103410E72B58}
Browsing is active on domain.
Master browser name is: HOM200OF002
Master browser is running build 2600
1 backup servers retrieved from master HOM200OF002
\\HOM200OF002
There are 4 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A154
00B-A5AC-407E-9860-103410E72B58}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A154
00B-A5AC-407E-9860-103410E72B58}

I did uninstall Norton Internet Security 2007 from computer B hom200of002
and computer D hom100fr001 and that removed the Mshome is not accessible
problem. The uninstalled didn't change that computer B still shows My network
Places shares that don't exist that were there originally but does show the
turned off computer C P933iii shares with a unknown computer. Maybe the
nonexisting shares are still an effect of Norton Internet security 2007 that
will have to be manually removed.


John Wunderlich said:
On hom200of002 using net view \\hom200of002 per
http://support.microsoft.com/kb/298804/en-us completes without
error.

I get the following with C:\Tmp>browstat fm 1:
Browser: Unable to determine master for network \device\1: 2
Unable to get Master: The system cannot find the file specified.

It looks like you might have an old version of browstat.exe.
If you give the following command and it results in an error, then you have an old version:
browstat dn
In that case, you'll have to do a "browstat sta" as you did below
and record the network name and put that in place of the "1".
For example:
browstat fm NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
I get the following with C:\Tmp>browstat vw 1 \\master 0x40000000:
Remoting NetServerEnum to \\master on transport \device\1 with
flags 40000000 Unable to remote API to \\master on transport
\device\1: The network location ca
nnot be reached. For information about network troubleshooting,
see Windows Help

You were supposed to replace "master" with the name of your browse
master... assuming the older browstat, your command will look
something like:

browstat vw NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58} \\hom200of002 0x40000000

It's a pain to put that network ID in... you might want to look
for a newer browstat...

HTH,
John
I get the following with C:\Tmp>nbtstat -a hom200of002:
Local Area Connection:
Node IpAddress: [192.168.1.100] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
HOM200OF002 <00> UNIQUE Registered
MSHOME <00> GROUP Registered
HOM200OF002 <20> UNIQUE Registered
MSHOME <1E> GROUP Registered
MSHOME <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

MAC Address = 00-13-20-02-43-DD
I don’t see the master browser but browstat status shows it:
Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-98
60-103410E72B58}
Browsing is active on domain.
Master browser name is: HOM200OF002
Master browser is running build 2600
1 backup servers retrieved from master HOM200OF002
\\HOM200OF002
There are 4 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}

All computers are Windows XP Pro SP2 and are in the default
windows workgroup MSHOME.
 
No computer A hom200of001 does not have a personal firewall. I assume your
next sentence refers to computer D. Yes, computer B hom200of002 and D
hom100of001 have Norton Internet Security 2007 and have the most problems.
Computer E was dropped off the network. Computer C P933iii will be dropped as
well to simplify things. To further simplify things. Computer D will be moved
from Wireless to wired. It occurred to me that maybe the wireless link is too
slow and Norton Internet Security has decided it is on the network alone and
has clamped things down.

Since I changed things, I will verify I have the same conditions as before.
I see same Windows Explorer Mshome computer icons (even though P933iii
doesn’t exist). My Network Places is the same. I can ping from hom200of002
to hom200of001 but not to hom200fr001. I will remove the results to try to
fit in the space allowed.


Removed Norton Internet Security 2007 computer D hom100fr001.

Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Did not check hom200of002
Computer A can create a file and store it into Computer D through Windows
Explorer Mshome computer icons. Did not check hom200of002
Computer A can ping using ping hom100fr001. Did not check hom200of002


Computer B hom200of002 doesn’t show hom100fr001 in My Network Neighborhood
Computer B can’t access hom100fr001 using Windows Explorer Mshome computer
icons. Get Mshome is not accessible.
Computer B can ping hom100fr001 using the IP address but not using the
computer name.

Computer D doesn’t show anything in My Network Neighborhood
Computer D can’t access Windows Explorer Mshome computer icons. Get Mshome
is not accessible.
Computer D can ping hom200of001 but not hom200of002.

Removed Norton Internet Security 2007 Computer B hom200of002.

Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Computer A can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer A can ping using ping hom100fr001.

Computer B hom200of002 shows hom100fr001 in My Network Neighborhood
Computer B can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer B can ping hom100fr001 and hom200of001 using the computer name.

Computer D shows in My Network Neighborhood
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\Hom100fr001\tmp

Computer D can modified a file on hom200of001 and hom200of002 through
Windows Explorer Mshome computer icons
Computer D can ping hom200of001 and hom200of002 using computer name.

Meantime

Computer B


Computer D

Start CPSServ V1.10 - HOM100FR001

Find Computer Browser ("browser")
Checking \\HOM100FR001... Found browser on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find DHCP Client ("dhcp")
Checking \\HOM100FR001... Found dhcp on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001... Found lmhosts on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001... Found remoteregistry on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find Server ("server")
Checking \\HOM100FR001... Found server on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001... Found sharedaccess on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find Workstation ("workstation")
Checking \\HOM100FR001... Found workstation on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:

End CPSServ V1.10 - HOM100FR001

CDiagnosis V1.40
Start diagnosis for HOM100FR001
Full Targets hom200of001 192.168.1.103 hom200of002 192.168.1.100 hom100fr001
192.168.1.105 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

tmp C:\tmp
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\HOM100FR001

\\HOM200OF001

\\HOM200OF002

The command completed successfully.


Full Targets Analysis hom200of001 192.168.1.103 hom200of002 192.168.1.100
hom100fr001 192.168.1.105 127.0.0.1

Target hom200of001

"HOM100FR001 ping hom200of001"


Pinging hom200of001 [192.168.1.103] with 32 bytes of data:

Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view hom200of001"

Shared resources at hom200of001



Share name Type Used as Comment

-------------------------------------------------------------------------------
PSC2410 Print hp psc 2400 series
tmp Disk (UNC)
The command completed successfully.


Target 192.168.1.103

"HOM100FR001 ping 192.168.1.103"


Pinging 192.168.1.103 with 32 bytes of data:

Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 192.168.1.103"

Shared resources at 192.168.1.103



Share name Type Used as Comment

-------------------------------------------------------------------------------
PSC2410 Print hp psc 2400 series
tmp Disk
The command completed successfully.


Target hom200of002

"HOM100FR001 ping hom200of002"


Pinging hom200of002 [192.168.1.100] with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view hom200of002"

Shared resources at hom200of002



Share name Type Used as Comment

-------------------------------------------------------------------------------
Image Library Disk
PictureProject Disk
SharedDocs Disk
Tmp Disk
The command completed successfully.


Target 192.168.1.100

"HOM100FR001 ping 192.168.1.100"


Pinging 192.168.1.100 with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 192.168.1.100"

Shared resources at 192.168.1.100



Share name Type Used as Comment

-------------------------------------------------------------------------------
Image Library Disk
PictureProject Disk
SharedDocs Disk
Tmp Disk
The command completed successfully.


Target hom100fr001

"HOM100FR001 ping hom100fr001"


Pinging hom100fr001 [192.168.1.105] with 32 bytes of data:

Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view hom100fr001"

Shared resources at hom100fr001



Share name Type Used as Comment

-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.


Target 192.168.1.105

"HOM100FR001 ping 192.168.1.105"


Pinging 192.168.1.105 with 32 bytes of data:

Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 192.168.1.105"

Shared resources at 192.168.1.105



Share name Type Used as Comment

-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.


Target 127.0.0.1

"HOM100FR001 ping 127.0.0.1"


Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.


Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"HOM100FR001 ping www.yahoo.com"


Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=27ms TTL=54
Reply from 209.131.36.158: bytes=32 time=27ms TTL=53
Reply from 209.131.36.158: bytes=32 time=27ms TTL=53
Reply from 209.131.36.158: bytes=32 time=33ms TTL=53

Ping statistics for 209.131.36.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 33ms, Average = 28ms

Target 66.94.230.32

"HOM100FR001 ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=26ms TTL=54
Reply from 66.94.230.32: bytes=32 time=27ms TTL=53
Reply from 66.94.230.32: bytes=32 time=44ms TTL=53
Reply from 66.94.230.32: bytes=32 time=27ms TTL=53

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 44ms, Average = 31ms

Target 192.168.1.1

"HOM100FR001 ping 192.168.1.1"


Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

End diagnosis for HOM100FR001

Is “Find Server ("server")
Checking \\HOM100FR001... Found server on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:†a normal result?

Waited an hour and see if hom200of002 My Network Places showed the correct
shares. It doesn’t
Hom200of001 also shows the shares that are not real but at least the
computer is listed as unknown. Maybe this is another effect of Norton
Internet Security that has to be manually removed.
 


No computer A hom200of001 does not have a personal firewall. I assume your
next sentence refers to computer D. Yes, computer B hom200of002 and D
hom100of001 have Norton Internet Security 2007 and have the most problems.
Computer E was dropped off the network. Computer C P933iii will be dropped as
well to simplify things. To further simplify things. Computer D will be moved
from Wireless to wired. It occurred to me that maybe the wireless link is too
slow and Norton Internet Security has decided it is on the network alone and
has clamped things down.

Since I changed things, I will verify I have the same conditions as before.
I see same Windows Explorer Mshome computer icons (even though P933iii
doesn’t exist). My Network Places is the same. I can ping from hom200of002
to hom200of001 but not to hom200fr001. I will remove the results to try to
fit in the space allowed.


Removed Norton Internet Security 2007 computer D hom100fr001.

Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Did not check hom200of002
Computer A can create a file and store it into Computer D through Windows
Explorer Mshome computer icons. Did not check hom200of002
Computer A can ping using ping hom100fr001. Did not check hom200of002


Computer B hom200of002 doesn’t show hom100fr001 in My Network Neighborhood
Computer B can’t access hom100fr001 using Windows Explorer Mshome computer
icons. Get Mshome is not accessible.
Computer B can ping hom100fr001 using the IP address but not using the
computer name.

Computer D doesn’t show anything in My Network Neighborhood
Computer D can’t access Windows Explorer Mshome computer icons. Get Mshome
is not accessible.
Computer D can ping hom200of001 but not hom200of002.

Removed Norton Internet Security 2007 Computer B hom200of002.

Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Computer A can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer A can ping using ping hom100fr001.

Computer B hom200of002 shows hom100fr001 in My Network Neighborhood
Computer B can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer B can ping hom100fr001 and hom200of001 using the computer name.

Computer D shows in My Network Neighborhood
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\Hom100fr001\tmp

Computer D can modified a file on hom200of001 and hom200of002 through
Windows Explorer Mshome computer icons
Computer D can ping hom200of001 and hom200of002 using computer name.

Meantime

Computer B


Computer D

Start CPSServ V1.10 - HOM100FR001

Find Computer Browser ("browser")
Checking \\HOM100FR001... Found browser on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find DHCP Client ("dhcp")
Checking \\HOM100FR001... Found dhcp on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001... Found lmhosts on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001... Found remoteregistry on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find Server ("server")
Checking \\HOM100FR001... Found server on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001... Found sharedaccess on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:


Find Workstation ("workstation")
Checking \\HOM100FR001... Found workstation on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:

End CPSServ V1.10 - HOM100FR001

CDiagnosis V1.40
Start diagnosis for HOM100FR001
Full Targets hom200of001 192.168.1.103 hom200of002 192.168.1.100 hom100fr001
192.168.1.105 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

tmp C:\tmp
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\HOM100FR001

\\HOM200OF001

\\HOM200OF002

The command completed successfully.


Full Targets Analysis hom200of001 192.168.1.103 hom200of002 192.168.1.100
hom100fr001 192.168.1.105 127.0.0.1

Target hom200of001

"HOM100FR001 ping hom200of001"


Pinging hom200of001 [192.168.1.103] with 32 bytes of data:

Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view hom200of001"

Shared resources at hom200of001



Share name Type Used as Comment

-------------------------------------------------------------------------------
PSC2410 Print hp psc 2400 series
tmp Disk (UNC)
The command completed successfully.


Target 192.168.1.103

"HOM100FR001 ping 192.168.1.103"


Pinging 192.168.1.103 with 32 bytes of data:

Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 192.168.1.103"

Shared resources at 192.168.1.103



Share name Type Used as Comment

-------------------------------------------------------------------------------
PSC2410 Print hp psc 2400 series
tmp Disk
The command completed successfully.


Target hom200of002

"HOM100FR001 ping hom200of002"


Pinging hom200of002 [192.168.1.100] with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view hom200of002"

Shared resources at hom200of002



Share name Type Used as Comment

-------------------------------------------------------------------------------
Image Library Disk
PictureProject Disk
SharedDocs Disk
Tmp Disk
The command completed successfully.


Target 192.168.1.100

"HOM100FR001 ping 192.168.1.100"


Pinging 192.168.1.100 with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 192.168.1.100"

Shared resources at 192.168.1.100



Share name Type Used as Comment

-------------------------------------------------------------------------------
Image Library Disk
PictureProject Disk
SharedDocs Disk
Tmp Disk
The command completed successfully.


Target hom100fr001

"HOM100FR001 ping hom100fr001"


Pinging hom100fr001 [192.168.1.105] with 32 bytes of data:

Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view hom100fr001"

Shared resources at hom100fr001



Share name Type Used as Comment

-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.


Target 192.168.1.105

"HOM100FR001 ping 192.168.1.105"


Pinging 192.168.1.105 with 32 bytes of data:

Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 192.168.1.105"

Shared resources at 192.168.1.105



Share name Type Used as Comment

-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.


Target 127.0.0.1

"HOM100FR001 ping 127.0.0.1"


Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HOM100FR001 net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.


Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"HOM100FR001 ping www.yahoo.com"


Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=27ms TTL=54
Reply from 209.131.36.158: bytes=32 time=27ms TTL=53
Reply from 209.131.36.158: bytes=32 time=27ms TTL=53
Reply from 209.131.36.158: bytes=32 time=33ms TTL=53

Ping statistics for 209.131.36.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 33ms, Average = 28ms

Target 66.94.230.32

"HOM100FR001 ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=26ms TTL=54
Reply from 66.94.230.32: bytes=32 time=27ms TTL=53
Reply from 66.94.230.32: bytes=32 time=44ms TTL=53
Reply from 66.94.230.32: bytes=32 time=27ms TTL=53

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 44ms, Average = 31ms

Target 192.168.1.1

"HOM100FR001 ping 192.168.1.1"


Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

End diagnosis for HOM100FR001

Is “Find Server ("server")
Checking \\HOM100FR001... Found server on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:” a normal result?

Waited an hour and see if hom200of002 My Network Places showed the correct
shares. It doesn’t
Hom200of001 also shows the shares that are not real but at least the
computer is listed as unknown. Maybe this is another effect of Norton
Internet Security that has to be manually removed.

OK, let's slow down just a bit. Pick the network configuration - which
computers you want online, and how you want each to be connected, and leave it
that way. Then provide logs from "browstat status", "ipconfig /all", "net
config server", and "net config workstation", from each computer. I want to
start by verifying the bindings, but that requires all 4 logs for each computer.
I'm still learning your computer names, so be canonical when you enumerate them.

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.
 
[...]
browstat vw NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
\\hom200of002 0x40000000 gets me:
Remoting NetServerEnum to \\hom200of002 on transport
\device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
with flags 40000000
4 entries returned. 4 total. 0 milliseconds

\\HOM100FR001 NT 05.01 (W,S,NT,PBR,MBR)
\\HOM200OF001 NT 05.01 (W,S,PQ,NT,PBR)
\\HOM200OF002 NT 05.01 (W,S,DL,NT,PBR,MBR)
\\P933III NT 05.01 (W,S,PQ,NT,PBR) test

From the above listing, you can see that *two* computers have the "MBR"
attribute. There can/should be only be one Master Browser (MBR) for a
given workgroup and subnet. There can be more than one Backup Browser
(BBR) or Potential Browser (PBR). The problem is either with computer
HOM200OF002 or HOM100FR001 (my bet is the latter). Every time I've
seen this situation, it turned out to be a firewall issue.

If you can't solve the firewall issue, you often can keep it from
affecting the rest of the network by stopping the "Computer Browser"
service on the suspect machine(s). Only one machine on a subnet
actually needs to be running the Computer Browser service so it
shouldn't hurt to stop it on one machine. To stop it:
Right-click "My Computer" -> Manage -> Services and Applications ->
Services -> double-click "Computer Browser" -> Stop.
To keep it from running at next reboot, also change the "Startup Type"
from "Automatic" to "Manual".

This will keep this machine from affecting browsing on the other
machines in the subnet, but a firewall issue still could prevent file
sharing on that machine.

HTH,
John
 
Thanks for the MBR explanation again. It didn’t sink in the first.

I found that Norton Internet Security 2007 on both hom200of002 and
hom100fr001 were involved in the MShome not accessible problem. I went more
into the steps a response to the another person's answer. Originally both
Computer D hom100fr001 and hom200of002 had Mshome is not accessible. Removing
the Norton Internet Security 2007 from each computer removed the Mshome is
not accessible. The important part was as follows:

Removed Norton Internet Security 2007 computer D hom100fr001.

Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Did not check hom200of002
Computer A can create a file and store it into Computer D through Windows
Explorer Mshome computer icons. Did not check hom200of002
Computer A can ping using ping hom100fr001. Did not check hom200of002


Computer B hom200of002 doesn’t show hom100fr001 in My Network Neighborhood
Computer B can’t access hom100fr001 using Windows Explorer Mshome computer
icons. Get Mshome is not accessible.
Computer B can ping hom100fr001 using the IP address but not using the
computer name.

Computer D doesn’t show anything in My Network Neighborhood
Computer D can’t access Windows Explorer Mshome computer icons. Get Mshome
is not accessible.
Computer D can ping hom200of001 but not hom200of002.

Removed Norton Internet Security 2007 Computer B hom200of002.

Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Computer A can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer A can ping using ping hom100fr001.

Computer B hom200of002 shows hom100fr001 in My Network Neighborhood
Computer B can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer B can ping hom100fr001 and hom200of001 using the computer name.

Computer D shows in My Network Neighborhood
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\Hom100fr001\tmp

Computer D can modified a file on hom200of001 and hom200of002 through
Windows Explorer Mshome computer icons
Computer D can ping hom200of001 and hom200of002 using computer name

After both removals, you probably see what you were looking for.


C:\Documents and Settings\Joe>browstat fm
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
Master Browser: \\HOM200OF001

C:\Documents and Settings\Joe>browstat vw
NetBT_Tcpip_{6A15400B-A5AC-407E-9860-1
03410E72B58} \\hom200of001 0x40000000
Remoting NetServerEnum to \\hom200of001 on transport
\device\NetBT_Tcpip_{6A1540
0B-A5AC-407E-9860-103410E72B58} with flags 40000000
4 entries returned. 4 total. 31 milliseconds

\\HOM100FR001 NT 05.01 (W,S,NT,PBR,BBR)
\\HOM200OF001 NT 05.01 (W,S,PQ,NT,PBR,BBR,MBR)
\\HOM200OF002 NT 05.01 (W,S,DL,NT,PBR)
\\P933III NT 05.01 (W,S,PQ,NT,PBR) test

The MShome is not accessible problem seems to be clear.


John Wunderlich said:
[...]
browstat vw NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
\\hom200of002 0x40000000 gets me:
Remoting NetServerEnum to \\hom200of002 on transport
\device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
with flags 40000000
4 entries returned. 4 total. 0 milliseconds

\\HOM100FR001 NT 05.01 (W,S,NT,PBR,MBR)
\\HOM200OF001 NT 05.01 (W,S,PQ,NT,PBR)
\\HOM200OF002 NT 05.01 (W,S,DL,NT,PBR,MBR)
\\P933III NT 05.01 (W,S,PQ,NT,PBR) test

From the above listing, you can see that *two* computers have the "MBR"
attribute. There can/should be only be one Master Browser (MBR) for a
given workgroup and subnet. There can be more than one Backup Browser
(BBR) or Potential Browser (PBR). The problem is either with computer
HOM200OF002 or HOM100FR001 (my bet is the latter). Every time I've
seen this situation, it turned out to be a firewall issue.

If you can't solve the firewall issue, you often can keep it from
affecting the rest of the network by stopping the "Computer Browser"
service on the suspect machine(s). Only one machine on a subnet
actually needs to be running the Computer Browser service so it
shouldn't hurt to stop it on one machine. To stop it:
Right-click "My Computer" -> Manage -> Services and Applications ->
Services -> double-click "Computer Browser" -> Stop.
To keep it from running at next reboot, also change the "Startup Type"
from "Automatic" to "Manual".

This will keep this machine from affecting browsing on the other
machines in the subnet, but a firewall issue still could prevent file
sharing on that machine.

HTH,
John
 
I am not sure of what you are looking for when you said canonical.

Currently since the Norton Internet Security was removed from computer B and
D I am not getting a Mshome is not accessible message and I currently have
computers A through D on the network.

When you are asking for “browstat status†etc. are you still working on the
Mshome is not accessible problem or does this address the nuisance problem of
My Network Places continues to show shares that don’t exist?
 
I am not sure of what you are looking for when you said canonical.

Currently since the Norton Internet Security was removed from computer B and
D I am not getting a Mshome is not accessible message and I currently have
computers A through D on the network.

When you are asking for “browstat status” etc. are you still working on the
Mshome is not accessible problem or does this address the nuisance problem of
My Network Places continues to show shares that don’t exist?

By Canonical, I mean be consistent when you mention Computer A, Computer B, etc.
vs "HOM100FR001", "HOM200OF001", etc.

Both symptoms that you mention have a common cause - SMBs which advertise shared
resources, and which define the workgroup, are being blocked. Read about the
browser, and advertisement of shared resources.
<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

And read about SMBs.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

Browstat is a tool which shows the propagation of browser SMBs. Short of doing
packet analysis, using it gives the best chance that you have of solving your
problem. Comparing logs from "browstat status", "ipconfig /all", "net config
server", and "net config workstation", from each computer, will help us look for
one way that SMBs get blocked.

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.
 
After both removals, you probably see what you were looking for.


C:\Documents and Settings\Joe>browstat fm
\Device\NetBT_Tcpip_{6A15400B-A5AC-407E-9860-103410E72B58}
Master Browser: \\HOM200OF001

C:\Documents and Settings\Joe>browstat vw
NetBT_Tcpip_{6A15400B-A5AC-407E-9860-1
03410E72B58} \\hom200of001 0x40000000
Remoting NetServerEnum to \\hom200of001 on transport
\device\NetBT_Tcpip_{6A1540
0B-A5AC-407E-9860-103410E72B58} with flags 40000000
4 entries returned. 4 total. 31 milliseconds

\\HOM100FR001 NT 05.01 (W,S,NT,PBR,BBR)
\\HOM200OF001 NT 05.01 (W,S,PQ,NT,PBR,BBR,MBR)
\\HOM200OF002 NT 05.01 (W,S,DL,NT,PBR)
\\P933III NT 05.01 (W,S,PQ,NT,PBR) test

The MShome is not accessible problem seems to be clear.

Good! You've found your problem. It *was* a firewall.
I'm not personally familiar with the Norton Internet Security product,
but if you choose to continue to use the Norton Internet Security
program, I'd suggest that you read the following article which appears
to describe in step-by-step detail how to configure Norton to work with
a home file sharing network:

"How to Configure the Norton Internet Security Personal Firewall to
Allow File Sharing"
<http://www.leeindy.com/firewall_nis-1.shtml>

HTH,
John
 
Thanks for the link. I have found that Norton Internet Security 2007 once
installed, doesn’t take too kindly to any changes on the network. In my case
the home router died and the replacement wasn’t exactly the same as the
original. Another time I found that installing Norton Internet Security 2007
on a stand alone computer and trying to connect that computer to network
doesn’t work.

The article you list is dated and covers earlier version of Norton Internet
Security. However, I reinstalled Norton Internet Security 2007 back on
hom200of002 and hom100fr001. I don’t have the MShome not accessible message.

Interpreting what I found on the referenced web site I got:

Right click on the Globe, select Open, select Norton Internet Security tab,
select settings, select Personal Firewall, select Configure, select Trust
Control, select Trusted

At this point I don’t see IP address and Mask but rather the MAC address of
home router. There isn’t a Home Network Wizard. There is an Advanced
Settings. I selected Configure

Norton Internet Security 2007 does not have a Block access to secure sites.

It does show the Default Block Inbound and Outbound ICMP as Blocked and
Block Windows File Sharing as Blocked. Per the web site under these
conditions I shouldn’t be able (I am on hom200of002) to reach hom200of001 and
hom100fr001 and modify files but I can. I can also ping to hom200of001 and
hom100fr001 by using the computer name.

I am left with I still don’t know how to fix Norton Internet Security 2007
other than making sure all the components that will be in the network are
active, uninstalling Norton Internet Security 2007, and reinstalling Norton
Internet Security 2007.
 
Back
Top