Re: networking issue
- From: Chuck <none@xxxxxxxxxxx>
- Date: 3 Jul 2005 16:44:05 -0500
On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
>"Chuck" wrote:
>
>> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> wrote:
>>
>> >Hi again, and thanks for the help. Was up all night working thought I'd
>> >postthis before crashing in the hopes that you may hev time to look it over
>> >by the time I get up:
>>
>> <SNIP>
>>
>> Jon,
>>
>> Let's see where we are.
>> # Node Types Hybrid and Unknown, no problem there.
>> # No gratuitous protocols.
>>
>> I can't find any references to either a "123" or "2351" error in Microsoft
>> documentation. I did a Google search, though, and got several hits. This set
>> of errors has come up in the past, in problems resolved in this group. They've
>> unfortunately been trial-and-error resolutions based upon my other 2 listed
>> possible causes for the "error = 53", namely:
>> # Corrupted LSP / Winsock.
>> # Firewall problem.
>>
>> I looked at the search hits. One guy reported having an "internet filter
>> service" running, and his problem was resolved by removing that. Two others had
>> gratuitous protocols, one IPV6, and the other NetBEUI.
>>
>> Why no "browstat status" for Laptop?
>>
>> What's different in your situation is that you have a symmetrical problem, ie
>> each computer showing these symptoms. In a way, this is good. You can work on
>> just ONE computer at a time, check "browstat status" on EACH computer after each
>> change, and look for a difference in results (possibly showing from either
>> computer).
>> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>>
>> What personal firewalls and antivirus products do you have?
>> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>>
>> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
>> ONE of your computers, and check for results using "browstat status" run on EACH
>> computer.
>> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> # LSP-Fix.
>> # WinsockFix
>> # WinsockXPFix
>> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
>> # Reset TCP/IP.
>>
>> Once you get results from updating ONE computer, try the same fix on a second
>> computer, and observe the results.
>help.
>tried all of these fixes and still nothing.
>hired someone local to come over and fix this and she said it was the router
>which i believe is incorrect.
>ready to take lives.
>willing to pay for competent help.
>could it be the router?
Jon,
Well, almost anything COULD be the router, but the symmetrical nature of the
problem makes it unlikely, at least it doesn't look like failed router ports.
All 3 computers appear to be getting DHCP{ settings from the router, so I can't
see positive evidence of obvious hardware failure there.
You could find out, if you want to try another router, but let's see if we can
pinpoint the problem a bit more.
We've tried the most obvious possibilities. Go through the troubleshooting
checklist if you wish.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
Next, 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=gateway 192.168.1.100
set FullTarget2=LAPTOP 192.168.1.101
set FullTarget3=Basement 192.168.1.103
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.1.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
--
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 sonic net.
.
- Follow-Ups:
- Re: networking issue
- From: Jon M
- Re: networking issue
- References:
- Re: networking issue
- From: Jon M
- Re: networking issue
- From: Chuck
- Re: networking issue
- From: Jon M
- Re: networking issue
- From: Chuck
- Re: networking issue
- From: Jon M
- Re: networking issue
- Prev by Date: Re: Can't browse network on 1 computer
- Next by Date: Re: DHCP Breaks XP Network Printing
- Previous by thread: Re: networking issue
- Next by thread: Re: networking issue
- Index(es):
Relevant Pages
|
