How do you turn off the nvidia firewall?
Does my LanParty 250gb motherboard have this feature. It states firewall somewhere on the product.
How do you turn off the nvidia firewall?
Does my LanParty 250gb motherboard have this feature. It states firewall somewhere on the product.
Yeap. Runs like a baby now. OC'ed to 2.4 Ghz (220x11) , stock voltage and cooling and prime runs 48h no prob.
Wow! I had completely given up on the fact that other people than me might use and, by natural extension, have major problems with the nVidia hardware firewall.
I too was initially drawn to the, in this case, A64/nForce3 250gb platform because of the added bonus of the hardware firewall. I didn't even "jump on the bandwaggon" early on since I got the ASUS K8N-E Deluxe board, which to my knowledge is the only nForce3 (250gb) board with ECC memory support.
Anyway, I received said board and an A64 3200+ in the beginning of august 2004 wanting to do a minor upgrade from my P4 system to tide me over for a year until new tech like DDR2, PCIe and the like is all but unavoidable. Right from the start I noticed quite a few peculiarities of my board. Some were totally to blame on ASUS, and have subsequently been fixed by BIOS updates, although funnily enough "my" issues were never mentioned in the fix list. So be it.
I did however very early on (try to) contact both ASUS and nVidia to get the ball running on fixing those issues. From ASUS I got a barely decipherable answer from one of their tech "support" people in Shanghai. Here's a teaser from that reply:
Dear Friend :
Thank you for contacting ASUS Customer Service.
My name is ailon ,and I would be assisting you today.
#!, if your AGP ,pci not lock , Actually , they will change with system Freq . and their actual freq also depend on power supply .
That was the reply to my question about the reason for the AGP running at 53MHz and the PCI bus running at 30MHz, when in the BIOS those were set to their respective default values of 66MHz and 33MHz. Anyway, I digress...
From nVidia I never got more than an automated response that they had received my mail. After that, deadly silence.
At this point maybe I should list some of the probs that I've had with the nVidia firewall. First off, Bittorrent traffic seems to be impossible. I've been trying heaps of different clients, but it's the same for all of them, after a period of about 10 minutes my connection is totally killed off. Every request simply times out. When I switch off the nVidia firewall however, everything works as it should and I get download speeds up to 200KB/s which is as expected for my 2mbit connection.
Another problem is this. Unless you use the factory-supplied settings for the firewall, those settings are "forgotten" by the firewall unless they have been applied *twice*. Weird, but true.
Also, if you dare to create your own rule set, make sure to define 64 or less rules. Otherwise the firewall again "forgets" these settings upon reboot or cold boot. Applying the settings twice doesn't help in this case. At least not to my knowledge.
The funny thing is that if you create a new rule set based on the "Medium" rule set, the firewall creates something in the region of 60 predefined rules of which all but 18 are superfluous, ie. the same ports get blocked with a new rule name.
You can check if you're firewall actually works by testing it with ShieldsUp and selecting All Service Ports. You will most certainly notice that the only stealthed ports that survive a reboot or cold boot are the ones with a dedicated rule in the rule set; they are the ones shown in green. All other ports are either closed (blue) or worse, open (red). Of course, neither of the last two states is in any way desirable. Your rig should be totally stealthed (green).
Last, but not least, there are some websites that I simply cannot open. I've not (yet?) found the reason for this, but with the firewall set to ON I cannot open sites like e.g. CSNation or the ActiveState website. Strangely enough I can open the TCL subsite of ActiveState. The above holds true *even* if I create a rule set that allows absolutely everything, in essence a totally empty rule set. Switch the nVidia firewall to OFF, and voila, everything works as it should.
I should add, that I've tried every build of the nVidia firewall software I've been able to lay my clammy hands on, which makes it about 10 different builds or so. The, to my knowledge, latest incarnation, namely the 6.39 build for use with nForce4 chipsets is the best so far. I even can get some throughput with Bittorrent, but only for about 1 hour. After that the connection dies again.
So there you are; this is the story of my misery. Apart from the firewall my nForce3 system actually runs pretty great, but I kind of feel cheated since the firewall feature was one of the major points in buying an nVidia platform.
Maybe some of you can shed some light on my problems. Perhaps some or most of them are caused by faulty hardware, ie. design flaws in the nForce3 chipset. I'd hate that of course, but I'd rather know that something is broken beyond repair than living in this state of uncertainty.
Best regards,
mbf
I too was initially drawn to the, in this case, A64/nForce3 250gb platform because of the added bonus of the hardware firewall. I didn't even "jump on the bandwaggon" early on since I got the ASUS K8N-E Deluxe board, which to my knowledge is the only nForce3 (250gb) board with ECC memory support.
Anyway, I received said board and an A64 3200+ in the beginning of august 2004 wanting to do a minor upgrade from my P4 system to tide me over for a year until new tech like DDR2, PCIe and the like is all but unavoidable. Right from the start I noticed quite a few peculiarities of my board. Some were totally to blame on ASUS, and have subsequently been fixed by BIOS updates, although funnily enough "my" issues were never mentioned in the fix list. So be it.
I did however very early on (try to) contact both ASUS and nVidia to get the ball running on fixing those issues. From ASUS I got a barely decipherable answer from one of their tech "support" people in Shanghai. Here's a teaser from that reply:
Dear Friend :
Thank you for contacting ASUS Customer Service.
My name is ailon ,and I would be assisting you today.
#!, if your AGP ,pci not lock , Actually , they will change with system Freq . and their actual freq also depend on power supply .
That was the reply to my question about the reason for the AGP running at 53MHz and the PCI bus running at 30MHz, when in the BIOS those were set to their respective default values of 66MHz and 33MHz. Anyway, I digress...
From nVidia I never got more than an automated response that they had received my mail. After that, deadly silence.
At this point maybe I should list some of the probs that I've had with the nVidia firewall. First off, Bittorrent traffic seems to be impossible. I've been trying heaps of different clients, but it's the same for all of them, after a period of about 10 minutes my connection is totally killed off. Every request simply times out. When I switch off the nVidia firewall however, everything works as it should and I get download speeds up to 200KB/s which is as expected for my 2mbit connection.
Another problem is this. Unless you use the factory-supplied settings for the firewall, those settings are "forgotten" by the firewall unless they have been applied *twice*. Weird, but true.
Also, if you dare to create your own rule set, make sure to define 64 or less rules. Otherwise the firewall again "forgets" these settings upon reboot or cold boot. Applying the settings twice doesn't help in this case. At least not to my knowledge.
The funny thing is that if you create a new rule set based on the "Medium" rule set, the firewall creates something in the region of 60 predefined rules of which all but 18 are superfluous, ie. the same ports get blocked with a new rule name.
You can check if you're firewall actually works by testing it with ShieldsUp and selecting All Service Ports. You will most certainly notice that the only stealthed ports that survive a reboot or cold boot are the ones with a dedicated rule in the rule set; they are the ones shown in green. All other ports are either closed (blue) or worse, open (red). Of course, neither of the last two states is in any way desirable. Your rig should be totally stealthed (green).
Last, but not least, there are some websites that I simply cannot open. I've not (yet?) found the reason for this, but with the firewall set to ON I cannot open sites like e.g. CSNation or the ActiveState website. Strangely enough I can open the TCL subsite of ActiveState. The above holds true *even* if I create a rule set that allows absolutely everything, in essence a totally empty rule set. Switch the nVidia firewall to OFF, and voila, everything works as it should.
I should add, that I've tried every build of the nVidia firewall software I've been able to lay my clammy hands on, which makes it about 10 different builds or so. The, to my knowledge, latest incarnation, namely the 6.39 build for use with nForce4 chipsets is the best so far. I even can get some throughput with Bittorrent, but only for about 1 hour. After that the connection dies again.
So there you are; this is the story of my misery. Apart from the firewall my nForce3 system actually runs pretty great, but I kind of feel cheated since the firewall feature was one of the major points in buying an nVidia platform.
Maybe some of you can shed some light on my problems. Perhaps some or most of them are caused by faulty hardware, ie. design flaws in the nForce3 chipset. I'd hate that of course, but I'd rather know that something is broken beyond repair than living in this state of uncertainty.
Best regards,
mbf
Thanks for the details- I tried to reply to your PM, but its blocked! I heard that the Apache drivers in the FW are causing all kinds of conflicts - even when completely disabled. Anyway, I'll let you know how things turn out with my trails.
Hi again!
Dang, I had somehow managed to block for PMs when I set up this account way back when. Thanks for making me aware of it. Of course, this has now been rectified...
On a more important note, I'm really looking forward to your experiments! I had also originally failed to notice that you've already done tests with ShieldsUp and that you're also aware of the "destealthing" issues. Like I said, this is *not* expected behavior and that nVidia time and again fails to fix this issue is embarrasing to say the least.
By the way, that web shortcut (to ShieldsUp) has a prominent place on my desktop since august 2004. Everytime I switch on the nVidia firewall I immediately run a port scan via ShieldsUp. I simply need to be sure, that the nVidia firewall is in "working condition". When it passes the ShieldsUp test, it actually works until changes are made to the config (including changing profiles).
Anyway, I'm looking forward to hearing from you. Would be great to have some of my findings verified. Also, we simply cannot be the only ones with these problems. I really wonder why there's been no investigation into the workings of the nVidia firewall. Especially since it is/was one of the major selling points for the nForce3/4 chipsets. I did originally contact several hardware web sites, amongst others Anandtech, yet I never got any reply at all. A true shame, since I'm 100% positive that nothing helps getting things done than the focused eye of the media...
Best regards,
mbf
Dang, I had somehow managed to block for PMs when I set up this account way back when. Thanks for making me aware of it. Of course, this has now been rectified...
On a more important note, I'm really looking forward to your experiments! I had also originally failed to notice that you've already done tests with ShieldsUp and that you're also aware of the "destealthing" issues. Like I said, this is *not* expected behavior and that nVidia time and again fails to fix this issue is embarrasing to say the least.
By the way, that web shortcut (to ShieldsUp) has a prominent place on my desktop since august 2004. Everytime I switch on the nVidia firewall I immediately run a port scan via ShieldsUp. I simply need to be sure, that the nVidia firewall is in "working condition". When it passes the ShieldsUp test, it actually works until changes are made to the config (including changing profiles).
Anyway, I'm looking forward to hearing from you. Would be great to have some of my findings verified. Also, we simply cannot be the only ones with these problems. I really wonder why there's been no investigation into the workings of the nVidia firewall. Especially since it is/was one of the major selling points for the nForce3/4 chipsets. I did originally contact several hardware web sites, amongst others Anandtech, yet I never got any reply at all. A true shame, since I'm 100% positive that nothing helps getting things done than the focused eye of the media...
Best regards,
mbf
SOLVED (kind of!):
First of, thank you everyone for your bountious help. I have run my system for a few days to make sure the results are accurate.
I did this:
1a) Unpluged second HD. Imediately no more NTFS errors at boot.
1b) Complete format of main HD.
1c) Installed Windows (MCE 2005, basicaly XP with service pack 2).
2) Then installed Nvidia 6.39 (minus IDE drivers and firewall/Active Armour - just said 'no' during install).
3) Then installed nvidia 66.93 official (sorry FastEddie, still a newb).
4) Then Marvell Yukon driver (enables 2nd internet plug).
5) ZA 5 firewall.
6) Kaspersky AV (I was still getting KLIF errors, so I upgraded my KAV, and install was clean - original problem could have been KAV version).
7) Windows updates from web.
8) Connected second HD. Recognized.
All went well and smooth. I heard ZA 5 has a lot of issues, especialy with bittorrent, but I have't noticed any. I was unsure about sound drivers though - do we install both Nvidia and Realtek? Sound was working after step 3, but it sounded a bit flat though (could have been my imagination), so I installed Realtek a few days later. Now there is a conflict and the Nvidia mixer won't open due to "driver conflict". Also (may be my imagination again) but the disk read/write seems a bit slower than before.
What cha think?
Any more word on the stability of the IDE drivers, NCQ, or nvidia FW/controlers? Can I try to upgrade, or must I reformat again to do that?
First of, thank you everyone for your bountious help. I have run my system for a few days to make sure the results are accurate.
I did this:
1a) Unpluged second HD. Imediately no more NTFS errors at boot.
1b) Complete format of main HD.
1c) Installed Windows (MCE 2005, basicaly XP with service pack 2).
2) Then installed Nvidia 6.39 (minus IDE drivers and firewall/Active Armour - just said 'no' during install).
3) Then installed nvidia 66.93 official (sorry FastEddie, still a newb).
4) Then Marvell Yukon driver (enables 2nd internet plug).
5) ZA 5 firewall.
6) Kaspersky AV (I was still getting KLIF errors, so I upgraded my KAV, and install was clean - original problem could have been KAV version).
7) Windows updates from web.
8) Connected second HD. Recognized.
All went well and smooth. I heard ZA 5 has a lot of issues, especialy with bittorrent, but I have't noticed any. I was unsure about sound drivers though - do we install both Nvidia and Realtek? Sound was working after step 3, but it sounded a bit flat though (could have been my imagination), so I installed Realtek a few days later. Now there is a conflict and the Nvidia mixer won't open due to "driver conflict". Also (may be my imagination again) but the disk read/write seems a bit slower than before.
What cha think?
Any more word on the stability of the IDE drivers, NCQ, or nvidia FW/controlers? Can I try to upgrade, or must I reformat again to do that?
Hi again!
Well, I can't really agree with you having "solved" your problems... Rather, you've circumvented the problems by choosing not to use features on your board (features which I'm sure you counted on being able to use fully and paid the extra premium for.) That's not really the same thing as solving the problems. Good call on not installing the nVidia IDE drivers, though. I wouldn't trust them farther than I could (virtually) throw them.
I have a few additional comments though. First of all, drop Zone Alarm. Yes, it has the snazziest interface, but that's about it. Especially in conjunction with software like BitTorrent clients or eD2000 clients it has proven time and time again of not being up to the task. Especially after quitting aforementioned clients. ZA simply cannot cope with the amount of incoming and unhandled connection requests. This results in massive CPU hogging. Try Sygate Personal Firewall (Pro) or Kerio Firewall instead.
Also, nVidia has just released the nForce 6.53 driver package, which as far as I can determine is their best effort yet. At the very least they've managed to solve a long-standing problem for me, namely those pesky websites I couldn't connect to (I wrote about that in an earlier post). One shouldn't believe it, but they actually managed to solve a bug in their software...
As for P2P "performance" seems to be on the same level as the earlier 6.39 driver package. Still, the software gets better and not worse, which is a consolation, albeit a small one...
Other than that, good luck with your setup. Let me/us know if there are any other problems you encounter.
Best regards,
mbf
Oh, and the ForceWare graphics driver is officially at 71.84 now, although there are beta version of the 75.xx series out there. Just FYI.
Well, I can't really agree with you having "solved" your problems...
Rather, you've circumvented the problems by choosing not to use features on your board (features which I'm sure you counted on being able to use fully and paid the extra premium for.) That's not really the same thing as solving the problems. Good call on not installing the nVidia IDE drivers, though. I wouldn't trust them farther than I could (virtually) throw them.I have a few additional comments though. First of all, drop Zone Alarm. Yes, it has the snazziest interface, but that's about it. Especially in conjunction with software like BitTorrent clients or eD2000 clients it has proven time and time again of not being up to the task. Especially after quitting aforementioned clients. ZA simply cannot cope with the amount of incoming and unhandled connection requests. This results in massive CPU hogging. Try Sygate Personal Firewall (Pro) or Kerio Firewall instead.
Also, nVidia has just released the nForce 6.53 driver package, which as far as I can determine is their best effort yet. At the very least they've managed to solve a long-standing problem for me, namely those pesky websites I couldn't connect to (I wrote about that in an earlier post). One shouldn't believe it, but they actually managed to solve a bug in their software...
As for P2P "performance" seems to be on the same level as the earlier 6.39 driver package. Still, the software gets better and not worse, which is a consolation, albeit a small one...
Other than that, good luck with your setup. Let me/us know if there are any other problems you encounter.
Best regards,
mbf
Oh, and the ForceWare graphics driver is officially at 71.84 now, although there are beta version of the 75.xx series out there. Just FYI.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter