Tiny Firewall Pro 6.0: How do I stealth RPC Port 135 ?

"Stuart Gibson" wrote in news: snipped-for-privacy@nnrp-t71-03.news.uk.clara.net:

I suggest you use a different testing site to see if the results change as some sites are better than others.

And a stealthed port means nothing and is overrated. You want to be stealthed, you should put the machines behind a NAT router that cost as much as Tiny Pro.

I had a similar question about port 113, the IDENT port. I couldn't find a way to stealth it. Then I came across a suggestion that I like. Just find a random IP that leads to nothing, and have the firewall redirect incoming traffic to the ports you want stealthed to that IP which isn't connected to anything. No one sending packets will have any idea where they went, so you're effectively stealthed.

"Stuart Gibson" wrote in news: snipped-for-privacy@sabbath.news.uk.clara.net:

US Robotics is a manufacturer you maybe looking for in a router ADSL solution.

Duane :)

I managed to stealth port 135 by fiddling with the RPC settings. Now only port 1025 is open. I guess if I dig into it a bit more, I'll be able to block that too.

I've been thinking of getting a router for a while now, as I am building up a home network. I only have 2 machines connected ATM, but have enough bits lying around to build a couple more.

Can you recommend a good adsl modem/router/firewall/switch combo ?

I don't want to add too many boxes to my already cluttered desk, as I am running out of space!

Stu.

I never thought of that! Sounds like a good scheme to me. If I can't figure out how to block the port, I'll give it a try.

Thanks Jeff.

Which is fine, but port 113 isn't often stealthed for a reason. That being that some mail or news servers can time out waiting for a response from the IDENT port. In my case, "unstealthing" that port had positive results.

Hi, I had the same problem with zone alarm with ICS/NAT in High setting ! I finaly create a rule to block port 135 and 1025. Since I don't know Tiny, can't you create a rule to close them in UDP & TCP ? pascal

The problem with tfp6 is there are a million preset default rules, and there are so many different options, and the help file only refers to version 5, so a lot of the new stuff is not even described, and its just so damn complicated, so its all a bit of a nightmare to set up

I'm thinking of deleting all the existing preset rules and starting fresh.

Stu.

Hummm ..... Not a good idea, Perhaps it's better to wait an answer to create a rule OR send an email to support Tiny. Is it so much complicated to create a rule in Tiny like in ZA ? After 1:00, in ZA, I finish to understand how to create a rule to block those port 135 & 1025. To much complicated. Hope you will have a rapid answer. pascal

And it wasn't so hard after all. I just wish I didn't have to figure everything out for myself. Where's the version 6.0 manual or help file ?? Software like this shouldn't be released without comprehensive instructions, especially for newbies (not that I consider myself one, mind you. I've been using TPF since version 2.0, but since version 4.0 I've kinda just hit and hoped, and that used to work fine on W98, not so on XP!!)

I created a filter under Network Security/Protocols & Ports.

Only thing is, it says 'Filter is Inactive' for every filter in the list, when in fact they MUST be active, otherwise the filter I just created wouldn't work!

I feel a bug report coming on....

Stu.