Lost peer computer on network

[Randy W. Sims]

I have a small peer network of computers running Windows 2000 Pro / XP
Home. Used to be static IP, but was changed a while back to use dynamic
IP/DNS except for one (Windows XP Home) notebook that didn't get
changed, but it still worked fine. That notebook is now being used at
two locations on two networks, so it was changed to dynamic IP/DNS. That
is the only change I'm aware of that has been made. Now when connected
to the original network, it doesn't see the Microsoft network. TCP/IP
layer is fine. I can ping other computers and get pinged. I can access
the Internet (DSL modem into router/gateway). But the MS Network cannot
be browsed/accessed. Workgroup name is correct. I don't know of any
other settings to check.

Grateful for any advice.

Randy.

 

[Chuck]

I have a small peer network of computers running Windows 2000 Pro / XP
Home. Used to be static IP, but was changed a while back to use dynamic
IP/DNS except for one (Windows XP Home) notebook that didn't get
changed, but it still worked fine. That notebook is now being used at
two locations on two networks, so it was changed to dynamic IP/DNS. That
is the only change I'm aware of that has been made. Now when connected
to the original network, it doesn't see the Microsoft network. TCP/IP
layer is fine. I can ping other computers and get pinged. I can access
the Internet (DSL modem into router/gateway). But the MS Network cannot
be browsed/accessed. Workgroup name is correct. I don't know of any
other settings to check.

Grateful for any advice.

Randy.

Randy,

When you say "I can ping other computers and get pinged." are you referring to
from the problem computer?

This sounds like a personal firewall problem, though your history description
doesn't correlate that. Look at other possibilities too.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Are all essential network components and services still running on the problem
computer?
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

If no help yet, provide "browstat status" and "ipconfig /all" from the problem
computer, and from 2 properly working computers so we can diagnose the problem.
Read this article, and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

 

[Randy W. Sims]

Chuck wrote:

Thanks for the response Chuck. Much useful info on your website. Still
working through some of it, but here are results from the steps you
suggested.

Randy,

When you say "I can ping other computers and get pinged." are you referring to
from the problem computer?

Sorry. Further testing produces mixed results. I haven't tried all
computers on the network, but I verified that I can ping the router
(LinkSys RT31P2) and several computers running Windows 2000. I was not
able to ping a computer running WinXP Home. This is all from the faulty
system. From another good system (WinXP Home), I was able to ping the
faulty one.

This sounds like a personal firewall problem, though your history description
doesn't correlate that. Look at other possibilities too.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

1) Error message when trying to access network:

---><8---
\\MYSERVER\share 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 network path was not found.
---><8---

Verified many times correct Workgroup name, user name and password under
multiple accounts.

2) Temporarily disabled MS Firewall. Norton System works is installed
with Antivirus (temp disabled). Looks like SVG antivirus also installed.
No active firewalls.

3) Anonymous access restrictions not enabled.

4) `browstat status` from faulty system (GRAHAM):

Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{GRAHAM_GID}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


`ipconfig /all` from faulty system:

Windows IP Configuration

Host Name . . . . . . . . . . . . : GRAHAM
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bellsouth.net

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . : bellsouth.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : hh-hh-hh-hh-hh-hh
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : X.X.X.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : X.X.X.254
DHCP Server . . . . . . . . . . . : X.X.X.254
DNS Servers . . . . . . . . . . . : 205.152.37.23
205.152.144.23
Lease Obtained. . . . . . . . . . : Monday, January 23, 2006
19:23:38
Lease Expires . . . . . . . . . . : Tuesday, January 24, 2006
19:23:38


`browstat status` from good system (SORBET):

Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{GOOD_GID}
Browsing is active on domain.
Master browser name is: MYSERVER
Master browser is running build 2195
2 backup servers retrieved from master MYSERVER
\\CHOCOLATE
\\MYSERVER
There are 5 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{GOOD_GID}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{GOOD_GID}

`ipconfig /all` from good system:

Windows IP Configuration

Host Name . . . . . . . . . . . . : SORBET
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bellsouth.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : bellsouth.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : hh-hh-hh-hh-hh-hh
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : X.X.X.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : X.X.X.254
DHCP Server . . . . . . . . . . . : X.X.X.254
DNS Servers . . . . . . . . . . . : 205.152.37.23
205.152.144.23
Lease Obtained. . . . . . . . . . : Monday, January 23, 2006
5:12:15 PM
Lease Expires . . . . . . . . . . : Tuesday, January 24, 2006
5:12:15 PM


