port 1046 is open

[john_84]

i am currently running kerio firewall and when i scan the computer with grc i found that the port
1046 is not stealth but closed anybody knows
how to close this port

[RedLobster]

John, well lets see whats on that port.
Please open FIREWALL STATUS an see if there two listing LOCALHOST: one connect OUT and one connected IN.........one may show 44334.......what does the other say???

If your rules are correct ALL ports should show stealt........I'll wait a few moments for your reply.....past my bedtime LOL

[RedLobster]

John I didn't see you as being login so you have already left the forum.....when you return there will be lots of great people here to help you......looks like you need to tweak your rules.

[RedLobster]

John, please don't think me rude for not returning....as you may notice I am not a member here..an was just lurking around to see whats happening with spywareblaster.

[john_84]

actually kerio firewall is trying to act as a server
when the kerio firewall starts it open these four ports 44501,44334,1790 and 1796

[RedLobster]

WOW John, you posted and took off....no one had a chance to even reply.
Well good luck..hope you find a solution...

[tahoma]

miranda im keeps that port open here

[melissa]

are u using avast antivirus if yes then turned it off and then do port scan agian

[RedLobster]

A very common mistake to think that all four ports are needed.......only two ports are actually needed..one connected out and one connected in



MEL

are you showing avast as having a port open..if so consider tweaking your rules...

[RedLobster]

quick comment.....if firewall rules are applied correctly ALL ports will be stealth no mater which scan is used.........an no program should need to be disabled..EVER!!

[CrazyM]

Hi john_84

-{ Quote: " quoting: john_84 link=board=23;threadid=26509;start=0#msg153566 date=1080805431]
actually kerio firewall is trying to act as a server
when the kerio firewall starts it open these four ports 44501,44334,1790 and 1796" }-

Kerio will establish connections on localhost (127.0.0.1) to communicate with itself. So those are normal.

If you don't already have one, at the end of your rule set you could add a block rule for all inbound and enable logging.

Regards,

CrazyM