Hi All, Well, I finally connected the D-Link Router (DI-604) I bought a while ago ... and I do mean a while ago. Anyway on to my Question. While running various Firewall Port Scanners I get some "Closed" results instead of "Stealth" result. Which I'm use to when I was running only a Software Firewall. What do I need to do to fix these results? TIA, Steve EDIT - I fixed the PING issue ... and the corrected several results ... but 113 from GRC & SOS and 80 from SOS remain.
Hi dog, If your router's admin control panel does not have a feature to stealth port 113 (which is the case with mine), you can use port forwarding to route requests to port 113 to a non-existent IP behind your router. Stealthed it for me at GRC and others. Nick
Thanks Ron & Nick. Nick could you please explain a little more ... I've only had the router installed for about 2 hrs ... and I'm unsure about all it's in and outs. TIA, Steve PS. I DL'd the firmware update ... but haven't installed it yet.
This applies to Linksys. Your router should have similar software. The port fowarding area will explain how to forward your addresses. http://www.2kevin.net/router.html
Thanks Ron, That did it ... Setup a DMZ for an address that doesn't exist on the network. http://image.grc.com/passed.gif http://image.grc.com/trustealthanalysis.gif http://image.grc.com/passed.gif Steve
Hi dog, A word of caution: don't install the firmware until you read through the threads at ronjor's first link. Look for known issues with the current firmware versions (and work-arounds when something goes wrong). My rule for updating router firmware is if it's not broken, don't rush to update it. Nick
Opps ... To Late ... I already updated from 3.38 to 3.51 ... Everythings OK so far, PAWS crossed Thanks again for your help Guys (Ron & Nick) I appreciate it ... 10 KC Cookies Each. Steve
There are lots of helpful FAQ's for the D-Link 604 at the following address: http://support.dlink.com/faq and in particular, you can find the workaround for Port 113 at http://support.dlink.com/faq/view.asp?prod_id=1068 Hope this helps.
Thanks Cyber Surfer I've already got the issue sorted by using the suggested port forwarding to an unused network address ... I had checked their KB, but didn't happen apon that second link ... it's good to have another option. Thanks Steve