Chuck,
Here is the output from your "cdiag" script...
######## From the good machine (diablo) ###########
CDiagnosis V1.33
Start diagnosis for DIABLO
Enumerate Shares
Share name Resource Remark
-------------------------------------------------------------------------------
C$ C:\ Default share
ADMIN$ C:\WINNT Remote Admin
IPC$ Remote IPC
C C:\
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS.WINNT\DOCUMENTS
The command completed successfully.
Adhoc Browser View
Server Name Remark
-------------------------------------------------------------------------------
\\DIABLO Old System
\\MUNICH HP_System
The command completed successfully.
Full Targets munich 192.168.0.100 diablo 192.168.0.101 127.0.0.1
Target munich
"DIABLO ping munich"
Pinging munich [192.168.0.100] with 32 bytes of data:
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"DIABLO net view munich"
Target 192.168.0.100
"DIABLO ping 192.168.0.100"
Pinging 192.168.0.100 with 32 bytes of data:
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"DIABLO net view 192.168.0.100"
Target diablo
"DIABLO ping diablo"
Pinging diablo [192.168.0.101] with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"DIABLO net view diablo"
Shared resources at diablo
Old System
Share name Type Used as Comment
-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.
Target 192.168.0.101
"DIABLO ping 192.168.0.101"
Pinging 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"DIABLO net view 192.168.0.101"
Shared resources at 192.168.0.101
Old System
Share name Type Used as Comment
-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.
Target 127.0.0.1
"DIABLO 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
"DIABLO net view 127.0.0.1"
Shared resources at 127.0.0.1
Old System
Share name Type Used as Comment
-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.
Ping Targets
www.yahoo.com 66.94.230.32 192.168.0.1
Target
www.yahoo.com
"DIABLO ping www.yahoo.com"
Pinging
www.yahoo.akadns.net [66.94.230.37] with 32 bytes of data:
Reply from 66.94.230.37: bytes=32 time=39ms TTL=52
Reply from 66.94.230.37: bytes=32 time=26ms TTL=52
Reply from 66.94.230.37: bytes=32 time=26ms TTL=52
Reply from 66.94.230.37: bytes=32 time=35ms TTL=52
Ping statistics for 66.94.230.37:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 39ms, Average = 31ms
Target 66.94.230.32
"DIABLO ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:
Reply from 66.94.230.32: bytes=32 time=32ms TTL=52
Reply from 66.94.230.32: bytes=32 time=26ms TTL=52
Reply from 66.94.230.32: bytes=32 time=28ms TTL=52
Reply from 66.94.230.32: bytes=32 time=28ms TTL=52
Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 32ms, Average = 28ms
Target 192.168.0.1
"DIABLO ping 192.168.0.1"
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
End diagnosis for DIABLO
###############################################
NOTE: During this run, the following messages appeared in the command
window:
System error 5 has occurred.
Access is denied.
System error 5 has occurred.
Access is denied.
######## From the bad machine (munich) ###########
CDiagnosis V1.33
Start diagnosis for MUNICH
Enumerate Shares
Share name Resource Remark
-------------------------------------------------------------------------------
C$ C:\ Default share
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
H$ H:\ Default share
ADMIN$ C:\WINDOWS Remote Admin
IPC$ Remote IPC
My Pictures C:\Documents and Settings\don.MUNICH\My Documents\My
Pictures
Don's Photos
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS.WINDOWS\DOCUMENTS
Printer USB001 Spooled Samsung ML-1740 Series
Printer3 Microsoft Document Ima Spooled Microsoft Office Document
Image Wr
The command completed successfully.
Adhoc Browser View
Server Name Remark
-------------------------------------------------------------------------------
\\DIABLO Old System
\\MUNICH HP_System
The command completed successfully.
Full Targets munich 192.168.0.100 diablo 192.168.0.101 127.0.0.1
Target munich
"MUNICH ping munich"
Pinging munich [192.168.0.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
"MUNICH net view munich"
Shared resources at munich
HP_System
Share name Type Used as Comment
-------------------------------------------------------------------------------
My Pictures Disk Don's Photos
Printer Print Samsung ML-1740 Series
Printer3 Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.
Target 192.168.0.100
"MUNICH ping 192.168.0.100"
Pinging 192.168.0.100 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
"MUNICH net view 192.168.0.100"
Shared resources at 192.168.0.100
HP_System
Share name Type Used as Comment
-------------------------------------------------------------------------------
My Pictures Disk Don's Photos
Printer Print Samsung ML-1740 Series
Printer3 Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.
Target diablo
"MUNICH ping diablo"
Pinging diablo [192.168.0.101] with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"MUNICH net view diablo"
Shared resources at diablo
Old System
Share name Type Used as Comment
-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.
Target 192.168.0.101
"MUNICH ping 192.168.0.101"
Pinging 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"MUNICH net view 192.168.0.101"
Shared resources at 192.168.0.101
Old System
Share name Type Used as Comment
-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.
Target 127.0.0.1
"MUNICH 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
"MUNICH net view 127.0.0.1"
Ping Targets
www.yahoo.com 66.94.230.32 192.168.0.1
Target
www.yahoo.com
"MUNICH ping www.yahoo.com"
Pinging
www.yahoo.akadns.net [66.94.230.44] with 32 bytes of data:
Reply from 66.94.230.44: bytes=32 time=32ms TTL=52
Reply from 66.94.230.44: bytes=32 time=28ms TTL=52
Reply from 66.94.230.44: bytes=32 time=30ms TTL=52
Reply from 66.94.230.44: bytes=32 time=30ms TTL=52
Ping statistics for 66.94.230.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 32ms, Average = 30ms
Target 66.94.230.32
"MUNICH ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:
Reply from 66.94.230.32: bytes=32 time=44ms TTL=52
Reply from 66.94.230.32: bytes=32 time=28ms TTL=52
Reply from 66.94.230.32: bytes=32 time=28ms TTL=52
Reply from 66.94.230.32: bytes=32 time=30ms TTL=52
Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 44ms, Average = 32ms
Target 192.168.0.1
"MUNICH ping 192.168.0.1"
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
End diagnosis for MUNICH
###############################################
NOTE: During this run, the following messages appeared in the command
window:
System error 53 has occurred.
The network path was not found.
Also note that the shares on munich list "printer3" which I don't have
on my system. I think that I've tried to remove this from my printer
list before but I don't remember if it actually went away or not. It
may be back because of something that I've done in the process of
trying to fix this problem.
Don