Strange holes in an XP network

  • Thread starter Thread starter Martin Cleaver
  • Start date Start date
M

Martin Cleaver

I have several PCs connected in an XP Pro home network (with a Linux
file server) through a Linksys (wireless) router. They are all in a
workgroup. Yet some of the machines don't seem to be communicating
easily. They can all access the file server and wired network machines,
but for some reason some of the wirless machines can't communicate with
each other.
The only difference I can see on one difficult laptop machine (with
ipconfig /all) is that IP routing enabled is set to "yes" while on the
rest it is set to "no". Not that I would know how to change this
setting (can't find instructions anywhere under help).
Does anyone have a great miraculous answer to this silly problem?
Rgds
Martin
 
I have several PCs connected in an XP Pro home network (with a Linux
file server) through a Linksys (wireless) router. They are all in a
workgroup. Yet some of the machines don't seem to be communicating
easily. They can all access the file server and wired network machines,
but for some reason some of the wirless machines can't communicate with
each other.
The only difference I can see on one difficult laptop machine (with
ipconfig /all) is that IP routing enabled is set to "yes" while on the
rest it is set to "no". Not that I would know how to change this
setting (can't find instructions anywhere under help).
Does anyone have a great miraculous answer to this silly problem?
Rgds
Martin

Martin,

One of my XP computers has IP routing enabled, and the others don't. No problem
in my workgroup.

I'd bet your problem is more basic than that. Asymmetrical access / visibility
is a common problem with workgroups. It's usually caused by a misconfigured /
overlooked personal firewall, but there are 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

If no help, provide "browstat status" and "ipconfig /all" from each computer,
and 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
 
I tried Browstat and think I have found something:

V:\Windows\Netsoftware\Network\browstat>browstat status


Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8
DFD-791BD0E90037}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of br
owser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651
141D-C43C-4242-8DFD-791BD0E90037}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651
141D-C43C-4242-8DFD-791BD0E90037}

One domain and eight servers... ?

Rgds

Martin
 
I tried Browstat and think I have found something:

V:\Windows\Netsoftware\Network\browstat>browstat status


Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8
DFD-791BD0E90037}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of br
owser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651
141D-C43C-4242-8DFD-791BD0E90037}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651
141D-C43C-4242-8DFD-791BD0E90037}

One domain and eight servers... ?

Rgds

Martin

Martin,

A server is any computer running the Server service, ie File and Printer Sharing
for Microsoft Networks. Generally, every computer will show up as a server.

Browstat is most useful when run on each computer. Minimally, if you have 3 or
more computers, run it (and "ipconfig /all") from the problem computer(s), and
from 2 properly working computers.

Now, what's the "error = 2"? Well, you said that you have a Linux server in the
workgroup. Linux servers work fine when there's no problems. Unfortunately,
the error codes that they create, when there's a problem, leave no resemblance
to Microsoft documented codes, that I have found. I bet we're going to have to
look at the distro (name and version) of the server.
 
The Linux Machine is running Suse 8.3...
The problem machines are SpotAcer (my laptop) and FayIan (my kids).
Shuttle is wired and has no problems.

CDiag says:

CDiagnosis V1.33
Start diagnosis for FAYIAN

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
D$ D:\ Default share

C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

FayIanC C:\
FayIanD D:\
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\ALTO Samba 3.0.12-5-SUSE

\\FAYIAN Fay and Ian's PC

\\FUJITSU Ian's Fujitsu

\\NAS Linksys server

\\SHUTTLE Shuttle

\\SPOTACER Spot Acer Notebook

\\SPOTVIDEO Spot Video test machnie

\\VAIODESK Desktop Vaio

The command completed successfully.


Full Targets 127.0.0.1

Target 127.0.0.1

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


"FAYIAN net view 127.0.0.1"

Shared resources at 127.0.0.1

Fay and Ian's PC

Share name Type Used as Comment

-------------------------------------------------------------------------------
FayIanC Disk
FayIanD Disk
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"FAYIAN ping www.yahoo.com"



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



Reply from 216.109.117.206: bytes=32 time=249ms TTL=52

Reply from 216.109.117.206: bytes=32 time=381ms TTL=52

Reply from 216.109.117.206: bytes=32 time=288ms TTL=52

Reply from 216.109.117.206: bytes=32 time=539ms TTL=52



Ping statistics for 216.109.117.206:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 249ms, Maximum = 539ms, Average = 364ms


Target 66.94.230.32

"FAYIAN ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=415ms TTL=52

Reply from 66.94.230.32: bytes=32 time=418ms TTL=51

Reply from 66.94.230.32: bytes=32 time=298ms TTL=51

Reply from 66.94.230.32: bytes=32 time=640ms TTL=51



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 298ms, Maximum = 640ms, Average = 442ms


End diagnosis for FAYIAN


CDiagnosis V1.33
Start diagnosis for SPOTACER

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC

print$ C:\WINDOWS\System32\SPOOL\drivers
Printer Drivers

ADMIN$ C:\WINDOWS Remote Admin

C$ C:\ Default share

ACERC C:\
Acerdocs C:\Documents and Settings\Martin\My Documents

Files C:\Files

SharedDocs C:\Documents and Settings\All Users\Documents

Video C:\Video
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\ALTO Samba 3.0.12-5-SUSE

\\FAYIAN Fay and Ian's PC

\\FUJITSU Ian's Fujitsu

\\NAS Linksys server

\\SHUTTLE Shuttle

\\SPOTACER Spot Acer Notebook

\\SPOTVIDEO Spot Video test machnie

\\VAIODESK Desktop Vaio

The command completed successfully.


Full Targets 127.0.0.1

Target 127.0.0.1

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


"SPOTACER net view 127.0.0.1"

Shared resources at 127.0.0.1

Spot Acer Notebook

Share name Type Used as Comment

-------------------------------------------------------------------------------
ACERC Disk
Acerdocs Disk
CleaveM Disk
Files Disk
PB-DB Disk
SharedDocs Disk
Video Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"SPOTACER ping www.yahoo.com"



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



Reply from 216.109.118.70: bytes=32 time=102ms TTL=52

Reply from 216.109.118.70: bytes=32 time=103ms TTL=52

Reply from 216.109.118.70: bytes=32 time=102ms TTL=52

Reply from 216.109.118.70: bytes=32 time=113ms TTL=52



Ping statistics for 216.109.118.70:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 102ms, Maximum = 113ms, Average = 105ms


Target 66.94.230.32

"SPOTACER ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=185ms TTL=52

Reply from 66.94.230.32: bytes=32 time=200ms TTL=52

Reply from 66.94.230.32: bytes=32 time=182ms TTL=51

Reply from 66.94.230.32: bytes=32 time=183ms TTL=51



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 182ms, Maximum = 200ms, Average = 187ms


End diagnosis for SPOTACER

Browstat FayIan:


Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{DBF361A9-D9C0-411A-B620-8CB8F32D409C}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of browser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{DBF361A9-D9C0-411A-B620-8CB8F32D409C}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{DBF361A9-D9C0-411A-B620-8CB8F32D409C}

Browstat Shuttle:


Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8DFD-791BD0E90037}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of browser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8DFD-791BD0E90037}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8DFD-791BD0E90037}

Browstat SpotAcer:



Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{93ADD945-8549-422F-8E39-D4F1EF825BC8}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of browser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{93ADD945-8549-422F-8E39-D4F1EF825BC8}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{93ADD945-8549-422F-8E39-D4F1EF825BC8}

Does that help?

BTW: Happy Xmas!

Greetings

Martin
 
The Linux Machine is running Suse 8.3...
The problem machines are SpotAcer (my laptop) and FayIan (my kids).
Shuttle is wired and has no problems.

CDiag says:

CDiagnosis V1.33
Start diagnosis for FAYIAN

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
D$ D:\ Default share

C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

FayIanC C:\
FayIanD D:\
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\ALTO Samba 3.0.12-5-SUSE

\\FAYIAN Fay and Ian's PC

\\FUJITSU Ian's Fujitsu

\\NAS Linksys server

\\SHUTTLE Shuttle

\\SPOTACER Spot Acer Notebook

\\SPOTVIDEO Spot Video test machnie

\\VAIODESK Desktop Vaio

The command completed successfully.


Full Targets 127.0.0.1

Target 127.0.0.1

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


"FAYIAN net view 127.0.0.1"

Shared resources at 127.0.0.1

