Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA
From: Chuck (none_at_example.net)
Date: 11/22/04
- Next message: Linda Callard: "Re: File & Printer Sharing Problem"
- Previous message: ccc: "Help me with routing rule with 2 interfaces"
- In reply to: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Next in thread: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Reply: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Reply: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Messages sorted by: [ date ] [ thread ]
Date: 21 Nov 2004 20:11:06 -0600
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\DK>netstat
>
>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.
- Next message: Linda Callard: "Re: File & Printer Sharing Problem"
- Previous message: ccc: "Help me with routing rule with 2 interfaces"
- In reply to: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Next in thread: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Reply: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Reply: dimdur_at_ureach.com: "Re: Home Network: Comp A can access CompB, but CompB doesnt see CompA"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
