Free Version and Port 135 (RPC)

[Mogul]

Hi,
today i like to Update my Outpost and i became the Message that my Version is no more supportet......
I must downl. Free oder Pro Version.
OK, i downl. the Free Version.....and i was a little suprised, my old configuration File cant load :(
Anyway......
After a probing with "Shields Up" (http://grc.com/default.htm) my Port 135 is open.
In the Freebetaversions a can close it very simple, but in the Free Version i have no chance to close a Port.

Can you make a little Checkbox only for Port 135 (RPC) in the Free-Version ? Only for "open" and "close" ?
Its hard enough to make a new configuration after a New OS-Install, because there no chance to save my configuration......ok, its a free Version.
Please give us a chance to close the Port in the Free Version.
39$ is a little to much for me, and i love Outpost also without the "configuration save chance".

Sorry for my Horrorenglish :D

Greets

[WizzOzz]

Can other using the free version verify that port 135 is open in free?

Youll find info about rpcss here:
http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=2210
It seems to me there is an app listening at the port, is this right?

Could you give us more info?
http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=976

Thx.

[chrisclu]

Hi Mogal,
Is "allow outgoing DNS" checked in your global system settings?
Port 135 has to do epmap or endpoint resolution. ( I just got that from the web:) )
If so, uncheck it and run test again.
Chris

[Mogul]

Hi,
i check it out with "no Dns".....:(
Here is the Result (123kb)....
Portscan.jpg (http://home.arcor.de/netzsammler/screen/portprobe.jpg)
I now that Outpost is in the "Allow most Mode", but this is not the Problem, it was only for "Newsbin" ;). RPC is open, in "Allow most" and "Regel Wizzard"(Blue).
Til yesterday i use the Betaversions withe the updates since Month.....but it was not longer supportet, with this Version i can make a block-rule thru Port 135.....it runs perfectly under WinXP (there i have no update to the Freeversion).

To your Info:
It's a PC in a lokal 3 Workstation-Lan

@WizzOzz,
im Zweifelsfall auch deutsch ;)
Nur um mal evtl. falsche Vermutungen auszuräumen (wegen meinem Englisch). Ich hatte bis gestern die Betaversionen die mal Free waren drauf und das Update ging nicht mehr. Also hab ich unter Win2000 die Free installiert......bin also nicht in dem Beta-Test hier angemeldet und hatte auch keine Pro-Version "freigeschaltet".....ganz legal die alte Beta und immer ugedatet.

Greets

[chrisclu]

WOW. I have never seen this before. You can't be running Win98.

However I searched the forum for port 135 for you and found a lot. go here first. http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=1908&highlight=port+135

root posted the following.

SVCHOST.EXE: This is a process that runs a group of services that are run from dll files.. It runs from the registry key, HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Svchost where details of the services running under each instance of svchost.exe can be found. It is not unusual for more than one instance of this programme to be running in Task manager, this is done to optimise the running of the various services.
This service listens on port 135 and cannot be closed. I have svchost.exe in my blocked applications sections and it always shows stealthed. I am on a stand alone computer with Win2K SP2.
I believe you can block port 135 even though you are networked.
If you have this in your blocked applications section and you do not have any other application allowing use of port 135, and you still fail stealth, then there may be a bug.

[Mogul]

Hi,
hurry, i must go thru Work :( :)
Svchost is a "good" Idea, but with the Free Version from the Betaphase of Outpost i can block the Port, only the port.
The rule is working under WinXP perfectly.
I think its a little easyer to make (if possible) a checkbox that activate the same rule in the Free Version of Outpost.
I come back in the eveneing.....

cu

[Keith]

Originally posted by chrisclu
I am on a stand alone computer with Win2K SP2.

But you sig says you're on W98SE:confused:

[Mikhail]

Is "allow outgoing DNS" checked in your global system settings?
Chris, I do not see how "allow outgoing DNS" could result in 135 port open sorry...
this Version i can make a block-rule thru Port 135
Modul - if you want to create "System rules" you might be intersted in Outpost PRO.
Svchost is a "good" Idea, but with the Free Version from the Betaphase of Outpost i can block the Port, only the port.
Mogul - becuase it is ideologically incorrect. Instead of blocking every port that can be vulnearble and create 65000+ rules it is much easier to only allow the services you really need and to put your computer in "block most (the rest)" mode.

Please understand with a firewall you do not block smth, in oposite you allow only something and blocking the rest.

[muchod]

Originally posted by Mogul
Hi,
hurry, i must go thru Work :( :)
Svchost is a "good" Idea, but with the Free Version from the Betaphase of Outpost i can block the Port, only the port.


What is the difference in blocking a specific port opened by an application between the free and the pro version?
I think all you have to do is create a rule that blocks it for this application (in this case SVCHOST). If you put SVCHOST in your allowed application list then you are allowing the traffic to this port.... :confused: