Wkgrp Network of 3 XP and 1 2K machines stopped working

E

Ed Katzman

Hi:

I've seen bits and pieces of this problem discussed, but I can't see a
whole solution.

My network:
A: WinXP Pro SP2
B: WinXP Pro SP2
C: WinXP Media Center
D: Win2000 Pro SP4

All machines have only Client for MS Networks, File and print sharing,
QoS packet scheduler, and TCP/IP active, with NetBIOS over TCP/IP
activated.

All have an Administrator account with the same password, which is
blank.

A & B are wired to the router; C & D have wireless cards.

Everything was working until recently.

My problem:

A & C can see each other in network neighborhood and exchange files.
A can see B & D by name in a net view and in a "view workgroup
computers" under My Network places
If I try to connect A to B or D by clicking on their name, I get " 'D'
(or 'B') is not accessible. You may not have permission ... network
path not found" (Same from C)
From A, I can ping C by name, but not B or D ("could not find host")
From A, I can ping C AND D by ip, but not B

From B I can see all machines in net view and "view workgroup
computers" and can connect to A and C and exchange files, etc. B cannot
access D.
B can ping A & C by name, but not D. B can ping A, C, AND D by ip.

C is just like A

D cannot access workgroup from "My Network Places", getting "Workgroup
not accessible. List of servers not currently available."
D can see A in "Search for computers" by name and ip.
D can't see B or C by name or ip in "Search"
D can ping A by ip but not by name, geting "unknown host".
D can't ping either B or C by name or ip.
From D, net view shows "List of servers is not available."

Can someone please give me a sequence of tests, as specific as possible,
using command line programs to get the information to sort this out?

Many thanks.

Ed
 
R

Robert L [MS-MVP]

I would check the firewall first. also what's the system error if using net view \\remotepcip?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi:

I've seen bits and pieces of this problem discussed, but I can't see a
whole solution.

My network:
A: WinXP Pro SP2
B: WinXP Pro SP2
C: WinXP Media Center
D: Win2000 Pro SP4

All machines have only Client for MS Networks, File and print sharing,
QoS packet scheduler, and TCP/IP active, with NetBIOS over TCP/IP
activated.

All have an Administrator account with the same password, which is
blank.

A & B are wired to the router; C & D have wireless cards.

Everything was working until recently.

My problem:

A & C can see each other in network neighborhood and exchange files.
A can see B & D by name in a net view and in a "view workgroup
computers" under My Network places
If I try to connect A to B or D by clicking on their name, I get " 'D'
(or 'B') is not accessible. You may not have permission ... network
path not found" (Same from C)
From A, I can ping C by name, but not B or D ("could not find host")
From A, I can ping C AND D by ip, but not B

From B I can see all machines in net view and "view workgroup
computers" and can connect to A and C and exchange files, etc. B cannot
access D.
B can ping A & C by name, but not D. B can ping A, C, AND D by ip.

C is just like A

D cannot access workgroup from "My Network Places", getting "Workgroup
not accessible. List of servers not currently available."
D can see A in "Search for computers" by name and ip.
D can't see B or C by name or ip in "Search"
D can ping A by ip but not by name, geting "unknown host".
D can't ping either B or C by name or ip.
From D, net view shows "List of servers is not available."

Can someone please give me a sequence of tests, as specific as possible,
using command line programs to get the information to sort this out?

Many thanks.

Ed
 
G

Guest

In addition, your XP computers must have at least one password protected
account for sharing to take place. This is usually the Administrator
account. So, first thing is set passwords on your computers and then see if
you can connect.

If you want, you can create identical accounts on all systems, with
identical passwords. This will make sharing easier in the long run.

FE
Wm P
MVP Microsoft Networking
MCP | CCNA | A+
 
E

Ed Katzman

Wm P: Thanks.

Do all accounts on all machines need to be the same? Or can only the
accounts that are the same access the other machine(s)?

Ed
 
E

Ed Katzman

In article <[email protected]>, (e-mail address removed)
says...
Bob: Many thanks. One of the XP machines had its firewall set to
"Don't allow exceptions." I fixed that and now it can see all the other
machines.

The win2000 machine is now the big problem. It see or can't open some
machines and some can't open it.

I get Error 53 from net view \\remotepcip.

Ed
 
E

Ed Katzman

Bob: I checked a few more things and am closer but not there.



All machines have all critical updates installed.
They also all show "auto login only in intranet zone" in both Internet
and Local Internet.

Fixing passwords and firewalls solved some of the problem. Now I'm OK
except A (WinXP Pro SP2) can't access B (WinXP Pro SP2) or D (Win2000
SP4), tho they show up in My Network Places. I get " 'D'
(or 'B') is not accessible. You may not have permission ... network
path not found"

A to D and vice versa is the connection I most need.

Any more ideas? Thanks again.


Ed
 
E

Ed Katzman

I'm still unable to get all these machines to connect. I've gone thru
many things I can find on the net, especially PChuck's great site.
http://nitecruzr.blogspot.com/2005/05/getting-help-on-usenet-and-
believing.html

I've run his CDiag scripts, which gives machine to machine ping and
other output. I've inserted them below as a fuller descripyion of my
problem.

Can someone help? Thanks. Ed

Hi:

I've seen bits and pieces of this problem discussed, but I can't see a
whole solution.

My network:
A: WinXP Pro SP2
B: WinXP Pro SP2
C: WinXP Media Center
D: Win2000 Pro SP4

All machines have only Client for MS Networks, File and print sharing,
QoS packet scheduler, and TCP/IP active, with NetBIOS over TCP/IP
activated.

All have an Administrator account with the same password, which is
blank.

A & B are wired to the router; C & D have wireless cards.

Everything was working until recently.

My problem:
Click to expand...

CDiag from machine A (GatewayP4)

CDiagnosis V1.33
Start diagnosis for GATEWAYP4

Enumerate Shares


Share name Resource Remark

------------------------------------------------------------------------
-------
IPC$ Remote IPC
D$ D:\ Default share
C$ C:\ Default share
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
ADMIN$ C:\WINDOWS Remote Admin
F$ F:\ Default share
DATA (D) D:\
Old WinXP(F) F:\
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

NEC870 USB005 Spooled NEC SuperScript 870
The command completed successfully.


Adhoc Browser View

Server Name Remark

------------------------------------------------------------------------
-------
\\AWWLAPTOP AWWLaptop
\\GATEWAYP4 GatewayP4
\\JACKDELL JackDell
\\JACKT450 Jack T450
The command completed successfully.


Full Targets GatewayP4 192.168.1.103 JackT450 192.168.1.102 AWWLaptop
192.168.1.101 JackDell 192.168.1.9 127.0.0.1

Target GatewayP4

"GATEWAYP4 ping GatewayP4"


Pinging gatewayp4 [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

"GATEWAYP4 net view GatewayP4"

Shared resources at GatewayP4

GatewayP4

Share name Type Used as Comment

------------------------------------------------------------------------
-------
DATA (D) Disk
NEC870 Print NEC SuperScript 870
Old WinXP(F) Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.1.103

"GATEWAYP4 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

"GATEWAYP4 net view 192.168.1.103"

Shared resources at 192.168.1.103

GatewayP4

Share name Type Used as Comment

------------------------------------------------------------------------
-------
DATA (D) Disk
NEC870 Print NEC SuperScript 870
Old WinXP(F) Disk
SharedDocs Disk
The command completed successfully.


Target JackT450

"GATEWAYP4 ping JackT450"

Ping request could not find host JackT450. Please check the name and try
again.

"GATEWAYP4 net view JackT450"


Target 192.168.1.102

"GATEWAYP4 ping 192.168.1.102"


Pinging 192.168.1.102 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

"GATEWAYP4 net view 192.168.1.102"


Target AWWLaptop

"GATEWAYP4 ping AWWLaptop"

Ping request could not find host AWWLaptop. Please check the name and
try again.

"GATEWAYP4 net view AWWLaptop"

Shared resources at AWWLaptop

AWWLaptop

Share name Type Used as Comment

------------------------------------------------------------------------
-------
C Disk
WindowsNTFax Print Fax share created by Network Magic
The command completed successfully.


Target 192.168.1.101

"GATEWAYP4 ping 192.168.1.101"


Pinging 192.168.1.101 with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128

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

"GATEWAYP4 net view 192.168.1.101"

Shared resources at 192.168.1.101

AWWLaptop

Share name Type Used as Comment

------------------------------------------------------------------------
-------
C Disk
WindowsNTFax Print Fax share created by Network Magic
The command completed successfully.


Target JackDell

"GATEWAYP4 ping JackDell"


Pinging JackDell [192.168.1.9] with 32 bytes of data:

Reply from 192.168.1.9: bytes=32 time=2ms TTL=128
Reply from 192.168.1.9: bytes=32 time=3ms TTL=128
Reply from 192.168.1.9: bytes=32 time=2ms TTL=128
Reply from 192.168.1.9: bytes=32 time=4ms TTL=128

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

"GATEWAYP4 net view JackDell"

Shared resources at JackDell

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs Disk
The command completed successfully.


Target 192.168.1.9

"GATEWAYP4 ping 192.168.1.9"


Pinging 192.168.1.9 with 32 bytes of data:

Reply from 192.168.1.9: bytes=32 time=2ms TTL=128
Reply from 192.168.1.9: bytes=32 time=2ms TTL=128
Reply from 192.168.1.9: bytes=32 time=3ms TTL=128
Reply from 192.168.1.9: bytes=32 time=2ms TTL=128

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

"GATEWAYP4 net view 192.168.1.9"

Shared resources at 192.168.1.9

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs Disk
The command completed successfully.


Target 127.0.0.1

"GATEWAYP4 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

"GATEWAYP4 net view 127.0.0.1"

Shared resources at 127.0.0.1

GatewayP4

Share name Type Used as Comment

------------------------------------------------------------------------
-------
DATA (D) Disk
NEC870 Print NEC SuperScript 870
Old WinXP(F) Disk
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"GATEWAYP4 ping www.yahoo.com"


Pinging www.yahoo.akadns.net [216.109.118.78] with 32 bytes of data:

Reply from 216.109.118.78: bytes=32 time=33ms TTL=49
Reply from 216.109.118.78: bytes=32 time=37ms TTL=49
Reply from 216.109.118.78: bytes=32 time=37ms TTL=49
Reply from 216.109.118.78: bytes=32 time=34ms TTL=49

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

Target 66.94.230.32

"GATEWAYP4 ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=63ms TTL=48
Reply from 66.94.230.32: bytes=32 time=66ms TTL=48
Reply from 66.94.230.32: bytes=32 time=65ms TTL=48
Reply from 66.94.230.32: bytes=32 time=63ms TTL=48

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

End diagnosis for GATEWAYP4

CDiag from Machine B (JackT450)

CDiagnosis V1.33
Start diagnosis for JACKT450

Enumerate Shares


Share name Resource Remark

------------------------------------------------------------------------
-------
E$ E:\ Default share
IPC$ Remote IPC
D$ D:\ Default share
print$ C:\WINDOWS\System32\spool\DRIVERS
Printer Drivers
H$ H:\ Default share
C$ C:\ Default share
G$ G:\ Default share
ADMIN$ C:\WINDOWS Remote Admin
Data (D) D:\
SharedDocs C:\Documents and Settings\All Users\Documents

The command completed successfully.


Adhoc Browser View

Server Name Remark

------------------------------------------------------------------------
-------
\\AWWLAPTOP AWWLaptop
\\GATEWAYP4 GatewayP4
\\JACKDELL JackDell
\\JACKT450 Jack T450
The command completed successfully.


Full Targets GatewayP4 192.168.1.103 JackT450 192.168.1.102 AWWLaptop
192.168.1.101 JackDell 192.168.1.9 127.0.0.1

Target GatewayP4

"JACKT450 ping GatewayP4"

Ping request could not find host GatewayP4. Please check the name and
try again.

"JACKT450 net view GatewayP4"


Target 192.168.1.103

"JACKT450 ping 192.168.1.103"


Pinging 192.168.1.103 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

"JACKT450 net view 192.168.1.103"


Target JackT450

"JACKT450 ping JackT450"


Pinging JackT450 [192.168.1.102] with 32 bytes of data:

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

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

"JACKT450 net view JackT450"

Shared resources at JackT450

Jack T450

Share name Type Used as Comment

------------------------------------------------------------------------
-------
Data (D) Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.1.102

"JACKT450 ping 192.168.1.102"


Pinging 192.168.1.102 with 32 bytes of data:

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

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

"JACKT450 net view 192.168.1.102"

Shared resources at 192.168.1.102

Jack T450

Share name Type Used as Comment

------------------------------------------------------------------------
-------
Data (D) Disk
SharedDocs Disk
The command completed successfully.


Target AWWLaptop

"JACKT450 ping AWWLaptop"

Ping request could not find host AWWLaptop. Please check the name and
try again.

"JACKT450 net view AWWLaptop"


Target 192.168.1.101

"JACKT450 ping 192.168.1.101"


Pinging 192.168.1.101 with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time=95ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=3ms TTL=128

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

"JACKT450 net view 192.168.1.101"

Shared resources at 192.168.1.101

AWWLaptop

Share name Type Used as Comment

------------------------------------------------------------------------
-------
C Disk
WindowsNTFax Print Fax share created by Network Magic
The command completed successfully.


Target JackDell

"JACKT450 ping JackDell"


Pinging JackDell [192.168.1.9] with 32 bytes of data:

Reply from 192.168.1.9: bytes=32 time=4ms TTL=128
Reply from 192.168.1.9: bytes=32 time=4ms TTL=128
Reply from 192.168.1.9: bytes=32 time=4ms TTL=128
Reply from 192.168.1.9: bytes=32 time=7ms TTL=128

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

"JACKT450 net view JackDell"

Shared resources at JackDell

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs Disk
The command completed successfully.


Target 192.168.1.9

"JACKT450 ping 192.168.1.9"


Pinging 192.168.1.9 with 32 bytes of data:

Reply from 192.168.1.9: bytes=32 time=3ms TTL=128
Reply from 192.168.1.9: bytes=32 time=6ms TTL=128
Reply from 192.168.1.9: bytes=32 time=4ms TTL=128
Reply from 192.168.1.9: bytes=32 time=7ms TTL=128

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

"JACKT450 net view 192.168.1.9"

Shared resources at 192.168.1.9

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs Disk
The command completed successfully.


Target 127.0.0.1

"JACKT450 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

"JACKT450 net view 127.0.0.1"

Shared resources at 127.0.0.1

Jack T450

Share name Type Used as Comment

------------------------------------------------------------------------
-------
Data (D) Disk
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"JACKT450 ping www.yahoo.com"


Pinging www.yahoo.akadns.net [216.109.118.78] with 32 bytes of data:

Reply from 216.109.118.78: bytes=32 time=50ms TTL=49
Reply from 216.109.118.78: bytes=32 time=33ms TTL=49
Reply from 216.109.118.78: bytes=32 time=35ms TTL=49
Reply from 216.109.118.78: bytes=32 time=34ms TTL=49

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

Target 66.94.230.32

"JACKT450 ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=63ms TTL=48
Reply from 66.94.230.32: bytes=32 time=64ms TTL=48
Reply from 66.94.230.32: bytes=32 time=65ms TTL=48
Reply from 66.94.230.32: bytes=32 time=65ms TTL=48

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

End diagnosis for JACKT450

CDiag from Machine C (JackDell)

CDiagnosis V1.33
Start diagnosis for JACKDELL

Enumerate Shares


Share name Resource Remark

------------------------------------------------------------------------
-------
IPC$ Remote IPC
ADMIN$ C:\WINDOWS Remote Admin
C$ C:\ Default share
JackDell Docs
C:\Documents and Settings
The command completed successfully.


Adhoc Browser View

Server Name Remark

------------------------------------------------------------------------
-------
\\AWWLAPTOP AWWLaptop
\\GATEWAYP4 GatewayP4
\\JACKDELL JackDell
\\JACKT450 Jack T450
The command completed successfully.


Full Targets GatewayP4 192.168.1.103 JackT450 192.168.1.102 AWWLaptop
192.168.1.101 JackDell 192.168.1.9 127.0.0.1

Target GatewayP4

"JACKDELL ping GatewayP4"

Ping request could not find host GatewayP4. Please check the name and
try again.

"JACKDELL net view GatewayP4"


Target 192.168.1.103

"JACKDELL ping 192.168.1.103"


Pinging 192.168.1.103 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

"JACKDELL net view 192.168.1.103"


Target JackT450

"JACKDELL ping JackT450"

Ping request could not find host JackT450. Please check the name and try
again.

"JACKDELL net view JackT450"


Target 192.168.1.102

"JACKDELL ping 192.168.1.102"


Pinging 192.168.1.102 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

"JACKDELL net view 192.168.1.102"


Target AWWLaptop

"JACKDELL ping AWWLaptop"

Ping request could not find host AWWLaptop. Please check the name and
try again.

"JACKDELL net view AWWLaptop"


Target 192.168.1.101

"JACKDELL ping 192.168.1.101"


Pinging 192.168.1.101 with 32 bytes of data:

Request timed out.
Reply from 192.168.1.101: bytes=32 time=251ms TTL=128
Reply from 192.168.1.101: bytes=32 time=2ms TTL=128
Reply from 192.168.1.101: bytes=32 time=94ms TTL=128

Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 251ms, Average = 115ms

"JACKDELL net view 192.168.1.101"


Target JackDell

"JACKDELL ping JackDell"


Pinging JackDell [192.168.1.9] with 32 bytes of data:

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

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

"JACKDELL net view JackDell"

Shared resources at JackDell

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs Disk
The command completed successfully.


Target 192.168.1.9

"JACKDELL ping 192.168.1.9"


Pinging 192.168.1.9 with 32 bytes of data:

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

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

"JACKDELL net view 192.168.1.9"

Shared resources at 192.168.1.9

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs Disk
The command completed successfully.


Target 127.0.0.1

"JACKDELL 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

"JACKDELL net view 127.0.0.1"

Shared resources at 127.0.0.1

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"JACKDELL ping www.yahoo.com"


Pinging www.yahoo.akadns.net [68.142.226.46] with 32 bytes of data:

Reply from 68.142.226.46: bytes=32 time=41ms TTL=48
Reply from 68.142.226.46: bytes=32 time=41ms TTL=48
Reply from 68.142.226.46: bytes=32 time=43ms TTL=48
Reply from 68.142.226.46: bytes=32 time=41ms TTL=48

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

Target 66.94.230.32

"JACKDELL ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=71ms TTL=48
Reply from 66.94.230.32: bytes=32 time=66ms TTL=48
Reply from 66.94.230.32: bytes=32 time=64ms TTL=48
Reply from 66.94.230.32: bytes=32 time=65ms TTL=48

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

End diagnosis for JACKDELL

CDiag from Machine D (AWWLaptop)

CDiagnosis V1.33
Start diagnosis for AWWLAPTOP

Enumerate Shares


Share name Resource Remark

------------------------------------------------------------------------
-------
print$ C:\WINNT\System32\spool\drivers Printer Drivers
C$ C:\ Default share
ADMIN$ C:\WINNT Remote Admin
IPC$ Remote IPC
C C:\
WindowsNTFax MSFAX: Spooled Fax share created by
Network Magic
The command completed successfully.


Adhoc Browser View


Full Targets GatewayP4 192.168.1.103 JackT450 192.168.1.102 AWWLaptop
192.168.1.101 JackDell 192.168.1.9 127.0.0.1

Target GatewayP4

"AWWLAPTOP ping GatewayP4"

Unknown host GatewayP4.

"AWWLAPTOP net view GatewayP4"


Target 192.168.1.103

"AWWLAPTOP ping 192.168.1.103"


Pinging 192.168.1.103 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

"AWWLAPTOP net view 192.168.1.103"


Target JackT450

"AWWLAPTOP ping JackT450"

Unknown host JackT450.

"AWWLAPTOP net view JackT450"


Target 192.168.1.102

"AWWLAPTOP ping 192.168.1.102"


Pinging 192.168.1.102 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

"AWWLAPTOP net view 192.168.1.102"


Target AWWLaptop

"AWWLAPTOP ping AWWLaptop"


Pinging AWWLaptop [192.168.1.101] with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128

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

"AWWLAPTOP net view AWWLaptop"

Shared resources at AWWLaptop

AWWLaptop

Share name Type Used as Comment

------------------------------------------------------------------------
-------
C Disk
WindowsNTFax Print Fax share created by Network Magic
The command completed successfully.


Target 192.168.1.101

"AWWLAPTOP ping 192.168.1.101"


Pinging 192.168.1.101 with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128

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

"AWWLAPTOP net view 192.168.1.101"

Shared resources at 192.168.1.101

AWWLaptop

Share name Type Used as Comment

------------------------------------------------------------------------
-------
C Disk
WindowsNTFax Print Fax share created by Network Magic
The command completed successfully.


Target JackDell

"AWWLAPTOP ping JackDell"

Unknown host JackDell.

"AWWLAPTOP net view JackDell"


Target 192.168.1.9

"AWWLAPTOP ping 192.168.1.9"


Pinging 192.168.1.9 with 32 bytes of data:

Reply from 192.168.1.9: bytes=32 time=163ms TTL=128
Reply from 192.168.1.9: bytes=32 time=82ms TTL=128
Reply from 192.168.1.9: bytes=32 time=2ms TTL=128
Reply from 192.168.1.9: bytes=32 time=230ms TTL=128

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

"AWWLAPTOP net view 192.168.1.9"

Shared resources at 192.168.1.9

JackDell

Share name Type Used as Comment

------------------------------------------------------------------------
-------
JackDell Docs
Disk
The command completed successfully.


Target 127.0.0.1

"AWWLAPTOP ping 127.0.0.1"


Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms 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

"AWWLAPTOP net view 127.0.0.1"

Shared resources at 127.0.0.1

AWWLaptop

Share name Type Used as Comment

------------------------------------------------------------------------
-------
C Disk
WindowsNTFax Print Fax share created by Network Magic
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"AWWLAPTOP ping www.yahoo.com"


Pinging www.yahoo.akadns.net [216.109.117.106] with 32 bytes of data:

Reply from 216.109.117.106: bytes=32 time=34ms TTL=49
Reply from 216.109.117.106: bytes=32 time=34ms TTL=49
Reply from 216.109.117.106: bytes=32 time=32ms TTL=49
Reply from 216.109.117.106: bytes=32 time=33ms TTL=49

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

Target 66.94.230.32

"AWWLAPTOP ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=65ms TTL=48
Hardware error.
Hardware error.
Hardware error.

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 65ms, Average = 16ms

End diagnosis for AWWLAPTOP
 
C

Chuck

I'm still unable to get all these machines to connect. I've gone thru
many things I can find on the net, especially PChuck's great site.
http://nitecruzr.blogspot.com/2005/05/getting-help-on-usenet-and-
believing.html

I've run his CDiag scripts, which gives machine to machine ping and
other output. I've inserted them below as a fuller descripyion of my
problem.
Click to expand...

Ed,

From parsing the CDiag output, and looking at the patterns, I can easily see:
# GatewayP4 and JackT450 can't be accessed at all.
# JackDell can't access anything besides itself.

You need to start by looking at those 3 computers for the causes of those
problems. Those are the biggest problems (though probably not the only ones).
Research, and diagnose, your problems methodically. The diagnostics of your
problems are described (in general) in the first article, and (in some detail),
in the second article.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

If you like, provide "browstat status" and "ipconfig /all" from each computer -
maybe there's a clue there. 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
 
C

Chuck

On Mon, 16 Jan 2006 20:24:23 -0600, Ed Katzman <*email_address_deleted*> wrote:

<SNIP a lot of rambling / nonsense>

That may be your opinion. But did you read any of my articles?

BTW, Ed, posting your email address openly will get you more unwanted email,
than wanted email. Learn to munge your email address properly, to keep yourself
a bit safer when posting to open forums. Protect yourself and the rest of the
internet - read this article.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#Munging>
 
E

Ed Katzman

Content-Type: multipart/mixed; boundary="(gngnoooeis=========__1137511322)"

--(gngnoooeis=========__1137511322)
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Content-Type: multipart/mixed; boundary="(vwjsllvulg=========__1137464634)"

--(vwjsllvulg=========__1137464634)
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Ed,

From parsing the CDiag output, and looking at the patterns, I can easily see:
# GatewayP4 and JackT450 can't be accessed at all.
# JackDell can't access anything besides itself.

You need to start by looking at those 3 computers for the causes of those
problems. Those are the biggest problems (though probably not the only ones).
Research, and diagnose, your problems methodically. The diagnostics of your
Click to expand...

Chuck:

Thanks. Your website is great! As I work through the information, I
thought I'd report on my findings as I go, so if I find something
important you can tell me how to look further.

My summary from the CDIAG logs is here. I see that all can reach
AWWLaptop by ip and most can reach JackDell by name or ip. Gatewayp4
and Jackt450 can only see themselves:

Ping Summary
Can Ping
By Name/By IP
To
GatewayP4 JackT450 AWWLaptop JackDell
From GatewayP4 Y/Y CF/TO CF/Y Y/Y
JackT450 CF/TO Y/Y CF/Y Y/Y
AWWLaptop UH/TO UH/TO Y/Y UH/Y
JackDell CF/TO CF/TO CF/Y Y/Y

Key:
Y: Good response with information
CF: Can't find host
UH: Unknown host
TO: Request timed out

Net View of Machine Summary
Response from net view
By Name/By IP
To
GatewayP4 JackT450 AWWLaptop JackDell
From GatewayP4 Y/Y 53/53 Y/Y Y/Y
JackT450 53/53 Y/Y 53/Y Y/Y
AWWLaptop 53/53 53/53 Y/Y 53/Y
JackDell 53/53 53/53 53/53 Y/Y

Key:
Y: Shows shares
53: Error 53

Ad Hoc Browser View
Response from net view
GatewayP4 Server list* *Not consistent
JackT450 Server List
AWWLaptop Error 6118
JackDell Server list



Here is the summary from from my ipconfig /all and browstat sta runs. I
notice my node types include Unknown , hybrid, and peer-to-peer, and
that GatewayP4 says browing is not active, but in previous browstat runs
in the last few days it has listed GatewayP4 or JackDell as the browser
(sometimes with an error 5.)

I see a bridge on Gatewayp4 and I know one of you pages says to get rid
of it, but I don't know how. (It bridges the Firewire and the network
adapter.)

Also, I tried to start browsing on Gatewayp4 thru control panel and it
says that it started and then stopped again right away.

GatewayP4

Status for domain KATZMANWEST on transport \Device\NetBT_Tcpip_
{20FFB232-34CD-4D8B-AC66-34B472B57E4A}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Windows IP Configuration



Host Name . . . . . . . . . . . . : gatewayp4

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

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

WINS Proxy Enabled. . . . . . . . : Yes

DNS Suffix Search List. . . . . . : hsd1.il.comcast.net.



Ethernet adapter Network Bridge:



Connection-specific DNS Suffix . : hsd1.il.comcast.net.

Description . . . . . . . . . . . : MAC Bridge Miniport

Physical Address. . . . . . . . . : A2-1B-D9-3D-FA-E0

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.103

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

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

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

DNS Servers . . . . . . . . . . . : 68.87.72.130

68.87.77.130

Lease Obtained. . . . . . . . . . : Monday, January 16, 2006
2:41:52 PM

Lease Expires . . . . . . . . . . : Tuesday, January 17, 2006
2:41:52 PM



Jack T4540 info

Status for domain KATZMANWEST on transport \Device\NetBT_Tcpip_
{E2029B39-A8DE-4725-842C-485B641721B1}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Windows IP Configuration



Host Name . . . . . . . . . . . . : JackT450

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

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

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

DNS Suffix Search List. . . . . . : hsd1.il.comcast.net.



Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . : hsd1.il.comcast.net.

Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI
For Complete PC Management NIC (3C905C-TX)

Physical Address. . . . . . . . . : 00-50-DA-1B-DA-70

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.102

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

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

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

DNS Servers . . . . . . . . . . . : 68.87.72.130

68.87.77.130

Lease Obtained. . . . . . . . . . : Monday, January 16, 2006
12:18:08 PM

Lease Expires . . . . . . . . . . : Tuesday, January 17, 2006
12:18:08 PM

JackDell info

Status for domain KATZMANWEST on transport \Device\NetBT_Tcpip_
{785B3231-529D-40B3-B225-BC5582BE2155}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Windows IP Configuration



Host Name . . . . . . . . . . . . : JackDell

Primary Dns Suffix . . . . . . . :

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

IP Routing Enabled. . . . . . . . : Yes

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



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Controller

Physical Address. . . . . . . . . : 00-11-11-8A-5D-D0



Ethernet adapter Wireless Network Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Dell Wireless 1450 Dual-band
(802.11a/b/g) USB2.0 Adapter #3

Physical Address. . . . . . . . . : 00-90-4B-C9-9A-96

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.9

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

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

DNS Servers . . . . . . . . . . . : 63.240.76.198

204.127.199.8

AWWLaptop Info

Status for domain KATZMANWEST on transport \Device\NetBT_Tcpip_
{C386D73F-A088-4A12-ACCB-A0949BE69857}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : AWWLaptop
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer

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

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

DNS Suffix Search List. . . . . . : hsd1.il.comcast.net.

Ethernet adapter Local Area Connection 4:



Connection-specific DNS Suffix . : hsd1.il.comcast.net.
Description . . . . . . . . . . . : Wireless-G Notebook Adapter #2
Physical Address. . . . . . . . . : 00-0C-41-AD-D5-7B

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

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

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

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

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

DNS Servers . . . . . . . . . . . : 68.87.72.130
68.87.77.130
Lease Obtained. . . . . . . . . . : Monday, January 16, 2006
5:58:00 PM

Lease Expires . . . . . . . . . . : Tuesday, January 17, 2006
5:58:00 PM


Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Cable Disconnected

Description . . . . . . . . . . . : 3Com 10/100 Mini PCI Ethernet
Adapter
Physical Address. . . . . . . . . : 00-01-03-86-93-F1
 
C

Chuck

Content-Type: multipart/mixed; boundary="(gngnoooeis=========__1137511322)"

--(gngnoooeis=========__1137511322)
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Content-Type: multipart/mixed; boundary="(vwjsllvulg=========__1137464634)"

