Firewal doesn't close 135 port

[killabee]

In my port security window I have opened only 80 and 1024-4096, but different port scanners show that I have opened 135 port and, besides, I regulary receive different messages, sent using RPC.

[Pascal]

http://forums.qbik.com/viewtopic.php?t=2706

How does your IP match up when using those tests? Is it the same IP that WinGate sees or an IP address of the intermediate device? (When you are testing it)

[killabee]

Hmm... I'm not sure that fully understood u. Everywhere the only one ip - my external ip.

[killabee]

I mean those sites, which I use to test myself, see my real ip... Not the ip of my cable modem or smth else. If u want - I can give u my ip, and u'll test me by yourself... But, I think, u can get my ip easily ;))

[Pascal]

Yeah, I was wondering if it was hitting an intermediary device (Such as another nat / firewall device on your local network) before hitting the WinGate machine. So that it might be an open port response from that device.

However, Neil mentioned something yesterday which might be of interest. Check the port ranges for "Connections from the Internet" for UDP. Make sure that those ranges are configured properly.

[killabee]

Hmm... Yeap... I had opened UDP ports 1024-4096... Strange. Closed them. Will see, what will change... :)

[killabee]

Or this UDP range is ok and it is not the reason of differnet "enlarge your pennis" and "your computer is under the risk" :))) messages?

[adrien]

These messages normally come in on port 1025 or 1026 UDP, so that port range of 1024-4096 would have let them in.

Adrien

[killabee]

I guess u are right, cause there are no more messages after I closed those udp range. :)