Home Network: Comp A can access CompB, but CompB doesnt see CompA

Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee causing
a problem..

If you'd like to work this through one-on-one, send me an email and I'll
walk you through the steps.




"MovingtoLinux!" wrote in message
...
Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router
is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same
steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it
with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see
Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread
with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee
causing
a problem..

In article ,
"MovingtoLinux!" wrote:
Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee causing
a problem..

1. If the computers run the original or SP1 versions of Windows XP,
disable XP's built-in Internet Connection Firewall on local area
network connections -- it's for use only on a direct modem connection
to the Internet. If they run SP2, enable the exception for file and
printer sharing in the Windows Firewall. Disable and un-install all
other firewall programs while troubleshooting. When un-installing a
firewall program, use the un-install procedure provided by the
manufacturer . Don't use Control Panel | Add or Remove Programs,
which might not completely un-install it.

For more information, see:

Windows XP Internet Connection Firewall
http://www.practicallynetworked.com/...c_firewall.htm

2. Use only the TCP/IP protocol for File and Printer Sharing. If the
network needs more than one protocol, unbind File and Printer Sharing
from all but one of them. Details he

Windows XP Network Protocols
http://www.practicallynetworked.com/..._protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details he

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/...hoot/netbt.htm

4. Run "ipconfig /all" on XP and look at the "Node Type" at the
beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network, for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parame ters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default...b;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default...b;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Hi
I had a similar problem on the LAN @ work here. Under the properties of your
network connection under the advanced tap, take off the internet connection
firewall.



"MovingtoLinux!" wrote:

Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee causing
a problem..

"MovingtoLinux!" wrote:

Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee causing
a problem..

I've tried the options listed (disabling firewall etc...) and they did not
seem to work. Also, I've had this network with 3 computers going with WinXP
SP2 with firewall active and McAfee Firewall/AntiVirus active and the
networks work fine. I can access comp B from comp A even with firewalls
active.. the setups are the same but comp B cannot access comp A...

Now my Netgear FR114P doesn't seem to be working! It comes on and the test
light won't ever go off! **sigh**, so I guess now I've got to get THAT fixed
before I can continue trying to figure this problem out. Thanks for the
replies and if anyone has experience with the above mentioned Netgear router,
PLEASE help me!! I'd greatly appreciate it!

On Thu, 18 Nov 2004 13:55:06 -0800, "MovingtoLinux!"
wrote:



"MovingtoLinux!" wrote:

Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee causing
a problem..

I've tried the options listed (disabling firewall etc...) and they did not
seem to work. Also, I've had this network with 3 computers going with WinXP
SP2 with firewall active and McAfee Firewall/AntiVirus active and the
networks work fine. I can access comp B from comp A even with firewalls
active.. the setups are the same but comp B cannot access comp A...

Now my Netgear FR114P doesn't seem to be working! It comes on and the test
light won't ever go off! **sigh**, so I guess now I've got to get THAT fixed
before I can continue trying to figure this problem out. Thanks for the
replies and if anyone has experience with the above mentioned Netgear router,
PLEASE help me!! I'd greatly appreciate it!

If you want help for Netgear products, the BBR Netgear Forum is absolutely the
best place to go.
http://www.dslreports.com/forum/netgear

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

This seems to be a wide-spread problem - I have been reading the threads (as
I am currently experiencing EXACTLY the same issue) - and advice seems to be
a Cut&Paste - and they do not work!

I went through all the hoops that are advised here - Computer Browser
Service is up and running; NetBIOS over TCP/IP enabled; guest account active;
comps can ping each other's IPs and hostnames; they are in the same
workgroup; Windows Firewall is disabled; same user ID and pass established on
both units; and still I can see shares on Comp И from Comp A (copy files into
them and run files from them) and Comp be can not connect to COMP A - even
though I can see it in View Workgroup Computers. When I try to connect to it
I get an error message: "Workgroup is not accessible. You might not have
permission to use this network resource. Contact the administrator of this
server to find out if you have access permissions". NET USE does not work
either.

Someone mentioned in one of the threads that they started experiencing this
after SP2 install - and once they removed SP2 - problem went away. Now, may
be it IS SP2 issue that M$ needs to take a look into? I have not been able to
find anything in KB in this regards.

Any further input is greatly appreciated.

-- DK

"MovingtoLinux!" wrote:

Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee causing
a problem..

If you want to work through this step by step, you're welcome to send me an
email.



"Dmitri" wrote in message
...
This seems to be a wide-spread problem - I have been reading the threads
(as
I am currently experiencing EXACTLY the same issue) - and advice seems to
be
a Cut&Paste - and they do not work!

I went through all the hoops that are advised here - Computer Browser
Service is up and running; NetBIOS over TCP/IP enabled; guest account
active;
comps can ping each other's IPs and hostnames; they are in the same
workgroup; Windows Firewall is disabled; same user ID and pass established
on
both units; and still I can see shares on Comp ? from Comp A (copy files
into
them and run files from them) and Comp be can not connect to COMP A - even
though I can see it in View Workgroup Computers. When I try to connect to
it
I get an error message: "Workgroup is not accessible. You might not have
permission to use this network resource. Contact the administrator of this
server to find out if you have access permissions". NET USE does not work
either.

Someone mentioned in one of the threads that they started experiencing
this
after SP2 install - and once they removed SP2 - problem went away. Now,
may
be it IS SP2 issue that M$ needs to take a look into? I have not been able
to
find anything in KB in this regards.

Any further input is greatly appreciated.

-- DK

"MovingtoLinux!" wrote:

Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router
is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of
the
systems and now I can't get them to network again. I followed the same
steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it
with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see
Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread
with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee
causing
a problem..

Addition:

I threw my wok laptop into the picture - it CAN access shares on Comp
B and Comp B can see and connect to it it - it is only direction from
Comp B to Comp A that has problem connecting.

There is got to be some setting that I am missing on Comp A. Which is
a bummer - since this is my main unit and all peripherals are
connected to it. Need to be able to share them.

On Sat, 20 Nov 2004 20:23:44 -0800, Dmitri
wrote:

This seems to be a wide-spread problem - I have been reading the threads (as
I am currently experiencing EXACTLY the same issue) - and advice seems to be
a Cut&Paste - and they do not work!

I went through all the hoops that are advised here - Computer Browser
Service is up and running; NetBIOS over TCP/IP enabled; guest account active;
comps can ping each other's IPs and hostnames; they are in the same
workgroup; Windows Firewall is disabled; same user ID and pass established on
both units; and still I can see shares on Comp ? from Comp A (copy files into
them and run files from them) and Comp be can not connect to COMP A - even
though I can see it in View Workgroup Computers. When I try to connect to it
I get an error message: "Workgroup is not accessible. You might not have
permission to use this network resource. Contact the administrator of this
server to find out if you have access permissions". NET USE does not work
either.

Someone mentioned in one of the threads that they started experiencing this
after SP2 install - and once they removed SP2 - problem went away. Now, may
be it IS SP2 issue that M$ needs to take a look into? I have not been able to
find anything in KB in this regards.

Any further input is greatly appreciated.

-- DK

"MovingtoLinux!" wrote:

Hello,

I've got two systems, both running WinXP SP2 and connected to a NETGEAR
4-Port Cable/DSL ProSafe Firewall/Print Server, Model FR114P. The router is
working fine and both comps can access the internet.

I had both these comps networked before, but I had to reinstall one of the
systems and now I can't get them to network again. I followed the same steps
as before which have always worked. I've made sure both are in the same
workgroup and Comp A will recognize Comp B immediately and can access it with
no problem, but Comp B will not see Comp A no matter what I try. In the
past, I only had to wait a few minutes and Comp B would eventually see Comp A
all of a sudden.

CompB will sometimes see the CompA, but I cannot access it and none of
CompA's shared drives are seen.

Any help with this would be greatly appreciated. I saw another thread with
the same problem, but it was due to Norton AV which I don't have on my
system. I do have McAfee though, but as I said, I had the computers
networked before with the same setup and so I dont' think it's McAfee causing
a problem..

ICQ 6124479
dimdur at ureach dot com

On Sun, 21 Nov 2004 20:23:33 GMT, *email_address_deleted* wrote:

Addition:

I threw my wok laptop into the picture - it CAN access shares on Comp
B and Comp B can see and connect to it it - it is only direction from
Comp B to Comp A that has problem connecting.

There is got to be some setting that I am missing on Comp A. Which is
a bummer - since this is my main unit and all peripherals are
connected to it. Need to be able to share them.

Dmitri,

Please provide ipconfig information for each computer, so we can run
comprehensive diagnoses to tell us where your problems are.
Start - Run - "cmd". Type "ipconfig /all c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

COMP A:
---------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-50-8D-E1-22-9B
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 167.206.3.232
167.206.3.231
167.206.3.166
Lease Obtained. . . . . . . . . . : Sunday, November 21, 2004
8:33:52 AM

Lease Expires . . . . . . . . . . : Monday, November 22, 2004
8:33:52 AM




COMP B::
-----------------------------------------------------------------------------------------------------------------------------------
Windows IP Configuration

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


Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-40-F4-33-6B-A8
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 . . . . . . . . . . . : 167.206.3.232
167.206.3.231
167.206.3.166

Lease Obtained. . . . . . . . . . : Sunday, November 21, 2004 5:08:42
PM
Lease Expires . . . . . . . . . . : Monday, November 22, 2004 5:08:42
PM

Once again - from A to B I have no problems - ping works both on IP
and hostname; I can see shares and operate with files in them.

From B to A - i can ping A by IP and hostname, but now I keep getting
message "Workgroup is not accessible. You might not have permission to
use this network resource. Contact the administrator of this server to
find out if you have access permissions."

On Both:

WinXP Pro with SP2
Simple File Sharing is enabled
Computer Browsing service is enabled
Same user ID and passwords are established.
Windows Firewall is disabled on Local Area connections

NETSTAT on B shows:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKnetstat

Active Connections

Proto Local Address Foreign Address State
TCP piii800mhz:netbios-ssn 192.168.1.100:3166 ESTABLISHED

NET VIEW from B returns an error:

"System error 121 occurred - the semaphore timeout period ahs expired"

\\piv24ghz from B shows error message "Server PIV24GHZ is not
accessible"

I has ZoneAlarm installed on Comp A - have removed it completely and
tried troubleshooting without it - made NO difference - I do not
believe that ZA is interfering in any way.

Thanks.


On 21 Nov 2004 15:12:09 -0600, Chuck wrote:

On Sun, 21 Nov 2004 20:23:33 GMT, *email_address_deleted* wrote:

Addition:

I threw my wok laptop into the picture - it CAN access shares on Comp
B and Comp B can see and connect to it it - it is only direction from
Comp B to Comp A that has problem connecting.

There is got to be some setting that I am missing on Comp A. Which is
a bummer - since this is my main unit and all peripherals are
connected to it. Need to be able to share them.

Dmitri,

Please provide ipconfig information for each computer, so we can run
comprehensive diagnoses to tell us where your problems are.
Start - Run - "cmd". Type "ipconfig /all c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.

ICQ 6124479
dimdur at ureach dot com

On Sun, 21 Nov 2004 22:56:37 GMT, *email_address_deleted* wrote:


SNIP

Once again - from A to B I have no problems - ping works both on IP
and hostname; I can see shares and operate with files in them.

From B to A - i can ping A by IP and hostname, but now I keep getting
message "Workgroup is not accessible. You might not have permission to
use this network resource. Contact the administrator of this server to
find out if you have access permissions."

On Both:

WinXP Pro with SP2
Simple File Sharing is enabled
Computer Browsing service is enabled
Same user ID and passwords are established.
Windows Firewall is disabled on Local Area connections

NETSTAT on B shows:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKnetstat

Active Connections

Proto Local Address Foreign Address State
TCP piii800mhz:netbios-ssn 192.168.1.100:3166 ESTABLISHED

NET VIEW from B returns an error:

"System error 121 occurred - the semaphore timeout period ahs expired"

\\piv24ghz from B shows error message "Server PIV24GHZ is not
accessible"

I has ZoneAlarm installed on Comp A - have removed it completely and
tried troubleshooting without it - made NO difference - I do not
believe that ZA is interfering in any way.

Thanks.

Dmitri,

The IPConfig logs look good.

Let's check the browser situation first.

Make sure the browser service is running on one computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started. Disable the
browser service on the other computer.

Then power both computers off. Power one on, and then the other. Use browstat
to identify the master browser.

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip
http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, as "browstat status". Make sure all computers give the same result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx

If the problem isn't the master browser, run some standard diagnostics for me.
Take the following code (everything inside the "#####"). (Did I get the names
and ip addresses right)?

Copy the code, precisely as it is keyed, into Notepad. Ensure that Format -
Word Wrap is not checked.
Save the file as "cdiag.cmd", as type "All Files", into the root folder "C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
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.

#####

@echo off
set FullTargets=pIV24ghz 192.168.1.100 piii800mhz 192.168.1.102
set PingTargets=127.0.0.1 192.168.1.1
Set Version=V1.05
@echo CDiagnosis %Version% c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) c:\cdiag.txt
for %%a in (%FullTargets% %PingTargets%) do (
@echo. c:\cdiag.txt
@echo Target %%a c:\cdiag.txt
@echo. c:\cdiag.txt
@echo "ping %%a" c:\cdiag.txt
@echo. c:\cdiag.txt
ping %%a c:\cdiag.txt
@echo. c:\cdiag.txt
@echo "net view %%a" c:\cdiag.txt
@echo. c:\cdiag.txt
net view %%a c:\cdiag.txt
)
@echo End diagnosis for %computername% c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

#####

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

I disabled Computer Browsing Service on Comp B (as per your advice)

Here are my Browstat results:

Comp A:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKbrowstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52A8-0FE7-461D-83C5-916105A611F7}
Browsing is active on domain.
Master browser name is: PIV24GHZ
Master browser is running build 2600
1 backup servers retrieved from master PIV24GHZ
\\PIV24GHZ
Unable to retrieve server list from PIV24GHZ: 121

Comp B:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


C:\browstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B3-0236FD4ECCE4}
Browsing is active on domain.
Master browser name is: PIV24GHZ
Could not connect to registry, error = 53 Unable to determine
build of browser master: 53


-----------------------------------------------------------------------------------------------------------------------
This is CDIAG for Comp A:

CDiagnosis V1.05
Start diagnosis for PIV24GHZ (Targets pIV24ghz 192.168.1.100
piii800mhz 192.168.1.102)

Target pIV24ghz

"ping pIV24ghz"



Pinging pIV24ghz [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms 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


"net view pIV24ghz"

Shared resources at pIV24ghz

Main Unit

Share name Type Used as Comment

-------------------------------------------------------------------------------
Canon Print Canon i470D
D Disk
EPSON860 Print EPSON Stylus COLOR 860
H Disk
Printer Print Print to this device to send a photo
quality fax.
Printer10 Print BroadGun pdfMachine
Printer11 Print Creates Adobe PDF
Printer2 Print Print to this device to send a fax.
Printer3 Print SnagIt 7
Printer4 Print Okidata OL-600e
Printer5 Print Microsoft Office Document Image Writer
Printer6 Print Fax via eFax
Printer7 Print Epson Stylus COLOR 860 ESC/P 2
SharedDocs Disk
Storage (I) Disk
The command completed successfully.


Target 192.168.1.100

"ping 192.168.1.100"



Pinging 192.168.1.100 with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms 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


"net view 192.168.1.100"


Target piii800mhz

"ping piii800mhz"



Pinging piii800mhz [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms 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


"net view piii800mhz"

Shared resources at piii800mhz

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk (UNC)
SharedDocs Disk
The command completed successfully.


Target 192.168.1.102

"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),


"net view 192.168.1.102"


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms 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


"net view 127.0.0.1"

Shared resources at 127.0.0.1

Main Unit

Share name Type Used as Comment

-------------------------------------------------------------------------------
Canon Print Canon i470D
D Disk
EPSON860 Print EPSON Stylus COLOR 860
H Disk
Printer Print Print to this device to send a photo
quality fax.
Printer10 Print BroadGun pdfMachine
Printer11 Print Creates Adobe PDF
Printer2 Print Print to this device to send a fax.
Printer3 Print SnagIt 7
Printer4 Print Okidata OL-600e
Printer5 Print Microsoft Office Document Image Writer
Printer6 Print Fax via eFax
Printer7 Print Epson Stylus COLOR 860 ESC/P 2
SharedDocs Disk
Storage (I) Disk
The command completed successfully.


Target 192.168.1.1

"ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150



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


"net view 192.168.1.1"

End diagnosis for PIV24GHZ
--------------------------------------------------------------------------------------------------

CDIAG results for Comp B:

CDiagnosis V1.05
Start diagnosis for PIII800MHZ (Targets pIV24ghz 192.168.1.100
piii800mhz 192.168.1.102)

Target pIV24ghz

"ping pIV24ghz"



Pinging pIV24ghz [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms 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


"net view pIV24ghz"


Target 192.168.1.100

"ping 192.168.1.100"



Pinging 192.168.1.100 with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms 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


"net view 192.168.1.100"


Target piii800mhz

"ping piii800mhz"



Pinging piii800mhz [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms 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


"net view piii800mhz"

Shared resources at piii800mhz

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.1.102

"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),


"net view 192.168.1.102"


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms 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


"net view 127.0.0.1"

Shared resources at 127.0.0.1

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.1.1

"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=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150



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 = 1ms, Average = 0ms


"net view 192.168.1.1"

End diagnosis for PIII800MHZ




Now they can't ping each other.......


On 21 Nov 2004 20:11:06 -0600, Chuck wrote:

On Sun, 21 Nov 2004 22:56:37 GMT, *email_address_deleted* wrote:


SNIP

Once again - from A to B I have no problems - ping works both on IP
and hostname; I can see shares and operate with files in them.

From B to A - i can ping A by IP and hostname, but now I keep getting
message "Workgroup is not accessible. You might not have permission to
use this network resource. Contact the administrator of this server to
find out if you have access permissions."

On Both:

WinXP Pro with SP2
Simple File Sharing is enabled
Computer Browsing service is enabled
Same user ID and passwords are established.
Windows Firewall is disabled on Local Area connections

NETSTAT on B shows:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKnetstat

Active Connections

Proto Local Address Foreign Address State
TCP piii800mhz:netbios-ssn 192.168.1.100:3166 ESTABLISHED

NET VIEW from B returns an error:

"System error 121 occurred - the semaphore timeout period ahs expired"

\\piv24ghz from B shows error message "Server PIV24GHZ is not
accessible"

I has ZoneAlarm installed on Comp A - have removed it completely and
tried troubleshooting without it - made NO difference - I do not
believe that ZA is interfering in any way.

Thanks.

Dmitri,

The IPConfig logs look good.

Let's check the browser situation first.

Make sure the browser service is running on one computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started. Disable the
browser service on the other computer.

Then power both computers off. Power one on, and then the other. Use browstat
to identify the master browser.

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip
http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, as "browstat status". Make sure all computers give the same result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx

If the problem isn't the master browser, run some standard diagnostics for me.
Take the following code (everything inside the "#####"). (Did I get the names
and ip addresses right)?

Copy the code, precisely as it is keyed, into Notepad. Ensure that Format -
Word Wrap is not checked.
Save the file as "cdiag.cmd", as type "All Files", into the root folder "C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
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.

#####

@echo off
set FullTargets=pIV24ghz 192.168.1.100 piii800mhz 192.168.1.102
set PingTargets=127.0.0.1 192.168.1.1
Set Version=V1.05
@echo CDiagnosis %Version% c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) c:\cdiag.txt
for %%a in (%FullTargets% %PingTargets%) do (
@echo. c:\cdiag.txt
@echo Target %%a c:\cdiag.txt
@echo. c:\cdiag.txt
@echo "ping %%a" c:\cdiag.txt
@echo. c:\cdiag.txt
ping %%a c:\cdiag.txt
@echo. c:\cdiag.txt
@echo "net view %%a" c:\cdiag.txt
@echo. c:\cdiag.txt
net view %%a c:\cdiag.txt
)
@echo End diagnosis for %computername% c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

#####

ICQ 6124479
dimdur at ureach dot com

Chuck, I "flipped" Computer Browser Service - disabled it on A and
enabled it on B:

Here are results:

comp A browstat:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKcd..

C:\Documents and Settingsbrowstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52A8-0FE7-461D-83C
5-916105A611F7}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Could not open key in registry, error = 5 Unable to determine
build of br
owser master: 5
\\\\PIII800MHZ . Version:05.01 Flags: 51003 NT POTENTIAL
MASTER
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}

C:\Documents and Settings

Comp B browstat:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\browstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B
3-0236FD4ECCE4}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Master browser is running build 2600
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}

