G
Guest
So bad news, I installed a brand new network card (netgear GA311), disabledChuck said:That's my network printer.Chuck said::
:
:
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"?
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.
the nVidia and still, my problem hasn't gone away...
On the positive side, the nVidia doesn't show up anymore in the "netsh
winsock show catalog"...
Computer still cannot ping itself (got a new ip address for the new card
btw), etc...