Firewall is blocking Monitor updates

[nhouck]

It seems the remote monitors are not able to report stats back to the master server when a firewall is enabled because they connect to the master server on random ports not the 8888 port.

 

2008-02-21 00:00:16 DROP TCP 74.63.64.62 64.27.11.18 8888 1773 40 A 3624548413 2714231045 65463 - - - RECEIVE

 

8888 here is the source port on the remote machine, and 1773 is the destination port on the master server. The destination port appears to be random on each new connection.

 

I would expect both the source port on the remote machine and the destination port on the master server to be 8888.

 

Has anyone else figured out a way to fix this?

 

Thanks,

 

Noel

[Johnny5_Hull]

This has been bothering me for a while.

 

I have just taken to conecting to the server via RDP, and using the monitors from there when I need to.

 

If someone has a solution, I would be interested to hear it.

 

Cheers

[LFA]

On Windows Firewall on XP and 2003 if open TCP port 8888 or add MonitorConsole.exe and MonitorService.exe it should work correctly. Windows firewall does not block outbound connections so you don't need to do anything else for master-remote connections.

 

On other firewalls you might have to open TCP port 8888 for inbound and outbound.

 

It is like when you use Internet Explorer. You are connecting to port 80 on a server but if you check with netstat the local port is random. For example after connecting to tcadmin.com I see this:

TCP 192.168.1.60:2865 208.101.49.151:80 ESTABLISHED 2076

TCP 192.168.1.60:2867 208.101.49.151:80 ESTABLISHED 2076

[Jdubz31]

On Windows Firewall on XP and 2003 if open TCP port 8888 or add MonitorConsole.exe and MonitorService.exe it should work correctly. Windows firewall does not block outbound connections so you don't need to do anything else for master-remote connections.

 

On other firewalls you might have to open TCP port 8888 for inbound and outbound.

 

Windows Firewall does not by default, but with the install images used by some companies, it may. You'll want to add the executables to the white list to be on the safe-side.

[nhouck]

If you notice this is blocking a RECEIVE, not outbound request.

 

I'm not really sure what's going on here, because I would expect the ports to be backwards. That is source port on the remote machine should be random, and destination port on the master should be 8888. In this case it is the opposite.

 

I'm pretty sure I have the Monitor executables on the white list but I'll double check.