2

I am trying to disallow my Chrome browser to access a specific port on a remote machine. To be more clear: I want e.g. Opera to be able to access the TCP port 1850 but i want to block Chrome on TCP port 1850.

With Firefox i could choose the path wich resulted in:

%ProgramFiles% (x86)\Mozilla Firefox 4.0 Beta 1\plugin-container.exe

I chose the port to block and it worked.

When I chose chrome (which process manager tells me runs in my AppData directory the path is

%USERPROFILE%\AppData\Local\Google\Chrome\Application\chrome.exe

and set the (same) port it does not block the connection.

Any ideas why?

OS: Windows 7 Home Premium (German)

Improve this question
1
  • The actual problem was to use the variable %USERPROFILE% in the path, if this is replaced by the real path the rule works. This is also stated in the Windows help documentation, but who is looking there for help :)
    – floplus
    Mar 15, 2011 at 7:05

2 Answers 2

Reset to default
0

What do you want to block?

Using the Windows Firewall and creating an outbound rule to disable, let's say, port 443 on remote machines, I can no longer connect to any https connection on remote servers. Maybe you chose the wrong protocol.

Improve this answer
7
  • The port i am blocking ist 1850 and it works with the firefox rule AND it works if i choose to block any application not only chrome...
    – floplus
    Mar 14, 2011 at 14:32
  • So to understand what you want: Your server works on TCP protocol with port number 1850. You want Chrome to not work on that port. I don't know what Service you are connecting to, but comparing it to your Firefox line, you might use a specific non-flash plugin. I would recommend looking for the plugin you use in about:memory and look for the pid. Use the pid to look up the exact system call in the task manager (or process explorer from sysinternals), the calls might be hidden by a chrome.exe wrapper and not work properly. It's also possible that the process you want to block isnt chrome at all
    – private_meta
    Mar 14, 2011 at 14:37
  • This MUST be a rule for chrome then, because the firefox rule works.(?)
    – floplus
    Mar 14, 2011 at 14:39
  • OK i found something in the help (!) unfortunately in german but in short it says you should not use variables like %USERPROFILE%
    – floplus
    Mar 14, 2011 at 14:42
  • Yes, but still figure out what I wrote you. Chrome handles plugins differently than Firefox, as Firefox uses the plugin container, but I'm not quite sure how Chrome handles it.
    – private_meta
    Mar 14, 2011 at 14:43
-1

I understand your question to be why is Chrome listed as being installed in your %USERPROFILE%\AppData\Local directory.

This is how Google designed their application. To have Chrome install to your Program Files folder as a more typical (and less virus looking) application you must install Chrome via the Google Pack download (which allows one install process to install one or more Google software titles) or use the Google Chrome MSI installer.

Improve this answer
1
  • I am fine with the install location as long as this is not the reason for the firewall to NOT block the chosen port.
    – floplus
    Mar 14, 2011 at 14:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .