Computer cannot connect to workgroup and cannot ping itself

[Guest]

I have 2 XP Pro machines connected via a Belkin router. They can both access
the web, no problem there.
Machine A is wired desktop, the other one (Machine B) is wireless laptop).
Machine B can see both computers in Network neghborhood, but can only
connect to itself.
Machine A cannot see anything in network neigborhood (get an error message).
Machine A will fail a ping test on itself. Interestingly, it will be able to
connect to Machine B via Net Use command if I use Machine B ip address (not
friendly name).
Machine B, eventhough can see Machine A and B in Net View, won't be able to
connect to Machine A, even using the IP address.

I've been doing everything I read on the web, removed firewall, check for
the browser function (on/off, etc.), made sure Netbios for tcp/ip is on, etc.

Help... anyone ?

 

[Chuck]

I have 2 XP Pro machines connected via a Belkin router. They can both access
the web, no problem there.
Machine A is wired desktop, the other one (Machine B) is wireless laptop).
Machine B can see both computers in Network neghborhood, but can only
connect to itself.
Machine A cannot see anything in network neigborhood (get an error message).
Machine A will fail a ping test on itself. Interestingly, it will be able to
connect to Machine B via Net Use command if I use Machine B ip address (not
friendly name).
Machine B, eventhough can see Machine A and B in Net View, won't be able to
connect to Machine A, even using the IP address.

I've been doing everything I read on the web, removed firewall, check for
the browser function (on/off, etc.), made sure Netbios for tcp/ip is on, etc.

Help... anyone ?

Gerard,

An interesting set of symptoms. One of the most common causes of this problem
would be a misconfigured or overlooked personal firewall, or other security
component. There are several other possibilities too, and any might be the cause
of your problem. Read this article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Let's look at "browstat status" and "ipconfig /all" from each computer, so we
can diagnose the problem. Read this article, and linked articles, and follow
instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

 

[Guest]

Here are the status files:

Browstat A:

Status for domain REDMOND on transport
\Device\NetBT_Tcpip_{2A69E466-C7D3-46C8-BA93-D2BC4F6C29E9}
Browsing is NOT active on domain.
Master browser name is held by: ZYCKI
Master browser is running build 2600

Browstat B

Status for domain REDMOND on transport
\Device\NetBT_Tcpip_{850DF91F-092F-4EEE-A155-D4B80F1C1E56}
Browsing is active on domain.
Master browser name is: LAPTOP
Master browser is running build 2600
1 backup servers retrieved from master LAPTOP
\\LAPTOP
There are 1 servers in domain REDMOND on transport
\Device\NetBT_Tcpip_{850DF91F-092F-4EEE-A155-D4B80F1C1E56}
There are 1 domains in domain REDMOND on transport
\Device\NetBT_Tcpip_{850DF91F-092F-4EEE-A155-D4B80F1C1E56}

IPConfig A

Windows IP Configuration



Host Name . . . . . . . . . . . . : ZYCKI

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Belkin



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller

Physical Address. . . . . . . . . : 00-14-22-3F-19-BB

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.2.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.1

Lease Obtained. . . . . . . . . . : Friday, March 03, 2006 4:38:14 PM

Lease Expires . . . . . . . . . . : Monday, January 18, 2038 7:14:07
PM

IPConfig B

Windows IP Configuration



Host Name . . . . . . . . . . . . : LAPTOP

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Belkin



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : Belkin Wireless Pre-N Notebook
Network Card

Physical Address. . . . . . . . . : 00-11-50-2D-F1-DC

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.2.5

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.1

Lease Obtained. . . . . . . . . . : Friday, March 03, 2006 6:03:16 PM

Lease Expires . . . . . . . . . . : Monday, January 18, 2038 7:14:07
PM



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-08-0D-5A-96-66

 

[Chuck]

Here are the status files:

<SNIP>

Gerard,

Mostly clean diagnosis.
# Physical setup is OK - both computers on the same subnet, DHCP from the same
server.
# Both computers stated to be in same workgroup, Redmond.
# Neither computer seeing server datagrams. Laptop has elected itself master
browser, yet sees only itself ("There are 1 servers...").

Here's one issue:
# Zycki is using an nVidia nForce networking controller. Did you get a User's
Guide with it? Do you know what model nForce it is?
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

Other thoughts:
# When you "made sure Netbios for tcp/ip is on", do you mean "Enabled", or
"Default"?
# What antivirus are you using on each computer?
# Have you checked anonymous access restriction, and hidden, settings?
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

 

[Guest]

There was a hw firewall in the nvidia card and I disabled it, but no luck.
I also check for anonymous access restriction, no issue there.
Netbios on, means enabled (not default).
I use Norton 06, but right now I removed all of this on the desktop (that
seems to be the pb computer).

What puzzles me is that a ping on itself will fail ???

btw, if any help I have installed a test utility called Essential Net Tools
if it can help debug the problem.

 

[Chuck]

There was a hw firewall in the nvidia card and I disabled it, but no luck.
I also check for anonymous access restriction, no issue there.
Netbios on, means enabled (not default).
I use Norton 06, but right now I removed all of this on the desktop (that
seems to be the pb computer).

What puzzles me is that a ping on itself will fail ???

btw, if any help I have installed a test utility called Essential Net Tools
if it can help debug the problem.

Gerard,

Please read my tutorial on solving network problems.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

And please type your replies after mine.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting

Let's enumerate your problems. Take the following code (everything INSIDE the
"#####" lines). Please DO NOT include ANY portion of the "#####" lines. (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=ZYCKI 192.168.2.2
set FullTarget2=LAPTOP 192.168.2.5
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.2.1
Set Version=V1.34
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>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

 

[Guest]

Here you go:

First the Desktop:

CDiagnosis V1.34
Start diagnosis for ZYCKI

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC

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

C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

J$ J:\ Default share

Documents C:\Documents and Settings\All Users\Documents

DellLaserMFP IP_192.168.2.4 Spooled Dell Laser MFP 1600n PCL 6
share c
DellLaserM~1 IP_192.168.2.4 Spooled Dell Laser MFP 1600n share
created
Printer3 Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
The command completed successfully.


Adhoc Browser View


Full Targets ZYCKI 192.168.2.2 LAPTOP 192.168.2.5 127.0.0.1

Target ZYCKI

"ZYCKI ping ZYCKI"



Pinging ZYCKI [192.168.2.2] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.2.2:

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


"ZYCKI net view ZYCKI"

Shared resources at ZYCKI

Computer in the attic

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer3 Print Microsoft Office Document Image Writer

The command completed successfully.


Target 192.168.2.2

"ZYCKI ping 192.168.2.2"



Pinging 192.168.2.2 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.2.2:

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


"ZYCKI net view 192.168.2.2"

Shared resources at 192.168.2.2

Computer in the attic

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer3 Print Microsoft Office Document Image Writer

The command completed successfully.


Target LAPTOP

"ZYCKI ping LAPTOP"

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


"ZYCKI net view LAPTOP"


Target 192.168.2.5

"ZYCKI ping 192.168.2.5"



Pinging 192.168.2.5 with 32 bytes of data:



Reply from 192.168.2.5: bytes=32 time=18ms TTL=128

Reply from 192.168.2.5: bytes=32 time=19ms TTL=128

Reply from 192.168.2.5: bytes=32 time=20ms TTL=128

Reply from 192.168.2.5: bytes=32 time=21ms TTL=128



Ping statistics for 192.168.2.5:

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

Approximate round trip times in milli-seconds:

Minimum = 18ms, Maximum = 21ms, Average = 19ms


"ZYCKI net view 192.168.2.5"

Shared resources at 192.168.2.5

Laptop for Pam

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PS share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~2 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk L:

Printer Print Microsoft Office Document Image Writer

The command completed successfully.


Target 127.0.0.1

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


"ZYCKI net view 127.0.0.1"

Shared resources at 127.0.0.1

Computer in the attic

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer3 Print Microsoft Office Document Image Writer

The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.2.1

Target www.yahoo.com

"ZYCKI ping www.yahoo.com"



Pinging www.yahoo.akadns.net [66.94.230.49] with 32 bytes of data:



Reply from 66.94.230.49: bytes=32 time=76ms TTL=53

Reply from 66.94.230.49: bytes=32 time=78ms TTL=53

Reply from 66.94.230.49: bytes=32 time=80ms TTL=53

Reply from 66.94.230.49: bytes=32 time=81ms TTL=53



Ping statistics for 66.94.230.49:

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

Approximate round trip times in milli-seconds:

Minimum = 76ms, Maximum = 81ms, Average = 78ms


Target 66.94.230.32

"ZYCKI ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=58ms TTL=53

Reply from 66.94.230.32: bytes=32 time=58ms TTL=53

Reply from 66.94.230.32: bytes=32 time=58ms TTL=53

Reply from 66.94.230.32: bytes=32 time=58ms TTL=53



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 58ms, Maximum = 58ms, Average = 58ms


Target 192.168.2.1

"ZYCKI ping 192.168.2.1"



Pinging 192.168.2.1 with 32 bytes of data:



Reply from 192.168.2.1: bytes=32 time=11ms TTL=64

Reply from 192.168.2.1: bytes=32 time=12ms TTL=64

Reply from 192.168.2.1: bytes=32 time=13ms TTL=64

Reply from 192.168.2.1: bytes=32 time=14ms TTL=64



Ping statistics for 192.168.2.1:

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

Approximate round trip times in milli-seconds:

Minimum = 11ms, Maximum = 14ms, Average = 12ms


End diagnosis for ZYCKI

Secong the Laptop:

CDiagnosis V1.34
Start diagnosis for LAPTOP

Enumerate Shares


Share name Resource Remark

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

C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

Documents C:\Documents and Settings\All Users\Documents

DellLaserMFP IP_192.168.2.4 Spooled Dell Laser MFP 1600n PS share
crea
DellLaserM~1 IP_192.168.2.4 Spooled Dell Laser MFP 1600n PCL 6
share c
DellLaserM~2 IP_192.168.2.4 Spooled Dell Laser MFP 1600n share
created
Printer Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
The command completed successfully.


Adhoc Browser View


Full Targets ZYCKI 192.168.2.2 LAPTOP 192.168.2.5 127.0.0.1

Target ZYCKI

"LAPTOP ping ZYCKI"

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


"LAPTOP net view ZYCKI"


Target 192.168.2.2

"LAPTOP ping 192.168.2.2"



Pinging 192.168.2.2 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.2.2:

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


"LAPTOP net view 192.168.2.2"


Target LAPTOP

"LAPTOP ping LAPTOP"



Pinging LAPTOP [192.168.2.5] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.2.5:

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

Approximate round trip times in milli-seconds:

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


"LAPTOP net view LAPTOP"

Shared resources at LAPTOP

Laptop for Pam

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PS share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~2 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer Print Microsoft Office Document Image Writer

The command completed successfully.


Target 192.168.2.5

"LAPTOP ping 192.168.2.5"



Pinging 192.168.2.5 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.2.5:

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

Approximate round trip times in milli-seconds:

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


"LAPTOP net view 192.168.2.5"

Shared resources at 192.168.2.5

Laptop for Pam

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PS share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~2 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer Print Microsoft Office Document Image Writer

The command completed successfully.


Target 127.0.0.1

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


"LAPTOP net view 127.0.0.1"

Shared resources at 127.0.0.1

Laptop for Pam

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PS share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~2 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer Print Microsoft Office Document Image Writer

The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.2.1

Target www.yahoo.com

"LAPTOP ping www.yahoo.com"



Pinging www.yahoo.akadns.net [66.94.230.46] with 32 bytes of data:



Reply from 66.94.230.46: bytes=32 time=62ms TTL=53

Reply from 66.94.230.46: bytes=32 time=59ms TTL=53

Reply from 66.94.230.46: bytes=32 time=59ms TTL=53

Reply from 66.94.230.46: bytes=32 time=60ms TTL=53



Ping statistics for 66.94.230.46:

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

Approximate round trip times in milli-seconds:

Minimum = 59ms, Maximum = 62ms, Average = 60ms


Target 66.94.230.32

"LAPTOP ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=59ms TTL=53

Reply from 66.94.230.32: bytes=32 time=60ms TTL=53

Reply from 66.94.230.32: bytes=32 time=59ms TTL=53

Reply from 66.94.230.32: bytes=32 time=60ms TTL=53



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 59ms, Maximum = 60ms, Average = 59ms


Target 192.168.2.1

"LAPTOP ping 192.168.2.1"



Pinging 192.168.2.1 with 32 bytes of data:



Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64



Ping statistics for 192.168.2.1:

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

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms


End diagnosis for LAPTOP

 

[Guest]

any news on this ?

Here you go:

First the Desktop:

CDiagnosis V1.34
Start diagnosis for ZYCKI

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC

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

C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

J$ J:\ Default share

Documents C:\Documents and Settings\All Users\Documents

DellLaserMFP IP_192.168.2.4 Spooled Dell Laser MFP 1600n PCL 6
share c
DellLaserM~1 IP_192.168.2.4 Spooled Dell Laser MFP 1600n share
created
Printer3 Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
The command completed successfully.


Adhoc Browser View


Full Targets ZYCKI 192.168.2.2 LAPTOP 192.168.2.5 127.0.0.1

Target ZYCKI

"ZYCKI ping ZYCKI"



Pinging ZYCKI [192.168.2.2] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.2.2:

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


"ZYCKI net view ZYCKI"

Shared resources at ZYCKI

Computer in the attic

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer3 Print Microsoft Office Document Image Writer

The command completed successfully.


Target 192.168.2.2

"ZYCKI ping 192.168.2.2"



Pinging 192.168.2.2 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.2.2:

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


"ZYCKI net view 192.168.2.2"

Shared resources at 192.168.2.2

Computer in the attic

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer3 Print Microsoft Office Document Image Writer

The command completed successfully.


Target LAPTOP

"ZYCKI ping LAPTOP"

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


"ZYCKI net view LAPTOP"


Target 192.168.2.5

"ZYCKI ping 192.168.2.5"



Pinging 192.168.2.5 with 32 bytes of data:



Reply from 192.168.2.5: bytes=32 time=18ms TTL=128

Reply from 192.168.2.5: bytes=32 time=19ms TTL=128

Reply from 192.168.2.5: bytes=32 time=20ms TTL=128

Reply from 192.168.2.5: bytes=32 time=21ms TTL=128



Ping statistics for 192.168.2.5:

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

Approximate round trip times in milli-seconds:

Minimum = 18ms, Maximum = 21ms, Average = 19ms


"ZYCKI net view 192.168.2.5"

Shared resources at 192.168.2.5

Laptop for Pam

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PS share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~2 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk L:

Printer Print Microsoft Office Document Image Writer

The command completed successfully.


Target 127.0.0.1

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


"ZYCKI net view 127.0.0.1"

Shared resources at 127.0.0.1

Computer in the attic

Share name Type Used as Comment


-------------------------------------------------------------------------------
DellLaserMFP Print Dell Laser MFP 1600n PCL 6 share created by
Network Magic
DellLaserM~1 Print Dell Laser MFP 1600n share created by Network
Magic
Documents Disk

Printer3 Print Microsoft Office Document Image Writer

The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.2.1

Target www.yahoo.com

"ZYCKI ping www.yahoo.com"



Pinging www.yahoo.akadns.net [66.94.230.49] with 32 bytes of data:



Reply from 66.94.230.49: bytes=32 time=76ms TTL=53

Reply from 66.94.230.49: bytes=32 time=78ms TTL=53

Reply from 66.94.230.49: bytes=32 time=80ms TTL=53

Reply from 66.94.230.49: bytes=32 time=81ms TTL=53



Ping statistics for 66.94.230.49:

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

Approximate round trip times in milli-seconds:

Minimum = 76ms, Maximum = 81ms, Average = 78ms


Target 66.94.230.32

"ZYCKI ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=58ms TTL=53

Reply from 66.94.230.32: bytes=32 time=58ms TTL=53

Reply from 66.94.230.32: bytes=32 time=58ms TTL=53

Reply from 66.94.230.32: bytes=32 time=58ms TTL=53



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 58ms, Maximum = 58ms, Average = 58ms


Target 192.168.2.1

 

[Chuck]

<SNIP>

OK, of the 4 relationships:
# ZYCKI to LAPTOP
# ZYCKI to ZYCKI
# LAPTOP to ZYCKI
# LAPTOP to LAPTOP
only the latter showed no problem. Any relationship involving ZYCKI showed one
or more problems.

So we have to start with ZYCKI. My experience is that multi symptomatic network
problems like this are caused either by misconfigured firewalls, or by LSP /
Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I suspect any combination of:
# Problem with nForce firewall (disabled or not).
# Problem with an overlooked additional firewall (you stated that ZYCKI had
Norton 2006 - when you removed it, did you follow all instructions from
Symantec, carefully?).
# LSP / Winsock corruption.

And please type your replies after mine.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting

 

[Guest]

<SNIP>

OK, of the 4 relationships:
# ZYCKI to LAPTOP
# ZYCKI to ZYCKI
# LAPTOP to ZYCKI
# LAPTOP to LAPTOP
only the latter showed no problem. Any relationship involving ZYCKI showed one
or more problems.

So we have to start with ZYCKI. My experience is that multi symptomatic network
problems like this are caused either by misconfigured firewalls, or by LSP /
Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I suspect any combination of:
# Problem with nForce firewall (disabled or not).
# Problem with an overlooked additional firewall (you stated that ZYCKI had
Norton 2006 - when you removed it, did you follow all instructions from
Symantec, carefully?).
# LSP / Winsock corruption.

And please type your replies after mine.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

 

[Chuck]

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

 

[Guest]

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

Here you go:


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9463F831-6BB4-43BC-9FCF-7894EC600AFD}] SEQPACKET 0
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1004
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9463F831-6BB4-43BC-9FCF-7894EC600AFD}] DATAGRAM 0
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1005
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{AD19A2A3-0E06-4DCE-BB83-17F0238661E1}] SEQPACKET 1
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1006
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{AD19A2A3-0E06-4DCE-BB83-17F0238661E1}] DATAGRAM 1
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1007
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{41E29A6C-719A-4E26-A2E8-DC606AE1DE0B}] SEQPACKET 2
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1008
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{41E29A6C-719A-4E26-A2E8-DC606AE1DE0B}] DATAGRAM 2
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1009
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{EA219350-B25F-4304-B0A7-CA6C15D25C3F}] SEQPACKET 3
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1010
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{EA219350-B25F-4304-B0A7-CA6C15D25C3F}] DATAGRAM 3
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1011
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{C8FB8631-14EB-4BD0-9EBA-74664FE3AF1E}] SEQPACKET 4
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1012
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{C8FB8631-14EB-4BD0-9EBA-74664FE3AF1E}] DATAGRAM 4
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1013
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1014
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1015
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Service Provider
Description: NVIDIA App Filter
Provider ID: {561A1E9F-D78B-40E3-866D-4CE5CF6BB83F}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1016
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 0

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID: {22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID: {3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA) Namespace
Provider ID: {6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: PNRP Cloud Namespace Provider
Provider ID: {03FE89CE-766D-4976-B9C1-BB9BC42C7B4D}
Name Space: 39
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: PNRP Name Namespace Provider
Provider ID: {03FE89CD-766D-4976-B9C1-BB9BC42C7B4D}
Name Space: 38
Active: 1
Version: 0

 

[Chuck]

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

 

[Guest]

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I used the "netsh winsock reset catalog". I run xp pro sp2.
I also sent mail to the nVidia support guys to ask about it. I am also
checking out the admin guide as we speak. Are you suggesting I should
re-enable the nvidia firewall to see what happens ?

 

[Guest]

:

:

:

:

:

I have 2 XP Pro machines connected via a Belkin router. They can both access
the web, no problem there.
Machine A is wired desktop, the other one (Machine B) is wireless laptop).
Machine B can see both computers in Network neghborhood, but can only
connect to itself.
Machine A cannot see anything in network neigborhood (get an error message).
Machine A will fail a ping test on itself. Interestingly, it will be able to
connect to Machine B via Net Use command if I use Machine B ip address (not
friendly name).
Machine B, eventhough can see Machine A and B in Net View, won't be able to
connect to Machine A, even using the IP address.

I've been doing everything I read on the web, removed firewall, check for
the browser function (on/off, etc.), made sure Netbios for tcp/ip is on, etc.

Help... anyone ?

Gerard,

An interesting set of symptoms. One of the most common causes of this problem
would be a misconfigured or overlooked personal firewall, or other security
component. There are several other possibilities too, and any might be the cause
of your problem. Read this article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Let's look at "browstat status" and "ipconfig /all" from each computer, so we
can diagnose the problem. Read this article, and linked articles, and follow
instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Here are the status files:

<SNIP>

Gerard,

Mostly clean diagnosis.
# Physical setup is OK - both computers on the same subnet, DHCP from the same
server.
# Both computers stated to be in same workgroup, Redmond.
# Neither computer seeing server datagrams. Laptop has elected itself master
browser, yet sees only itself ("There are 1 servers...").

Here's one issue:
# Zycki is using an nVidia nForce networking controller. Did you get a User's
Guide with it? Do you know what model nForce it is?
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

Other thoughts:
# When you "made sure Netbios for tcp/ip is on", do you mean "Enabled", or
"Default"?
# What antivirus are you using on each computer?
# Have you checked anonymous access restriction, and hidden, settings?
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

There was a hw firewall in the nvidia card and I disabled it, but no luck.
I also check for anonymous access restriction, no issue there.
Netbios on, means enabled (not default).
I use Norton 06, but right now I removed all of this on the desktop (that
seems to be the pb computer).

What puzzles me is that a ping on itself will fail ???

btw, if any help I have installed a test utility called Essential Net Tools
if it can help debug the problem.

Gerard,

Please read my tutorial on solving network problems.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

And please type your replies after mine.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting

Let's enumerate your problems. Take the following code (everything INSIDE the
"#####" lines). Please DO NOT include ANY portion of the "#####" lines. (Please
verify computer names and ip addresses).