Still I can not connect to A shares from B computer


On 21 Nov 2004 20:11:06 -0600, Chuck wrote:

On Sun, 21 Nov 2004 22:56:37 GMT, *email_address_deleted* wrote:


SNIP

Once again - from A to B I have no problems - ping works both on IP
and hostname; I can see shares and operate with files in them.

From B to A - i can ping A by IP and hostname, but now I keep getting
message "Workgroup is not accessible. You might not have permission to
use this network resource. Contact the administrator of this server to
find out if you have access permissions."

On Both:

WinXP Pro with SP2
Simple File Sharing is enabled
Computer Browsing service is enabled
Same user ID and passwords are established.
Windows Firewall is disabled on Local Area connections

NETSTAT on B shows:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKnetstat

Active Connections

Proto Local Address Foreign Address State
TCP piii800mhz:netbios-ssn 192.168.1.100:3166 ESTABLISHED

NET VIEW from B returns an error:

"System error 121 occurred - the semaphore timeout period ahs expired"

\\piv24ghz from B shows error message "Server PIV24GHZ is not
accessible"

I has ZoneAlarm installed on Comp A - have removed it completely and
tried troubleshooting without it - made NO difference - I do not
believe that ZA is interfering in any way.

Thanks.

Dmitri,

The IPConfig logs look good.

Let's check the browser situation first.

Make sure the browser service is running on one computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started. Disable the
browser service on the other computer.

Then power both computers off. Power one on, and then the other. Use browstat
to identify the master browser.

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip
http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, as "browstat status". Make sure all computers give the same result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx

If the problem isn't the master browser, run some standard diagnostics for me.
Take the following code (everything inside the "#####"). (Did I get the names
and ip addresses right)?

Copy the code, precisely as it is keyed, into Notepad. Ensure that Format -
Word Wrap is not checked.
Save the file as "cdiag.cmd", as type "All Files", into the root folder "C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
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.

#####

@echo off
set FullTargets=pIV24ghz 192.168.1.100 piii800mhz 192.168.1.102
set PingTargets=127.0.0.1 192.168.1.1
Set Version=V1.05
@echo CDiagnosis %Version% c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) c:\cdiag.txt
for %%a in (%FullTargets% %PingTargets%) do (
@echo. c:\cdiag.txt
@echo Target %%a c:\cdiag.txt
@echo. c:\cdiag.txt
@echo "ping %%a" c:\cdiag.txt
@echo. c:\cdiag.txt
ping %%a c:\cdiag.txt
@echo. c:\cdiag.txt
@echo "net view %%a" c:\cdiag.txt
@echo. c:\cdiag.txt
net view %%a c:\cdiag.txt
)
@echo End diagnosis for %computername% c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

#####

ICQ 6124479
dimdur at ureach dot com

-----------------------------------------
ÔÚ £¬Ð´µÀ£º
where can i find the FAQ? thanks.

-----------------------------------------

Ö Àñ£¡
tanker