Fay and Ian's PC

Share name Type Used as Comment

-------------------------------------------------------------------------------
FayIanC Disk
FayIanD Disk
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"FAYIAN ping www.yahoo.com"



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



Reply from 216.109.117.206: bytes=32 time=249ms TTL=52

Reply from 216.109.117.206: bytes=32 time=381ms TTL=52

Reply from 216.109.117.206: bytes=32 time=288ms TTL=52

Reply from 216.109.117.206: bytes=32 time=539ms TTL=52



Ping statistics for 216.109.117.206:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 249ms, Maximum = 539ms, Average = 364ms


Target 66.94.230.32

"FAYIAN ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=415ms TTL=52

Reply from 66.94.230.32: bytes=32 time=418ms TTL=51

Reply from 66.94.230.32: bytes=32 time=298ms TTL=51

Reply from 66.94.230.32: bytes=32 time=640ms TTL=51



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 298ms, Maximum = 640ms, Average = 442ms


End diagnosis for FAYIAN


CDiagnosis V1.33
Start diagnosis for SPOTACER

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC

print$ C:\WINDOWS\System32\SPOOL\drivers
Printer Drivers

ADMIN$ C:\WINDOWS Remote Admin

C$ C:\ Default share

ACERC C:\
Acerdocs C:\Documents and Settings\Martin\My Documents

Files C:\Files

SharedDocs C:\Documents and Settings\All Users\Documents

Video C:\Video
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\ALTO Samba 3.0.12-5-SUSE

\\FAYIAN Fay and Ian's PC

\\FUJITSU Ian's Fujitsu

\\NAS Linksys server

\\SHUTTLE Shuttle

\\SPOTACER Spot Acer Notebook

\\SPOTVIDEO Spot Video test machnie

\\VAIODESK Desktop Vaio

The command completed successfully.


Full Targets 127.0.0.1

Target 127.0.0.1

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


"SPOTACER net view 127.0.0.1"

Shared resources at 127.0.0.1

Spot Acer Notebook

Share name Type Used as Comment

-------------------------------------------------------------------------------
ACERC Disk
Acerdocs Disk
CleaveM Disk
Files Disk
PB-DB Disk
SharedDocs Disk
Video Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"SPOTACER ping www.yahoo.com"



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



Reply from 216.109.118.70: bytes=32 time=102ms TTL=52

Reply from 216.109.118.70: bytes=32 time=103ms TTL=52

Reply from 216.109.118.70: bytes=32 time=102ms TTL=52

Reply from 216.109.118.70: bytes=32 time=113ms TTL=52



Ping statistics for 216.109.118.70:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 102ms, Maximum = 113ms, Average = 105ms


Target 66.94.230.32

"SPOTACER ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=185ms TTL=52

Reply from 66.94.230.32: bytes=32 time=200ms TTL=52

Reply from 66.94.230.32: bytes=32 time=182ms TTL=51

Reply from 66.94.230.32: bytes=32 time=183ms TTL=51



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 182ms, Maximum = 200ms, Average = 187ms


End diagnosis for SPOTACER

Browstat FayIan:


Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{DBF361A9-D9C0-411A-B620-8CB8F32D409C}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of browser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{DBF361A9-D9C0-411A-B620-8CB8F32D409C}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{DBF361A9-D9C0-411A-B620-8CB8F32D409C}

Browstat Shuttle:


Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8DFD-791BD0E90037}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of browser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8DFD-791BD0E90037}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{8651141D-C43C-4242-8DFD-791BD0E90037}

Browstat SpotAcer:



Status for domain CLEAVER on transport
\Device\NetBT_Tcpip_{93ADD945-8549-422F-8E39-D4F1EF825BC8}
Browsing is active on domain.
Master browser name is: ALTO
Could not open key in registry, error = 2 Unable to determine
build of browser master: 2
\\\\ALTO . Version:04.09 Flags: 9a0b NT CONTROLLER
SERVER
1 backup servers retrieved from master ALTO
\\ALTO
There are 8 servers in domain CLEAVER on transport
\Device\NetBT_Tcpip_{93ADD945-8549-422F-8E39-D4F1EF825BC8}
There are 1 domains in domain CLEAVER on transport
\Device\NetBT_Tcpip_{93ADD945-8549-422F-8E39-D4F1EF825BC8}

Does that help?

BTW: Happy Xmas!

Greetings

Martin

Happy Xmas, Martin!

OK, as I feared the Linux (SUSE) box is the master browser. All 3 example
computers (FayIan, Shuttle, and SpotAcer) acknowledge the same master browser,
Alto, and get the same results. So you don't have a master browser conflict.

Now then your CDiag logs leave a lot of detail out. Please take a look at my
CDiag documentation, to see what the log should look like.
<http://nitecruzr.blogspot.com/2005/05/interpreting-cdiag-output-and-solving.html>
http://nitecruzr.blogspot.com/2005/05/interpreting-cdiag-output-and-solving.html

Are SpotAcer and FayIan both connecting wirelessly? Are they the only wireless
computers? I don't see any clues in "browstat status" - how about "ipconfig
/all"?
 
How can my CDiag leave out a lot of detail? I thought I had made the
necessary changes to the batch file to make it run?
Or did I do something wrong?
Rgds
Martin
 
How can my CDiag leave out a lot of detail? I thought I had made the
necessary changes to the batch file to make it run?
Or did I do something wrong?
Rgds
Martin

Martin,

I'm not sure. Let's make sure there were no typos, and start over with
"ipconfig /all" from each computer.
 
Okay... here we go:

Shuttle (wired - no problem):



Windows IP Configuration



Host Name . . . . . . . . . . . . : Shuttle

Primary Dns Suffix . . . . . . . : cleaver.nl

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

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

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

DNS Suffix Search List. . . . . . : cleaver.nl

domain_not_set.invalid



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . : domain_not_set.invalid

Description . . . . . . . . . . . : NVIDIA nForce MCP
Networking Controller

Physical Address. . . . . . . . . : 00-30-1B-AF-6C-16

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.0.0.65

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

Default Gateway . . . . . . . . . : 10.0.0.138

DHCP Server . . . . . . . . . . . : 10.0.0.138

DNS Servers . . . . . . . . . . . : 194.109.6.66

194.109.9.99

194.109.104.104

10.0.0.138

Lease Obtained. . . . . . . . . . : 27 December 2005 12:44:39

Lease Expires . . . . . . . . . . : 28 December 2005 12:44:39



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft TV/Video
Connection

Physical Address. . . . . . . . . : 00-00-00-00-00-00

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

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 0.1.0.4

Subnet Mask . . . . . . . . . . . : 255.255.255.255

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