<SNIP>

OK, of the 4 relationships:
# ZYCKI to LAPTOP
# ZYCKI to ZYCKI
# LAPTOP to ZYCKI
# LAPTOP to LAPTOP
only the latter showed no problem. Any relationship involving ZYCKI showed one
or more problems.

So we have to start with ZYCKI. My experience is that multi symptomatic network
problems like this are caused either by misconfigured firewalls, or by LSP /
Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I suspect any combination of:
# Problem with nForce firewall (disabled or not).
# Problem with an overlooked additional firewall (you stated that ZYCKI had
Norton 2006 - when you removed it, did you follow all instructions from
Symantec, carefully?).
# LSP / Winsock corruption.

And please type your replies after mine.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I used the "netsh winsock reset catalog". I run xp pro sp2.
I also sent mail to the nVidia support guys to ask about it. I am also
checking out the admin guide as we speak. Are you suggesting I should
re-enable the nvidia firewall to see what happens ?

One interesting I found in the firewall log when I do a ping, this is what I
get in the log:

277 Warning Firewall Blocked Port 3/8/2006 12:08:40 AM Source: IP
192.168.2.4 UDP Port 1024,
Destination: IP 239.255.255.250 UDP Port 1900.

Does this give any clue ?

 

[Chuck]

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I used the "netsh winsock reset catalog". I run xp pro sp2.
I also sent mail to the nVidia support guys to ask about it. I am also
checking out the admin guide as we speak. Are you suggesting I should
re-enable the nvidia firewall to see what happens ?

One interesting I found in the firewall log when I do a ping, this is what I
get in the log:

277 Warning Firewall Blocked Port 3/8/2006 12:08:40 AM Source: IP
192.168.2.4 UDP Port 1024,
Destination: IP 239.255.255.250 UDP Port 1900.

Does this give any clue ?

Gerard,

The last thing I remember, ZYCKI was 192.168.2.2, and LAPTOP was 192.168.2.5.
What computer were you pinging from?

Did you ever try setting the firewall up to trust Laptop, and if so, by what IP
address?

If you read my article about LSP / Winsock, you'll note that "netsh winsock
reset catalog" is only 1 of 6 possible tools that you need to try.

 

[Guest]

:

:

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
I used the "netsh winsock reset catalog". I run xp pro sp2.
I also sent mail to the nVidia support guys to ask about it. I am also
checking out the admin guide as we speak. Are you suggesting I should
re-enable the nvidia firewall to see what happens ?

One interesting I found in the firewall log when I do a ping, this is what I
get in the log:

277 Warning Firewall Blocked Port 3/8/2006 12:08:40 AM Source: IP
192.168.2.4 UDP Port 1024,
Destination: IP 239.255.255.250 UDP Port 1900.

Does this give any clue ?

Gerard,

The last thing I remember, ZYCKI was 192.168.2.2, and LAPTOP was 192.168.2.5.
What computer were you pinging from?

Did you ever try setting the firewall up to trust Laptop, and if so, by what IP
address?

If you read my article about LSP / Winsock, you'll note that "netsh winsock
reset catalog" is only 1 of 6 possible tools that you need to try.

I did the ping from zycki on itself (ping 192.168.2.2) and this is the error
that showed up in the firewall log.
I will try the other lsp/winsock fixes tonight and let you know how it goes.

 

[Chuck]

:

:

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I used the "netsh winsock reset catalog". I run xp pro sp2.
I also sent mail to the nVidia support guys to ask about it. I am also
checking out the admin guide as we speak. Are you suggesting I should
re-enable the nvidia firewall to see what happens ?

One interesting I found in the firewall log when I do a ping, this is what I
get in the log:

277 Warning Firewall Blocked Port 3/8/2006 12:08:40 AM Source: IP
192.168.2.4 UDP Port 1024,
Destination: IP 239.255.255.250 UDP Port 1900.

Does this give any clue ?

Gerard,

The last thing I remember, ZYCKI was 192.168.2.2, and LAPTOP was 192.168.2.5.
What computer were you pinging from?

Did you ever try setting the firewall up to trust Laptop, and if so, by what IP
address?

If you read my article about LSP / Winsock, you'll note that "netsh winsock
reset catalog" is only 1 of 6 possible tools that you need to try.

