Re: Home network problem (router and 2 laptops)

On Tue, 19 Jul 2005 06:45:19 -0700, Andy P <AndyP@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

>"Chuck" wrote:
>
>> On Mon, 18 Jul 2005 18:29:02 -0700, Andy P <Andy P@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> wrote:
>>
>> >And here is the IPCONFIG/all output from the other laptop (appended after the
>> >previous one).
>> >
>> >And I also tried disabling the Windows firewall with no success.
>> >
>> >"Andy P" wrote:
>> >
>> >> I wasted 2 weekends ... please help.
>> >>
>> >> I have a router (wireless, but I use the LAN connections) and 2 laptops with
>> >> XP Home. I had them connected and did not realize at what point my home
>> >> network stopped working as I changed some settings to secure it in April
>> >> (could be the Novell network software that I installed and later removed).
>> >> Currently, I have the same workgroup, filesharing on, the corresponding user
>> >> names and passwords on each with administrator rights. I can ping each by IP
>> >> but not by computer name. I can also see both computers in My Network Places.
>> >> I spent countless hours checking to have the TCP/IP, file and printer
>> >> sharing, and client for microsoft networks. I keep getting a "You may not
>> >> have permission to access this resource. File path not found" message when I
>> >> try to access the other laptop.
>> >>
>> >> What else can I try?
>> >>
>> >> THANK you so much.
>>
>> Andy,
>>
>> Working with Windows Networking is sometimes a frustrating task. What you're
>> seeing here, according to your report, is an "error = 53". There are several
>> known causes of this error, and I apologise if I enumerate several that you have
>> already considered, and dismissed.
>> # Corrupted LSP / Winsock.
>> # Firewall problem.
>> # Registry settings.
>> # Invalid node type.
>> # Excessive protocols.
>>
>> Now, when you refer to "countless hours checking to have the TCP/IP, file and
>> printer sharing, and client for microsoft networks", I'm going to hope that you
>> mean you thoroughly checked everything discussed in this article:
>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
>>
>> And I hope that the Guest account (for XP Home, that's all you need) is properly
>> activated on both computers.
>> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>
>>
>> Because I promise you, if there's something that isn't right, that's described
>> in one of the above articles, you'll have trouble some time. So I'll offer you
>> both articles from the beginning, for your education:
>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
>> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>
>>
>> Next, please read this article (from which came the above list), and follow any
>> links that seem relevant. Keep an open mind; some links may contain information
>> that you haven't considered.
>> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>>
>> If that's of no help, let's take the "ipconfig /all" output, and analyse your
>> problem. Take the following code (everything inside the "#####"). (Please
>> verify computer names and ip addresses).
>>
>> 1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
>> then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
>> into Notepad. Verify, and correct, names and addresses if necessary.
>> 2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
>> folder "C:\".
>> 3. Run it by Start - Run - "c:\cdiag".
>> 4. Wait patiently.
>> 5. 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, with all computers powered up and online.
>>
>> ##### Start CDiag Assembled Code
>>
>> @echo off
>> set FullTarget1=TOSHIBA 192.168.0.102
>> set FullTarget2=DELL 192.168.0.103
>> set FullTarget3=
>> set FullTarget4=
>> set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
>> set FullTargets=%FullTargets% 127.0.0.1
>> set PingTargets=www.yahoo.com 66.94.230.32 192.168.0.1
>> Set Version=V1.32
>> @echo CDiagnosis %Version% >c:\cdiag.txt
>> @echo Start diagnosis for %computername% >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> @echo Adhoc Browser View >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> net view >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> @echo Full Targets %FullTargets% >>c:\cdiag.txt
>> for %%a in (%FullTargets%) do (
>> @echo. >>c:\cdiag.txt
>> @echo Target %%a >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> @echo "%computername% ping %%a" >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> ping %%a >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> @echo "%computername% net view %%a" >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> net view %%a >>c:\cdiag.txt
>> )
>> @echo. >>c:\cdiag.txt
>> @echo Ping Targets %PingTargets% >>c:\cdiag.txt
>> for %%a in (%PingTargets%) do (
>> @echo. >>c:\cdiag.txt
>> @echo Target %%a >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> @echo "%computername% ping %%a" >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> ping %%a >>c:\cdiag.txt
>> )
>> @echo. >>c:\cdiag.txt
>> @echo End diagnosis for %computername% >>c:\cdiag.txt
>> notepad c:\cdiag.txt
>> :EOF
>>
>> ##### End CDiag Assembled Code

>Hi Helob & Chuck,
>
>Thank you for the detailed and numerous suggestions. I will start working
>through them tonight. I had found other postings from Chuck, so I have tried
>3 of the common suggestions, including the registry (and I don't have 3-party
>firewalls, though the router has a firewall tab - don't know whether I should
>open ports just in case?). One thing I noticed is that I have Netbios over
>TCP/IP as the Default among the three options.
>
>I will report back - I hope this posting will not disappear by tonight.
>
>Thanks again,
>Andy

Andy,

Setting NetBIOS Over TCP/IP to Default can be a problem is some LANs. This
requires the DHCP server to define its setting; an actual server on the LAN will
set this properly, but if your router is providing DHCP, it's best to set NBT to
ON.

The firewall tab in the router only controls protection against traffic from the
WAN (Internet). Please don't make any changes there, that will not help, and it
may decrease your protection.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.

Relevant Pages