--(vwjsllvulg=========__1137464634)
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit



Chuck:

Thanks. Your website is great! As I work through the information, I
thought I'd report on my findings as I go, so if I find something
important you can tell me how to look further.

My summary from the CDIAG logs is here. I see that all can reach
AWWLaptop by ip and most can reach JackDell by name or ip. Gatewayp4
and Jackt450 can only see themselves:

Ping Summary
Can Ping
By Name/By IP
To
GatewayP4 JackT450 AWWLaptop JackDell
From GatewayP4 Y/Y CF/TO CF/Y Y/Y
JackT450 CF/TO Y/Y CF/Y Y/Y
AWWLaptop UH/TO UH/TO Y/Y UH/Y
JackDell CF/TO CF/TO CF/Y Y/Y

Key:
Y: Good response with information
CF: Can't find host
UH: Unknown host
TO: Request timed out

Net View of Machine Summary
Response from net view
By Name/By IP
To
GatewayP4 JackT450 AWWLaptop JackDell
From GatewayP4 Y/Y 53/53 Y/Y Y/Y
JackT450 53/53 Y/Y 53/Y Y/Y
AWWLaptop 53/53 53/53 Y/Y 53/Y
JackDell 53/53 53/53 53/53 Y/Y

Key:
Y: Shows shares
53: Error 53

