Cannot access local network - pings successfully + can access by I

G

Guest

Hi

I am unable to access certain PCs on my P2P network - worked fine until v.
recently. I can see some of them but not others. I have uninstalled ZoneAlarm
and turned off Windows Firewall. All PCs running Windows XP SP2 - variations
of Pro, Home and Tablet. All updates available applied.

I can see the workgroup (Happyatom) on both but on one PC I cannot see any
PCs and when clicking on the workgroup icon I get the message "Happyatom is
not accessible. You might not have permission to use this network resource
...." On the other I can see the PCs in the workgroup but get a similar
message when clicking on their icons.

If I type the IP address of either PC on the other, then I can access the
shared drives. (I log into all PCs with the same username and password). All
PCs can access the internet through a hub and router.

The browser service is enabled on all PCs and I have enabled NetBIOS over
TCP/IP. The problem PCs are all in the same workgroup. Having researched as
much as I can I am still no nearer sorting out the problem. I would be very
grateful for any help.

Below are the results of running diagnostics on each of the problem PCs.

Many thanks in anticipation for any assistance.

Paul

Diagnostic Data for computers OFFICE64 and HATAB
Data for each computer in following sections:

IPCONFIG /ALL
BROWSTAT STATUS
Registry settings
Output from PCHUCK CDIAG v1.4 utility


####### COMPUTER: OFFICE64 ######

********* Windows IP Configuration

Host Name . . . . . . . . . . . . : office64
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010
PCI
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-11-D8-AB-D2-5D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.234
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.2
DHCP Server . . . . . . . . . . . : 192.168.0.2
DNS Servers . . . . . . . . . . . : 192.168.0.2
Lease Obtained. . . . . . . . . . : 23 August 2006 17:27:34
Lease Expires . . . . . . . . . . : 24 August 2006 17:27:34


********* BROWSTAT STATUS

Status for domain HAPPYATOM on transport
\Device\NetBT_Tcpip_{0BA93B0E-DCC5-4B0C
-8922-26ABCB6489D3}
Browsing is active on domain.
Master browser name is: OFFICE64
Master browser is running build 2600
1 backup servers retrieved from master OFFICE64
\\OFFICE64
There are 2 servers in domain HAPPYATOM on transport
\Device\NetBT_Tcpip_{0B
A93B0E-DCC5-4B0C-8922-26ABCB6489D3}
There are 2 domains in domain HAPPYATOM on transport
\Device\NetBT_Tcpip_{0B
A93B0E-DCC5-4B0C-8922-26ABCB6489D3}

********* Registry Settings
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"IsDomainMaster"="1"
"MaintainServerList"="Auto"

Enabled NetBIOS over TCP (have tried on Auto too)


********* CDiagnosis V1.40
Start diagnosis for OFFICE64
Full Targets office64 192.168.0.234 HATAB 192.168.0.230 127.0.0.1
Ping Targets www.yahoo.com 192.168.0.2

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share

E$ E:\ Default share

IPC$ Remote IPC

D$ D:\ Default share

print$ F:\WINDOWS\system32\spool\drivers
Printer Drivers

ADMIN$ F:\WINDOWS Remote Admin

F$ F:\ Default share

SharedDocs F:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

XP64Backups C:\
XP64Data D:\
COLOR_LASER USB001 Spooled EPSON AL-C900 Advanced

DELL33A66E NtwkPort00 Spooled DELL5100cn

DELL33A66EPS NtwkPort00 Spooled DELL5100cn-PS

EPSONEPL LPT1: Spooled EPSON EPL-5800 Advanced

Printer FPP2: Spooled pdfFactory

Printer2 PDF-XChange Spooled PDF-XChange 3.0

Printer3 Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
Printer4 FPR5: Spooled FinePrint

The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\HATAB Happy Atom Tablet

\\OFFICE64 ha64

The command completed successfully.


Full Targets Analysis office64 192.168.0.234 HATAB 192.168.0.230 127.0.0.1

Target office64

"OFFICE64 ping office64"



Pinging office64 [192.168.0.234] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.234:

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

Approximate round trip times in milli-seconds:

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


"OFFICE64 net view office64"

Shared resources at office64

ha64

Share name Type Used as Comment

-------------------------------------------------------------------------------
COLOR_LASER Print EPSON AL-C900 Advanced
DELL33A66E Print DELL5100cn
DELL33A66EPS Print DELL5100cn-PS
EPSONEPL Print EPSON EPL-5800 Advanced
Printer Print pdfFactory
Printer2 Print PDF-XChange 3.0
Printer3 Print Microsoft Office Document Image Writer
Printer4 Print FinePrint
SharedDocs Disk
XP64Backups Disk
XP64Data Disk
The command completed successfully.


Target 192.168.0.234

"OFFICE64 ping 192.168.0.234"



Pinging 192.168.0.234 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.234:

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

Approximate round trip times in milli-seconds:

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


"OFFICE64 net view 192.168.0.234"

Shared resources at 192.168.0.234

ha64

Share name Type Used as Comment

-------------------------------------------------------------------------------
COLOR_LASER Print EPSON AL-C900 Advanced
DELL33A66E Print DELL5100cn
DELL33A66EPS Print DELL5100cn-PS
EPSONEPL Print EPSON EPL-5800 Advanced
Printer Print pdfFactory
Printer2 Print PDF-XChange 3.0
Printer3 Print Microsoft Office Document Image Writer
Printer4 Print FinePrint
SharedDocs Disk
XP64Backups Disk
XP64Data Disk
The command completed successfully.


Target HATAB

"OFFICE64 ping HATAB"

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


"OFFICE64 net view HATAB"


Target 192.168.0.230

"OFFICE64 ping 192.168.0.230"



Pinging 192.168.0.230 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.230:

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

Approximate round trip times in milli-seconds:

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


"OFFICE64 net view 192.168.0.230"


Target 127.0.0.1

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


"OFFICE64 net view 127.0.0.1"

Shared resources at 127.0.0.1

ha64

Share name Type Used as Comment

-------------------------------------------------------------------------------
COLOR_LASER Print EPSON AL-C900 Advanced
DELL33A66E Print DELL5100cn
DELL33A66EPS Print DELL5100cn-PS
EPSONEPL Print EPSON EPL-5800 Advanced
Printer Print pdfFactory
Printer2 Print PDF-XChange 3.0
Printer3 Print Microsoft Office Document Image Writer
Printer4 Print FinePrint
SharedDocs Disk
XP64Backups Disk
XP64Data Disk
The command completed successfully.


Ping Targets Analysis www.yahoo.com 192.168.0.2

Target www.yahoo.com

"OFFICE64 ping www.yahoo.com"



Pinging www.yahoo-ht2.akadns.net [209.73.186.238] with 32 bytes of data:



Reply from 209.73.186.238: bytes=32 time=105ms TTL=48

Reply from 209.73.186.238: bytes=32 time=104ms TTL=49

Reply from 209.73.186.238: bytes=32 time=106ms TTL=48

Reply from 209.73.186.238: bytes=32 time=104ms TTL=49



Ping statistics for 209.73.186.238:

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

Approximate round trip times in milli-seconds:

Minimum = 104ms, Maximum = 106ms, Average = 104ms


Target 192.168.0.2

"OFFICE64 ping 192.168.0.2"



Pinging 192.168.0.2 with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time<1ms TTL=64

Reply from 192.168.0.2: bytes=32 time<1ms TTL=64

Reply from 192.168.0.2: bytes=32 time<1ms TTL=64

Reply from 192.168.0.2: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.0.2:

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 OFFICE64


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
========== END FOR OFFICE64
====================================================
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX



####### HATAB ######

********* IPCONFIG /ALL

Windows IP Configuration

Host Name . . . . . . . . . . . . : HATAB
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family
Gigabit
Ethernet NIC
Physical Address. . . . . . . . . : 00-0A-E4-E2-95-58
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.230
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.2
DHCP Server . . . . . . . . . . . : 192.168.0.2
DNS Servers . . . . . . . . . . . : 192.168.0.2
Lease Obtained. . . . . . . . . . : 23 August 2006 11:30:42
Lease Expires . . . . . . . . . . : 24 August 2006 11:30:42

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network
Connection
Physical Address. . . . . . . . . : 00-12-F0-D1-22-27



********* BROWSTAT STATUS

Status for domain HAPPYATOM on transport
\Device\NetBT_Tcpip_{176A3871-45A2-48C6
-944C-B564EA6C2192}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


********* Registry Settings
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"IsDomainMaster"="0"
"MaintainServerList"="AUTO"

Enabled NetBIOS over TCP (have tried on Auto too)



********* CDiagnosis V1.40
Start diagnosis for HATAB
Full Targets OFFICE64 192.168.0.234 HATAB 192.168.0.230 127.0.0.1
Ping Targets www.yahoo.com 192.168.0.2

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share

IPC$ Remote IPC

D$ D:\ Default share

F$ F:\ Default share

print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

ADMIN$ C:\WINDOWS Remote Admin

SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

TAB1 D:\
TABC C:\
TABDATA2 F:\
DELL33A66E NtwkPort00 Spooled DELL5100cn

Printer FPP2: Spooled pdfFactory

Printer2 Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
Printer3 Journal Note Writer Po Spooled Journal Note Writer

Printer4 FPR5: Spooled FinePrint

The command completed successfully.


Adhoc Browser View


Full Targets Analysis OFFICE64 192.168.0.234 HATAB 192.168.0.230 127.0.0.1

Target OFFICE64

"HATAB ping OFFICE64"

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


"HATAB net view OFFICE64"


Target 192.168.0.234

"HATAB ping 192.168.0.234"



Pinging 192.168.0.234 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.234:

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

Approximate round trip times in milli-seconds:

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


"HATAB net view 192.168.0.234"

Shared resources at 192.168.0.234

ha64

Share name Type Used as Comment

-------------------------------------------------------------------------------
COLOR_LASER Print EPSON AL-C900 Advanced
DELL33A66E Print DELL5100cn
DELL33A66EPS Print DELL5100cn-PS
EPSONEPL Print EPSON EPL-5800 Advanced
Printer Print pdfFactory
Printer2 Print PDF-XChange 3.0
Printer3 Print Microsoft Office Document Image Writer
Printer4 Print FinePrint
SharedDocs Disk
XP64Backups Disk
XP64Data Disk
The command completed successfully.


Target HATAB

"HATAB ping HATAB"



Pinging HATAB [192.168.0.230] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.230:

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

Approximate round trip times in milli-seconds:

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


"HATAB net view HATAB"

Shared resources at HATAB

Happy Atom Tablet

Share name Type Used as Comment

-------------------------------------------------------------------------------
DELL33A66E Print DELL5100cn
Printer Print pdfFactory
Printer2 Print Microsoft Office Document Image Writer
Printer3 Print Journal Note Writer
Printer4 Print FinePrint
SharedDocs Disk
TAB1 Disk
TABC Disk
TABDATA2 Disk
The command completed successfully.


Target 192.168.0.230

"HATAB ping 192.168.0.230"



Pinging 192.168.0.230 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.230:

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

Approximate round trip times in milli-seconds:

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


"HATAB net view 192.168.0.230"

Shared resources at 192.168.0.230

Happy Atom Tablet

Share name Type Used as Comment

-------------------------------------------------------------------------------
DELL33A66E Print DELL5100cn
Printer Print pdfFactory
Printer2 Print Microsoft Office Document Image Writer
Printer3 Print Journal Note Writer
Printer4 Print FinePrint
SharedDocs Disk
TAB1 Disk
TABC Disk
TABDATA2 Disk
The command completed successfully.


Target 127.0.0.1

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


"HATAB net view 127.0.0.1"

Shared resources at 127.0.0.1

Happy Atom Tablet

Share name Type Used as Comment

-------------------------------------------------------------------------------
DELL33A66E Print DELL5100cn
Printer Print pdfFactory
Printer2 Print Microsoft Office Document Image Writer
Printer3 Print Journal Note Writer
Printer4 Print FinePrint
SharedDocs Disk
TAB1 Disk
TABC Disk
TABDATA2 Disk
The command completed successfully.


Ping Targets Analysis www.yahoo.com 192.168.0.2

Target www.yahoo.com

"HATAB ping www.yahoo.com"



Pinging www.yahoo-ht2.akadns.net [209.73.186.238] with 32 bytes of data:



Request timed out.

Reply from 209.73.186.238: bytes=32 time=105ms TTL=49

Reply from 209.73.186.238: bytes=32 time=103ms TTL=49

Reply from 209.73.186.238: bytes=32 time=108ms TTL=48



Ping statistics for 209.73.186.238:

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

Approximate round trip times in milli-seconds:

Minimum = 103ms, Maximum = 108ms, Average = 105ms


Target 192.168.0.2

"HATAB ping 192.168.0.2"



Pinging 192.168.0.2 with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time<1ms TTL=64

Reply from 192.168.0.2: bytes=32 time<1ms TTL=64

Reply from 192.168.0.2: bytes=32 time<1ms TTL=64

Reply from 192.168.0.2: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.0.2:

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 HATAB
 
G

Guest

This looks like a knock on effect from ZoneAlarm. Your computers are unable
to find the master browser for the workgroup and thus unable to reference
what computers are and are not in the workgroup.

Try changing the work group name for all the computers to something new.
Also I know there is a samba command to query the master browser so there
must be a windows alternative. Have a look at that for your answer. Someone
here will know in more detail.
 
G

Guest

Thanks for your reply. Unfortunately I have been down the ZA route -
unistalled and then deleted all files following guidelines on ZoneAlarm
website. Also I would have thought that ZA would have prevented me seeing the
disks on the other PC when I type in the IP address - but using the IP
address I have full access to the other PC.

As regards master browser - using BROWSTAT, one PC returns itself as the
master browser, the other is unable to determine the master browser - using
GetAdapterStatus switch.
 
G

Guest

It has to be something that zone alarm leaves in as with it being unable to
find the UNC as you say it shows that your computers are not correcting
electing a master-browser.
Apparently it can take up to 15min for a computer to appear in a workgroup
but from what you have said I suspect you have tried waiting that long.

With a network that small you could manually set the ip's and enter them
along with the hostnames in the host file and eliminate the discovery delay.
 
G

Guest

I have to admit that ZA is top of the list of culprits - but I have removed
every trace of it as far as I know, following Zonelabs instructions.

My network is slightly bigger - there are 9 PCs on it. I would prefer not to
have static IPs as work colleagues sometimes bring their laptops and it is
easier not to have to keep worrying about settings and just have the router
DHCP allocate them.

I suspect I will probably return to a backup from a couple of weeks ago when
everything worked OK as I have already 'wasted' several days on this.

Many thanks for your help devstuff!
 

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

Top