No computer A hom200of001 does not have a personal firewall. I assume your
next sentence refers to computer D. Yes, computer B hom200of002 and D
hom100of001 have Norton Internet Security 2007 and have the most problems.
Computer E was dropped off the network. Computer C P933iii will be dropped as
well to simplify things. To further simplify things. Computer D will be moved
from Wireless to wired. It occurred to me that maybe the wireless link is too
slow and Norton Internet Security has decided it is on the network alone and
has clamped things down.
Since I changed things, I will verify I have the same conditions as before.
I see same Windows Explorer Mshome computer icons (even though P933iii
doesn’t exist). My Network Places is the same. I can ping from hom200of002
to hom200of001 but not to hom200fr001. I will remove the results to try to
fit in the space allowed.
Removed Norton Internet Security 2007 computer D hom100fr001.
Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Did not check hom200of002
Computer A can create a file and store it into Computer D through Windows
Explorer Mshome computer icons. Did not check hom200of002
Computer A can ping using ping hom100fr001. Did not check hom200of002
Computer B hom200of002 doesn’t show hom100fr001 in My Network Neighborhood
Computer B can’t access hom100fr001 using Windows Explorer Mshome computer
icons. Get Mshome is not accessible.
Computer B can ping hom100fr001 using the IP address but not using the
computer name.
Computer D doesn’t show anything in My Network Neighborhood
Computer D can’t access Windows Explorer Mshome computer icons. Get Mshome
is not accessible.
Computer D can ping hom200of001 but not hom200of002.
Removed Norton Internet Security 2007 Computer B hom200of002.
Computer A Hom200of001 //hom100fr001/tmp showed up in My Network Places.
Computer A can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer A can ping using ping hom100fr001.
Computer B hom200of002 shows hom100fr001 in My Network Neighborhood
Computer B can modified a file on hom100fr001 through Windows Explorer
Mshome computer icons
Computer B can ping hom100fr001 and hom200of001 using the computer name.
Computer D shows in My Network Neighborhood
\\Hom200of001\tmp
\\Hom200of002\Image Library
\\Hom200of002\PictureProject
\\Hom200of002\SharedDocs
\\Hom100fr001\tmp
Computer D can modified a file on hom200of001 and hom200of002 through
Windows Explorer Mshome computer icons
Computer D can ping hom200of001 and hom200of002 using computer name.
Meantime
Computer B
Computer D
Start CPSServ V1.10 - HOM100FR001
Find Computer Browser ("browser")
Checking \\HOM100FR001... Found browser on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Find DHCP Client ("dhcp")
Checking \\HOM100FR001... Found dhcp on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Find TCP/IP NetBIOS Helper ("lmhosts")
Checking \\HOM100FR001... Found lmhosts on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Find Remote Registry ("remoteregistry")
Checking \\HOM100FR001... Found remoteregistry on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Find Server ("server")
Checking \\HOM100FR001... Found server on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Find WF / ICS ("sharedaccess")
Checking \\HOM100FR001... Found sharedaccess on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
Find Workstation ("workstation")
Checking \\HOM100FR001... Found workstation on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:
End CPSServ V1.10 - HOM100FR001
CDiagnosis V1.40
Start diagnosis for HOM100FR001
Full Targets hom200of001 192.168.1.103 hom200of002 192.168.1.100 hom100fr001
192.168.1.105 127.0.0.1
Ping Targets
www.yahoo.com 66.94.230.32 192.168.1.1
Over All Analysis
Enumerate Shares
Share name Resource Remark
-------------------------------------------------------------------------------
C$ C:\ Default share
ADMIN$ C:\WINDOWS Remote Admin
IPC$ Remote IPC
tmp C:\tmp
The command completed successfully.
Adhoc Browser View
Server Name Remark
-------------------------------------------------------------------------------
\\HOM100FR001
\\HOM200OF001
\\HOM200OF002
The command completed successfully.
Full Targets Analysis hom200of001 192.168.1.103 hom200of002 192.168.1.100
hom100fr001 192.168.1.105 127.0.0.1
Target hom200of001
"HOM100FR001 ping hom200of001"
Pinging hom200of001 [192.168.1.103] with 32 bytes of data:
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"HOM100FR001 net view hom200of001"
Shared resources at hom200of001
Share name Type Used as Comment
-------------------------------------------------------------------------------
PSC2410 Print hp psc 2400 series
tmp Disk (UNC)
The command completed successfully.
Target 192.168.1.103
"HOM100FR001 ping 192.168.1.103"
Pinging 192.168.1.103 with 32 bytes of data:
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"HOM100FR001 net view 192.168.1.103"
Shared resources at 192.168.1.103
Share name Type Used as Comment
-------------------------------------------------------------------------------
PSC2410 Print hp psc 2400 series
tmp Disk
The command completed successfully.
Target hom200of002
"HOM100FR001 ping hom200of002"
Pinging hom200of002 [192.168.1.100] with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"HOM100FR001 net view hom200of002"
Shared resources at hom200of002
Share name Type Used as Comment
-------------------------------------------------------------------------------
Image Library Disk
PictureProject Disk
SharedDocs Disk
Tmp Disk
The command completed successfully.
Target 192.168.1.100
"HOM100FR001 ping 192.168.1.100"
Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"HOM100FR001 net view 192.168.1.100"
Shared resources at 192.168.1.100
Share name Type Used as Comment
-------------------------------------------------------------------------------
Image Library Disk
PictureProject Disk
SharedDocs Disk
Tmp Disk
The command completed successfully.
Target hom100fr001
"HOM100FR001 ping hom100fr001"
Pinging hom100fr001 [192.168.1.105] with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"HOM100FR001 net view hom100fr001"
Shared resources at hom100fr001
Share name Type Used as Comment
-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.
Target 192.168.1.105
"HOM100FR001 ping 192.168.1.105"
Pinging 192.168.1.105 with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"HOM100FR001 net view 192.168.1.105"
Shared resources at 192.168.1.105
Share name Type Used as Comment
-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.
Target 127.0.0.1
"HOM100FR001 ping 127.0.0.1"
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"HOM100FR001 net view 127.0.0.1"
Shared resources at 127.0.0.1
Share name Type Used as Comment
-------------------------------------------------------------------------------
tmp Disk
The command completed successfully.
Ping Targets Analysis
www.yahoo.com 66.94.230.32 192.168.1.1
Target
www.yahoo.com
"HOM100FR001 ping
www.yahoo.com"
Pinging
www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:
Reply from 209.131.36.158: bytes=32 time=27ms TTL=54
Reply from 209.131.36.158: bytes=32 time=27ms TTL=53
Reply from 209.131.36.158: bytes=32 time=27ms TTL=53
Reply from 209.131.36.158: bytes=32 time=33ms TTL=53
Ping statistics for 209.131.36.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 33ms, Average = 28ms
Target 66.94.230.32
"HOM100FR001 ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:
Reply from 66.94.230.32: bytes=32 time=26ms TTL=54
Reply from 66.94.230.32: bytes=32 time=27ms TTL=53
Reply from 66.94.230.32: bytes=32 time=44ms TTL=53
Reply from 66.94.230.32: bytes=32 time=27ms TTL=53
Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 44ms, Average = 31ms
Target 192.168.1.1
"HOM100FR001 ping 192.168.1.1"
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Reply from 192.168.1.1: bytes=32 time<1ms TTL=127
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
End diagnosis for HOM100FR001
Is “Find Server ("server")
Checking \\HOM100FR001... Found server on:
\\HOM100FR001
Checking \\HOM200OF001...Unable to open Service Control Manager database on
\\\HOM200OF001:
Checking \\HOM200OF002...Unable to open Service Control Manager database on
\\\HOM200OF002:” a normal result?
Waited an hour and see if hom200of002 My Network Places showed the correct
shares. It doesn’t
Hom200of001 also shows the shares that are not real but at least the
computer is listed as unknown. Maybe this is another effect of Norton
Internet Security that has to be manually removed.