Ad Hoc Browser View
Response from net view
GatewayP4 Server list* *Not consistent
JackT450 Server List
AWWLaptop Error 6118
JackDell Server list



Here is the summary from from my ipconfig /all and browstat sta runs. I
notice my node types include Unknown , hybrid, and peer-to-peer, and
that GatewayP4 says browing is not active, but in previous browstat runs
in the last few days it has listed GatewayP4 or JackDell as the browser
(sometimes with an error 5.)

I see a bridge on Gatewayp4 and I know one of you pages says to get rid
of it, but I don't know how. (It bridges the Firewire and the network
adapter.)

Also, I tried to start browsing on Gatewayp4 thru control panel and it
says that it started and then stopped again right away.
Click to expand...

<SNIP>

Ed,

Here's the Error 6118.
http://support.microsoft.com/?id=298804

And regards the Bridge:
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge>
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge
Leading you to:
http://support.microsoft.com/?id=283429

AND here's the problem with AWWLaptop:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : AWWLaptop
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
<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

Fix the Bridge on Gatewayp4, and Node Type on AWWLaptop. Then rerun the tests.
If you can get AWWLaptop and Gatewayp4 sorted, and there are more problems, at
least the additional problems will be easier to identify. My bet is any
additional problems will be firewall - see the Error 6118 reference. But take
it one step at a time.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
 
E

Ed Katzman

<SNIP>

Ed,

Here's the Error 6118.
http://support.microsoft.com/?id=298804

And regards the Bridge:
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge>
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge
Leading you to:
http://support.microsoft.com/?id=283429

AND here's the problem with AWWLaptop:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : AWWLaptop
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
<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

Fix the Bridge on Gatewayp4, and Node Type on AWWLaptop. Then rerun the tests.
If you can get AWWLaptop and Gatewayp4 sorted, and there are more problems, at
least the additional problems will be easier to identify. My bet is any
additional problems will be firewall - see the Error 6118 reference. But take
it one step at a time.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
Click to expand...
Chuck: I think I have it all sorted out, but I wonder if I have left
vulnerabilities or problems.

Here is what I did:

Eliminated the bridge from Gatewayp4
Changed AWWLaptop from Peer-Peer (Now broadcast)
Turned off all (Software) firewalls completely (Before I had them on,
with "allow exceptions")
Disabled browser in all but Gatewayp4
Turned off all machines, then restarted Gatewayp4 first.

I do have a Linksys router with a firewall active. Do I need the
software firewall? Can I add them back?

I still get Unknown as node type on two machines. The fix in your
article didn't cause this to change. The article says this is probably
OK, so I guess I can leave it.

Do I need a backup browser? How do I get it running without messing up
what I have?

Thanks again. Ed
 
C

Chuck

Chuck: I think I have it all sorted out, but I wonder if I have left
vulnerabilities or problems.

Here is what I did:

Eliminated the bridge from Gatewayp4
Changed AWWLaptop from Peer-Peer (Now broadcast)
Turned off all (Software) firewalls completely (Before I had them on,
with "allow exceptions")
Disabled browser in all but Gatewayp4
Turned off all machines, then restarted Gatewayp4 first.

I do have a Linksys router with a firewall active. Do I need the
software firewall? Can I add them back?

I still get Unknown as node type on two machines. The fix in your
article didn't cause this to change. The article says this is probably
OK, so I guess I can leave it.

Do I need a backup browser? How do I get it running without messing up
what I have?

Thanks again. Ed
Click to expand...

Ed,

OK, good start! Windows Networking is lots of fun when there are multiple
problems.

Firstly, you only need a backup browser if the primary master browser is ever
likely to be offline, and if it will cripple your network if you can't use
Network Neighborhood while the primary master browser is offline.
<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

Node type Unknown is fine. Did the Microsoft fix not change it? If not, just
leave it be.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

Now, the issue of perimeter protection (NAT routers) vs individual protection
(personal firewalls) goes on frequently. My professional opinion is that you
need both.
<http://nitecruzr.blogspot.com/2005/05/please-protect-yourself-layer-your.html>
http://nitecruzr.blogspot.com/2005/05/please-protect-yourself-layer-your.html

Now that you have everything working, try and enable a personal firewall on one
computer, and configure it properly. When you get that one working, do another.
And so forth.

Just take it one step at a time.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Wkgrp Network of 3 XP and 1 2K stopped working 3
Internet Access on small LAN 5
Can I use a switch on a peer to peer network? 4
XP - Ping one way but not other? 0
XP - Ping one way but not other? 8
Trouble with shared folders 4
HELP 4
network issue with wired router and 2 XP pro PCs 3

Top