I did the ping from zycki on itself (ping 192.168.2.2) and this is the error
that showed up in the firewall log.
I will try the other lsp/winsock fixes tonight and let you know how it goes.

That's very interesting. Look at the CDiag log from ZYCKI (your post 3/5
19:26). ZYCKI resolves itself as 192.168.2.2. But look at the Net Share from
ZYCKI . What is that entry ("Enumerate Shares") "IP_192.168.2.4"?

 

[Guest]

:

:

On Mon, 6 Mar 2006 21:26:26 -0800, Gerard <[email protected]>

<SNIP>

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I used the "netsh winsock reset catalog". I run xp pro sp2.
I also sent mail to the nVidia support guys to ask about it. I am also
checking out the admin guide as we speak. Are you suggesting I should
re-enable the nvidia firewall to see what happens ?

One interesting I found in the firewall log when I do a ping, this is what I
get in the log:

277 Warning Firewall Blocked Port 3/8/2006 12:08:40 AM Source: IP
192.168.2.4 UDP Port 1024,
Destination: IP 239.255.255.250 UDP Port 1900.

Does this give any clue ?

Gerard,

The last thing I remember, ZYCKI was 192.168.2.2, and LAPTOP was 192.168.2.5.
What computer were you pinging from?

Did you ever try setting the firewall up to trust Laptop, and if so, by what IP
address?

If you read my article about LSP / Winsock, you'll note that "netsh winsock
reset catalog" is only 1 of 6 possible tools that you need to try.

I did the ping from zycki on itself (ping 192.168.2.2) and this is the error
that showed up in the firewall log.
I will try the other lsp/winsock fixes tonight and let you know how it goes.

That's very interesting. Look at the CDiag log from ZYCKI (your post 3/5
19:26). ZYCKI resolves itself as 192.168.2.2. But look at the Net Share from
ZYCKI . What is that entry ("Enumerate Shares") "IP_192.168.2.4"?

That's my network printer.
So I tried all the winsock/lsp fixes you mentionned and none of this work.
I still don't have any response from the NVidia guys.
I ordered a new network card yesterday and will give it a shot as soon as I
get it. I am completely at a loss right now. Any more ideas ?

 