FayIan (Spotacer can't connect):



Windows IP Configuration



Host Name . . . . . . . . . . . . : fayian

Primary Dns Suffix . . . . . . . : cleaver.nl

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

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

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

DNS Suffix Search List. . . . . . : cleaver.nl

domain_not_set.invalid



Ethernet adapter Wireless Network Connection 3:



Connection-specific DNS Suffix . : domain_not_set.invalid

Description . . . . . . . . . . . : 802.11b+g USB Wireless LAN
Adapter

Physical Address. . . . . . . . . : 00-50-FC-8C-A8-95

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.0.0.64

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

Default Gateway . . . . . . . . . : 10.0.0.138

DHCP Server . . . . . . . . . . . : 10.0.0.138

DNS Servers . . . . . . . . . . . : 194.109.6.66

194.109.9.99

194.109.104.104

10.0.0.138

Lease Obtained. . . . . . . . . . : 27 December 2005 12:46:13

Lease Expires . . . . . . . . . . : 28 December 2005 12:46:13

SpotAcer (Can't connect with FayIan):



Windows IP Configuration



Host Name . . . . . . . . . . . . : SpotAcer

Primary Dns Suffix . . . . . . . : cleaver.nl

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

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

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

DNS Suffix Search List. . . . . . : cleaver.nl

domain_not_set.invalid



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : domain_not_set.invalid

Description . . . . . . . . . . . : Intel(R) PRO/Wireless
2200BG Network Connection

Physical Address. . . . . . . . . : 00-0E-35-4B-11-83

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.0.0.70

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

Default Gateway . . . . . . . . . : 10.0.0.138

DHCP Server . . . . . . . . . . . : 10.0.0.138

DNS Servers . . . . . . . . . . . : 194.109.6.66

194.109.9.99

194.109.104.104

10.0.0.138

Lease Obtained. . . . . . . . . . : 27 December 2005 14:59:37

Lease Expires . . . . . . . . . . : 28 December 2005 14:59:37

Fujitsi (no problems, wireless):



Windows IP Configuration



Host Name . . . . . . . . . . . . : FUJITSU

Primary Dns Suffix . . . . . . . : cleaver.nl

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

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

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

DNS Suffix Search List. . . . . . : cleaver.nl

domain_not_set.invalid



Ethernet adapter Local Area Connection:



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

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
Fast Ethernet NIC

Physical Address. . . . . . . . . : 00-E0-00-C1-B4-06



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : domain_not_set.invalid

Description . . . . . . . . . . . : Intersil PRISM Wireless LAN
PCI Card

Physical Address. . . . . . . . . : 00-E0-00-8D-C5-13

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.0.0.69

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

Default Gateway . . . . . . . . . : 10.0.0.138

DHCP Server . . . . . . . . . . . : 10.0.0.138

DNS Servers . . . . . . . . . . . : 194.109.6.66

194.109.9.99

194.109.104.104

10.0.0.138

Lease Obtained. . . . . . . . . . : Tuesday, December 27, 2005
4:55:19 PM

Lease Expires . . . . . . . . . . : Wednesday, December 28,
2005 4:55:19 PM



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft TV/Video
Connection

Physical Address. . . . . . . . . : 00-00-00-00-00-00

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

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 0.1.0.5

Subnet Mask . . . . . . . . . . . : 255.255.255.255

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


Xmas Greetings

Martin
 
Okay... here we go:

Xmas Greetings

Martin

Christmas Greetings, and Happy Flu Season to you, Martin! This is what a CDiag
should contain.

Take the following code (everything inside the "#####"). (Please verify computer
names and ip addresses) (accuracy here is crucial!).

1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
into Notepad. Verify, and correct, names and addresses if necessary.
2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
folder "C:\".
3. Run it by Start - Run - "c:\cdiag".
4. Wait patiently.
5. When Notepad opens up displaying c:\cdiag.txt, first check Format and
ensure that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A
Ctrl-C) and paste (Ctrl-V) into your next post.

Do this from all computers, please, with all computers powered up and online.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=Shuttle 10.0.0.65
set FullTarget2=fayian 10.0.0.64
set FullTarget3=SpotAcer 10.0.0.70
set FullTarget4=FUJITSU 10.0.0.69
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 10.0.0.138
Set Version=V1.33
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
for %%a in (%FullTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
for %%a in (%PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

##### End CDiag Assembled Code
 
Aha...
IO tried it first on SHuttle and got a few errors:

C:\>net view \par 1>>c:\\cdiag.txt
System error 123 has occurred.

The filename, directory name, or vol

\par was unexpected at this time.

C:\>) \par

C:\>cdiag
System error 53 has occurred.

The network path was not found.

System error 53 has occurred.

The network path was not found.

The file is
CDiagnosis V1.33
Start diagnosis for SHUTTLE

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
print$ C:\WINDOWS\System32\spool\drivers
Printer Drivers

ADMIN$ C:\WINDOWS Remote Admin

C$ C:\ Default share

IPC$ Remote IPC

Documents Back
C:\Server\Documents Back
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

ShuttleC C:\
Video C:\Video Video on Shuttle

Magicolor 2300
IP_10.0.0.254 Spooled magicolor 2300 DL

The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\ALTO Samba 3.0.12-5-SUSE

\\FAYIAN Fay and Ian's PC

\\NAS Linksys server

\\SHUTTLE Shuttle

\\SPOTACER Spot Acer Notebook

\\SPOTVIDEO Spot Video test machnie

\\VAIODESK Desktop Vaio

The command completed successfully.


Full Targets Shuttle 10.0.0.65 fayian 10.0.0.64 SpotAcer 10.0.0.70
FUJITSU 10.0.0.69 127.0.0.1

Target Shuttle

"SHUTTLE ping Shuttle"



Pinging Shuttle.cleaver.nl [10.0.0.65] with 32 bytes of data:



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

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

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

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



Ping statistics for 10.0.0.65:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"SHUTTLE net view Shuttle"

Shared resources at Shuttle

Shuttle

Share name Type Used as Comment

-------------------------------------------------------------------------------
Documents Back Disk
Magicolor 2300 Print magicolor 2300 DL
SharedDocs Disk
ShuttleC Disk
Video Disk Video on Shuttle
The command completed successfully.


Target 10.0.0.65

"SHUTTLE ping 10.0.0.65"



Pinging 10.0.0.65 with 32 bytes of data:



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

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

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

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



Ping statistics for 10.0.0.65:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"SHUTTLE net view 10.0.0.65"

Shared resources at 10.0.0.65

Shuttle

Share name Type Used as Comment

-------------------------------------------------------------------------------
Documents Back Disk
Magicolor 2300 Print magicolor 2300 DL
SharedDocs Disk
ShuttleC Disk
Video Disk Video on Shuttle
The command completed successfully.


Target fayian

"SHUTTLE ping fayian"



Pinging fayian [10.0.0.64] with 32 bytes of data:



Request timed out.

Reply from 10.0.0.64: bytes=32 time=50ms TTL=128

Reply from 10.0.0.64: bytes=32 time=99ms TTL=128

Reply from 10.0.0.64: bytes=32 time=225ms TTL=128



Ping statistics for 10.0.0.64:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 50ms, Maximum = 225ms, Average = 124ms


"SHUTTLE net view fayian"

Shared resources at fayian

Fay and Ian's PC

Share name Type Used as Comment

-------------------------------------------------------------------------------
FayIanC Disk
FayIanD Disk
SharedDocs Disk
The command completed successfully.


Target 10.0.0.64

"SHUTTLE ping 10.0.0.64"



Pinging 10.0.0.64 with 32 bytes of data:



Reply from 10.0.0.64: bytes=32 time=11ms TTL=128

Reply from 10.0.0.64: bytes=32 time=9ms TTL=128

Reply from 10.0.0.64: bytes=32 time=2ms TTL=128

Reply from 10.0.0.64: bytes=32 time=2ms TTL=128



Ping statistics for 10.0.0.64:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 11ms, Average = 6ms


"SHUTTLE net view 10.0.0.64"

Shared resources at 10.0.0.64

Fay and Ian's PC

Share name Type Used as Comment

-------------------------------------------------------------------------------
FayIanC Disk
FayIanD Disk
SharedDocs Disk
The command completed successfully.


Target SpotAcer

"SHUTTLE ping SpotAcer"



Pinging SpotAcer [10.0.0.70] with 32 bytes of data:



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

Reply from 10.0.0.70: bytes=32 time=2ms TTL=128

Reply from 10.0.0.70: bytes=32 time=2ms TTL=128

Reply from 10.0.0.70: bytes=32 time=2ms TTL=128



Ping statistics for 10.0.0.70:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms


"SHUTTLE net view SpotAcer"

Shared resources at SpotAcer

Spot Acer Notebook

Share name Type Used as Comment

-------------------------------------------------------------------------------
ACERC Disk
Acerdocs Disk
CleaveM Disk
Files Disk
PB-DB Disk
SharedDocs Disk
Video Disk
The command completed successfully.


Target 10.0.0.70

"SHUTTLE ping 10.0.0.70"



Pinging 10.0.0.70 with 32 bytes of data:



Reply from 10.0.0.70: bytes=32 time=2ms TTL=128

Reply from 10.0.0.70: bytes=32 time=2ms TTL=128

Reply from 10.0.0.70: bytes=32 time=2ms TTL=128

Reply from 10.0.0.70: bytes=32 time=2ms TTL=128



Ping statistics for 10.0.0.70:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 2ms, Average = 2ms


"SHUTTLE net view 10.0.0.70"

Shared resources at 10.0.0.70

Spot Acer Notebook

Share name Type Used as Comment

-------------------------------------------------------------------------------
ACERC Disk
Acerdocs Disk
CleaveM Disk
Files Disk
PB-DB Disk
SharedDocs Disk
Video Disk
The command completed successfully.


Target FUJITSU

"SHUTTLE ping FUJITSU"

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


"SHUTTLE net view FUJITSU"


Target 10.0.0.69

"SHUTTLE ping 10.0.0.69"



Pinging 10.0.0.69 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 10.0.0.69:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"SHUTTLE net view 10.0.0.69"


Target 127.0.0.1

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


"SHUTTLE net view 127.0.0.1"

Shared resources at 127.0.0.1

Shuttle

Share name Type Used as Comment

-------------------------------------------------------------------------------
Documents Back Disk
Magicolor 2300 Print magicolor 2300 DL
SharedDocs Disk
ShuttleC Disk
Video Disk Video on Shuttle
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 10.0.0.138

Target www.yahoo.com

"SHUTTLE ping www.yahoo.com"



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



Reply from 68.142.226.42: bytes=32 time=100ms TTL=52

Reply from 68.142.226.42: bytes=32 time=100ms TTL=52

Reply from 68.142.226.42: bytes=32 time=99ms TTL=53

Reply from 68.142.226.42: bytes=32 time=100ms TTL=53



Ping statistics for 68.142.226.42:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 99ms, Maximum = 100ms, Average = 99ms


Target 66.94.230.32

"SHUTTLE ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=181ms TTL=52

Reply from 66.94.230.32: bytes=32 time=181ms TTL=52

Reply from 66.94.230.32: bytes=32 time=181ms TTL=51

Reply from 66.94.230.32: bytes=32 time=181ms TTL=51



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 181ms, Maximum = 181ms, Average = 181ms


Target 10.0.0.138

"SHUTTLE ping 10.0.0.138"



Pinging 10.0.0.138 with 32 bytes of data:



Reply from 10.0.0.138: bytes=32 time=1ms TTL=255

Reply from 10.0.0.138: bytes=32 time=1ms TTL=255

Reply from 10.0.0.138: bytes=32 time<1ms TTL=255

Reply from 10.0.0.138: bytes=32 time=1ms TTL=255



Ping statistics for 10.0.0.138:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 1ms, Average = 0ms


End diagnosis for SHUTTLE

I'll try Spotacer next.
 
Here's the same from SpotAcer:

CDiagnosis V1.33
Start diagnosis for SPOTACER

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC

print$ C:\WINDOWS\System32\SPOOL\drivers
Printer Drivers

ADMIN$ C:\WINDOWS Remote Admin

C$ C:\ Default share

ACERC C:\
Acerdocs C:\Documents and Settings\Martin\My Documents

CleaveM c:\Documents and Settings\Martin\My
Documents\Server\Palm\CleaveM

Files C:\Files
PB-DB C:\Program Files\Postbank\Postbank Girotel Zakelijk\DB

SharedDocs C:\Documents and Settings\All Users\Documents

Video C:\Video
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\ALTO Samba 3.0.12-5-SUSE

\\FAYIAN Fay and Ian's PC

\\NAS Linksys server

\\SHUTTLE Shuttle

\\SPOTACER Spot Acer Notebook

\\SPOTVIDEO Spot Video test machnie

\\VAIODESK Desktop Vaio

The command completed successfully.


Full Targets Shuttle 10.0.0.65 fayian 10.0.0.64 SpotAcer 10.0.0.70
FUJITSU 10.0.0.69 127.0.0.1

Target Shuttle

"SPOTACER ping Shuttle"



Pinging Shuttle [10.0.0.65] with 32 bytes of data:



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

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

Reply from 10.0.0.65: bytes=32 time=2ms TTL=128

Reply from 10.0.0.65: bytes=32 time=3ms TTL=128



Ping statistics for 10.0.0.65:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 3ms, Average = 1ms


"SPOTACER net view Shuttle"

Shared resources at Shuttle

Shuttle

Share name Type Used as Comment

-------------------------------------------------------------------------------
Documents Back Disk
Magicolor 2300 Print magicolor 2300 DL
SharedDocs Disk
ShuttleC Disk
Video Disk Video on Shuttle
The command completed successfully.


Target 10.0.0.65

"SPOTACER ping 10.0.0.65"



Pinging 10.0.0.65 with 32 bytes of data:



Reply from 10.0.0.65: bytes=32 time=2ms TTL=128

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

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

Reply from 10.0.0.65: bytes=32 time=2ms TTL=128



Ping statistics for 10.0.0.65:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms


"SPOTACER net view 10.0.0.65"

Shared resources at 10.0.0.65

Shuttle

Share name Type Used as Comment

-------------------------------------------------------------------------------
Documents Back Disk
Magicolor 2300 Print magicolor 2300 DL
SharedDocs Disk
ShuttleC Disk
Video Disk Video on Shuttle
The command completed successfully.


Target fayian

"SPOTACER ping fayian"

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


"SPOTACER net view fayian"


Target 10.0.0.64

"SPOTACER ping 10.0.0.64"



Pinging 10.0.0.64 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 10.0.0.64:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"SPOTACER net view 10.0.0.64"


Target SpotAcer

"SPOTACER ping SpotAcer"



Pinging SpotAcer.cleaver.nl [10.0.0.70] with 32 bytes of data:



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

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

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

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



Ping statistics for 10.0.0.70:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"SPOTACER net view SpotAcer"

Shared resources at SpotAcer

Spot Acer Notebook

Share name Type Used as Comment

-------------------------------------------------------------------------------
ACERC Disk
Acerdocs Disk
CleaveM Disk
Files Disk
PB-DB Disk
SharedDocs Disk
Video Disk
The command completed successfully.


Target 10.0.0.70

"SPOTACER ping 10.0.0.70"



Pinging 10.0.0.70 with 32 bytes of data:



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

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

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

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



Ping statistics for 10.0.0.70:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"SPOTACER net view 10.0.0.70"

Shared resources at 10.0.0.70

Spot Acer Notebook

Share name Type Used as Comment

-------------------------------------------------------------------------------
ACERC Disk
Acerdocs Disk
CleaveM Disk
Files Disk
PB-DB Disk
SharedDocs Disk
Video Disk
The command completed successfully.


Target FUJITSU

"SPOTACER ping FUJITSU"

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


"SPOTACER net view FUJITSU"


Target 10.0.0.69

"SPOTACER ping 10.0.0.69"



Pinging 10.0.0.69 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 10.0.0.69:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"SPOTACER net view 10.0.0.69"


Target 127.0.0.1

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


"SPOTACER net view 127.0.0.1"

Shared resources at 127.0.0.1

Spot Acer Notebook

Share name Type Used as Comment

-------------------------------------------------------------------------------
ACERC Disk
Acerdocs Disk
CleaveM Disk
Files Disk
PB-DB Disk
SharedDocs Disk
Video Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 10.0.0.138

Target www.yahoo.com

"SPOTACER ping www.yahoo.com"



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



Reply from 68.142.226.33: bytes=32 time=100ms TTL=53

Reply from 68.142.226.33: bytes=32 time=100ms TTL=53

Reply from 68.142.226.33: bytes=32 time=101ms TTL=52

Reply from 68.142.226.33: bytes=32 time=107ms TTL=52



Ping statistics for 68.142.226.33:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 100ms, Maximum = 107ms, Average = 102ms


Target 66.94.230.32

"SPOTACER ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=544ms TTL=52

Reply from 66.94.230.32: bytes=32 time=439ms TTL=52

Reply from 66.94.230.32: bytes=32 time=182ms TTL=51

Reply from 66.94.230.32: bytes=32 time=183ms TTL=51



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 182ms, Maximum = 544ms, Average = 337ms


Target 10.0.0.138

"SPOTACER ping 10.0.0.138"



Pinging 10.0.0.138 with 32 bytes of data:



Reply from 10.0.0.138: bytes=32 time=2ms TTL=255

Reply from 10.0.0.138: bytes=32 time=1ms TTL=255

Reply from 10.0.0.138: bytes=32 time=1ms TTL=255

Reply from 10.0.0.138: bytes=32 time=2ms TTL=255



Ping statistics for 10.0.0.138:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms


End diagnosis for SPOTACER
 
By the way it's really cool of you to spend some time on my hassles in
this festive season! :)

Thanbx

Martin
 
By the way it's really cool of you to spend some time on my hassles in
this festive season! :)

Thanbx

Martin

Tis the season, Martin.

Colds and flu.
And staying inside and trying to find something to do.
Daytime TV sux.

Anyway, Shuttle and SpotAcer both have interesting problems. Now, Alto and NAS
are not diagnosable, but FayIan, SpotVideo, and VaioDesk should provide useful
insight. And Fujitsu, since both Shuttle and SpotAcer have problems seeing it.
 
Back
Top