New Router

[spacejamz]

just swapped out a linksys wrt54g router for an airlink108 router...got everything configured on the router and no problems connecting to the internet from the desktops or laptop...

however, when I run the shields up test, it shows that my port 113 is closed. In reading the summary about this, it says that Zone Alarm (which is what I am using) should automatically stealth it, but it does not...

Not sure how to set a rule to forward requests to port 113 to a non-existent port to 'stealth' it...

hope this makes sense...appreciate any suggestions on this...Thanks.

also any feedback on which router would be better to keep would be great (just got the airlink for the 108Mbps connectivity....)

 

[n0cmonkey]

That whole "stealth" thing is a silly label. It doesn't really mean anything useful.

You can try forwarding it to an IP address that isn't used on your network. Something like 192.168.134.2.

Zone alarm won't affect the router, if you're using it on your desktop behind the router.

 

[spacejamz]

thanks for the quick feedback...

I have never tried to forward anything before...any chance you might provide some guidance on how to do this?

I assume it would be done on the firewall rules page (if this isn't correct, let me know)...

if it is, what values would I need to enter on this screen?

Firewall Rules Page on my Router

Thanks again!!!

 

[n0cmonkey]

I can't find an airlink 108 manual, so I won't be much help.

 

[spacejamz]

Originally posted by: n0cmonkey
I can't find an airlink 108 manual, so I won't be much help.

here is the link for the manual...

 

[n0cmonkey]

Section 4.5.6 looks like the part you want to take a look at.
Public port: 113
LAN server: some ip you aren't going to use

Really though, this doesn't add anything.

 

[spacejamz]

Thanks again for the help...I have it 'stealthed' now...

out of curiousity, isn't it a good thing if a port scanner tries to scan the ports on your pc and your pc doesn't respond (versus just having the port closed)?

I am basing this off using shields up at ww.grc.com...

 

[n0cmonkey]

Originally posted by: spacejamz

Thanks again for the help...I have it 'stealthed' now...

out of curiousity, isn't it a good thing if a port scanner tries to scan the ports on your pc and your pc doesn't respond (versus just having the port closed)?

I am basing this off using shields up at ww.grc.com...

My opinion on the stealth thing:
If I try to scan your system and all of the ports are closed, I move on. If I scan your system, get no error, and get no response I move on. If I scan a system that isn't connected at the moment, I get an error and move on.

It's an extra step that doesn't really do anything. No response is as good as a "closed port" response when it comes to finding out if there is actually a machine there.