6) ...

7) Faulty cdiag <http://anytime24hour.com/temp/graham.cdiag.txt>
Good cdiags: <http://anytime24hour.com/temp/sorbet.cdiag.txt>
<http://anytime24hour.com/temp/chocolate.cdiag.txt>

8) ...

9) No unneeded protocols installed.

10) ???

11) working on it

12) ...

Are all essential network components and services still running on the problem
computer?
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

Everything checks ok in this section. (Still working through the rest of
that page)

If no help yet, provide "browstat status" and "ipconfig /all" from the problem
computer, and from 2 properly working computers so we can diagnose the problem.
Read this article, and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Provided above.


Thanks,
Randy.

 

[Chuck]

Chuck wrote:

Thanks for the response Chuck. Much useful info on your website. Still
working through some of it, but here are results from the steps you
suggested.



Sorry. Further testing produces mixed results. I haven't tried all
computers on the network, but I verified that I can ping the router
(LinkSys RT31P2) and several computers running Windows 2000. I was not
able to ping a computer running WinXP Home. This is all from the faulty
system. From another good system (WinXP Home), I was able to ping the
faulty one.


1) Error message when trying to access network:

---><8---
\\MYSERVER\share 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 network path was not found.
---><8---

Verified many times correct Workgroup name, user name and password under
multiple accounts.

2) Temporarily disabled MS Firewall. Norton System works is installed
with Antivirus (temp disabled). Looks like SVG antivirus also installed.
No active firewalls.

3) Anonymous access restrictions not enabled.

4) `browstat status` from faulty system (GRAHAM):

Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{GRAHAM_GID}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


`ipconfig /all` from faulty system:

Windows IP Configuration

Host Name . . . . . . . . . . . . : GRAHAM
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bellsouth.net

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . : bellsouth.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : hh-hh-hh-hh-hh-hh
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : X.X.X.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : X.X.X.254
DHCP Server . . . . . . . . . . . : X.X.X.254
DNS Servers . . . . . . . . . . . : 205.152.37.23
205.152.144.23
Lease Obtained. . . . . . . . . . : Monday, January 23, 2006
19:23:38
Lease Expires . . . . . . . . . . : Tuesday, January 24, 2006
19:23:38

<SNIP>

Here's a big one, Randy. Do you have a WINS server?

Windows IP Configuration
Host Name . . . . . . . . . . . . : GRAHAM
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer

If you don't have a WINS server, "Peer-Peer" won't work.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer

After you fix that, you'll need to rerun everything previously run on GRAHAM.

 

[Chuck]

Chuck wrote:

Thanks for the response Chuck. Much useful info on your website. Still
working through some of it, but here are results from the steps you
suggested.



Sorry. Further testing produces mixed results. I haven't tried all
computers on the network, but I verified that I can ping the router
(LinkSys RT31P2) and several computers running Windows 2000. I was not
able to ping a computer running WinXP Home. This is all from the faulty
system. From another good system (WinXP Home), I was able to ping the
faulty one.


1) Error message when trying to access network:

---><8---
\\MYSERVER\share 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 network path was not found.
---><8---

Verified many times correct Workgroup name, user name and password under
multiple accounts.

2) Temporarily disabled MS Firewall. Norton System works is installed
with Antivirus (temp disabled). Looks like SVG antivirus also installed.
No active firewalls.

3) Anonymous access restrictions not enabled.

4) `browstat status` from faulty system (GRAHAM):

Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{GRAHAM_GID}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


`ipconfig /all` from faulty system:

Windows IP Configuration

Host Name . . . . . . . . . . . . : GRAHAM
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bellsouth.net

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . : bellsouth.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : hh-hh-hh-hh-hh-hh
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : X.X.X.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : X.X.X.254
DHCP Server . . . . . . . . . . . : X.X.X.254
DNS Servers . . . . . . . . . . . : 205.152.37.23
205.152.144.23
Lease Obtained. . . . . . . . . . : Monday, January 23, 2006
19:23:38
Lease Expires . . . . . . . . . . : Tuesday, January 24, 2006
19:23:38

<SNIP>

Here's a big one, Randy. Do you have a WINS server?

Windows IP Configuration
Host Name . . . . . . . . . . . . : GRAHAM
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer

If you don't have a WINS server, "Peer-Peer" won't work.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer

After you fix that, you'll need to rerun everything previously run on GRAHAM.
If you want to use CDiag as a diagnostic, you have to fill in the CDiag data!
Add the name and IP address of EACH computer on the LAN to the CDiag code!
That's the meat of the diagnostic!!
<http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>
http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html
Now copy and edit the raw CDiag code. Add name ("Host Name") and IP address ("IP
Address") of each computer (as above) to the FullTarget lines, and add the IP
address of the Default Gateway / DHCP Server to the PingTargets line (if a NAT
router, and not one of the computers).

 

[Randy W. Sims]

<SNIP>

Here's a big one, Randy. Do you have a WINS server?

If you don't have a WINS server, "Peer-Peer" won't work.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer

That fixed it. I'd really, really like to know how this problem came
about in the first place.

After you fix that, you'll need to rerun everything previously run on GRAHAM.
If you want to use CDiag as a diagnostic, you have to fill in the CDiag data!
Add the name and IP address of EACH computer on the LAN to the CDiag code!
That's the meat of the diagnostic!!
<http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>
http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html
Now copy and edit the raw CDiag code. Add name ("Host Name") and IP address ("IP
Address") of each computer (as above) to the FullTarget lines, and add the IP
address of the Default Gateway / DHCP Server to the PingTargets line (if a NAT
router, and not one of the computers).

Oops. Trying to do 10 things at once, I just copy and pasted without
following up.


Many, many thanks Chuck. This problem has been gnawing at me since
Friday, and it quickly exhausted my limited knowledge. Your web site is
definitely one I'll remember for follow-up and future reference.

Thank you,

Randy.

 

[Chuck]

That fixed it. I'd really, really like to know how this problem came
about in the first place.


Oops. Trying to do 10 things at once, I just copy and pasted without
following up.


Many, many thanks Chuck. This problem has been gnawing at me since
Friday, and it quickly exhausted my limited knowledge. Your web site is
definitely one I'll remember for follow-up and future reference.

Thank you,

Randy.

Randy,

Great, thanks for following up. We don't know too much about the Peer-Peer
setting, except that it is a problem. We just see it in "ipconfig /all", and
that's enough. Glad it was that simple for you.

 

[zack]

Had the same problem and searched intermittently for months for a
solution. Computers could ping eachother, browse internet with no
problem but that dreaded message kept popping up every time I tried to
view computers on the network.

What worked for me was installing NETBUI. Check out

http://support.microsoft.com/kb/301041/EN-US/

I've had no problems since

 

[Chuck]

Had the same problem and searched intermittently for months for a
solution. Computers could ping eachother, browse internet with no
problem but that dreaded message kept popping up every time I tried to
view computers on the network.

What worked for me was installing NETBUI. Check out

http://support.microsoft.com/kb/301041/EN-US/

I've had no problems since

Zack,

Installing NetBEUI is a good workaround, when you have a problem with TCP/IP and
NetBIOS Over TCP/IP. There are numerous other problem that folks can have with
Windows Networking, and your problems need to be diagnosed before you apply
workarounds. And NetBEUI is limited in effect. Know what you're doing, and
what its limitations are, before applying it.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html

If you've been "looking intermittently for a solution", you haven't been looking
here, have you? You certainly haven't posted here, as "Zack", asking for help.
<http://groups.google.com/group/micr....network_web/search?q=zack&start=0&scoring=d&>
http://groups.google.com/group/micr....network_web/search?q=zack&start=0&scoring=d&

To the OP:
Anybody can give advice here. Beware of accepting advice from folks who post
once, about a change that they made recently, as a magical fix to your problems.
Diagnose your problems first. And note the caveat in the cited article:
Microsoft has discontinued support for the NetBEUI network protocol in Windows
XP.

And read about how to find reliable help.
<http://nitecruzr.blogspot.com/2005/05/getting-help-on-usenet-and-believing.html>
http://nitecruzr.blogspot.com/2005/05/getting-help-on-usenet-and-believing.html