[Chuck]

:

:

:

On Mon, 6 Mar 2006 21:26:26 -0800, Gerard <[email protected]>

<SNIP>

ok, I tried everything you suggested:
- reset the winsock
- reinstall the network drivers and services
- I don't have Norton installed anymore (I even used the cleanup utility
from symantec to get rid of this)
- the nvidia firewall is disabled.

Still can't ping itself or cannot connect to the workgroup. I am wondering
if I should just get a new network card and just disable the nvidia card
(which is on the motherboard).

Any more suggestions ? Let me know. thanks.

Gerard

Gerard,

If you've done all of the above, I think we're left with the nForce as the
source of the problem. I really have to recommend though that you look
carefully thru the documentation that came with the computer or the motherboard.
You're not the only person dealing with this right now. The folks at nVidia
HAVE to be supporting it somehow.

Right now, in my hardware purchase budget, an nForce is right at the top of the
list.

Let's look at one more diagnostic. Post the output from "netsh winsock show
catalog" on ZYCKI.

Here you go:

And, Gerard, here is why YOU don't go:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[TCP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[UDP/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 2
Protocol Chain: 1016 : 1002


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: NVIDIA App Filter over [MSAFD Tcpip
[RAW/IP]]
Provider ID: {9C9E6C64-2E05-4A03-8160-B93C7B6A1295}
Provider Path: %SYSTEMROOT%\system32\nvappfilter.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 2
Protocol Chain: 1016 : 1003

I'll bet even money that the nVidia firewall fails open. That is, when you
disabled it, it broke your network.

Are you sure that there's no User Guide entry for Troubleshooting? Maybe a
contact number for nVidia Tech Support? Something in the documentation that
surely must have come with the nForce?

Which Winsock reset procedures did you try?
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

I used the "netsh winsock reset catalog". I run xp pro sp2.
I also sent mail to the nVidia support guys to ask about it. I am also
checking out the admin guide as we speak. Are you suggesting I should
re-enable the nvidia firewall to see what happens ?

One interesting I found in the firewall log when I do a ping, this is what I
get in the log:

277 Warning Firewall Blocked Port 3/8/2006 12:08:40 AM Source: IP
192.168.2.4 UDP Port 1024,
Destination: IP 239.255.255.250 UDP Port 1900.

Does this give any clue ?

Gerard,

The last thing I remember, ZYCKI was 192.168.2.2, and LAPTOP was 192.168.2.5.
What computer were you pinging from?

Did you ever try setting the firewall up to trust Laptop, and if so, by what IP
address?

If you read my article about LSP / Winsock, you'll note that "netsh winsock
reset catalog" is only 1 of 6 possible tools that you need to try.



I did the ping from zycki on itself (ping 192.168.2.2) and this is the error
that showed up in the firewall log.
I will try the other lsp/winsock fixes tonight and let you know how it goes.

That's very interesting. Look at the CDiag log from ZYCKI (your post 3/5
19:26). ZYCKI resolves itself as 192.168.2.2. But look at the Net Share from
ZYCKI . What is that entry ("Enumerate Shares") "IP_192.168.2.4"?

That's my network printer.
So I tried all the winsock/lsp fixes you mentionned and none of this work.
I still don't have any response from the NVidia guys.
I ordered a new network card yesterday and will give it a shot as soon as I
get it. I am completely at a loss right now. Any more ideas ?

Gerard,

If you install a new network card (not nVidia I hope?), and the problem is
resolved, then I'll believe that was the problem. DUHH.

But please run "netsh winsock show catalog" again, and see if the nVidia entries
are still there. If they are, I will reserve my judgment.

I gotta keep wondering what the nVidia software is, though. What I've read
about the nForce is that it's a HARDWARE firewall. So WTH are they doing with
Winsock entries? HARDWARE doesn't need to be inserted into Winsock, I would
think. Do you know what model nForce this is?

Anyway, ask yourself why the printer was sending out pings. Or why ZYCKI
detected the pings as coming from that address. Which computer did you ping
from? Try pinging from the other one, and see what the log looks like.