Firewall Rules Will Not Allow Port Forwarding

Discussion in 'ESET NOD32 Antivirus/Smart Security Beta' started by mbmalone, Jun 20, 2011.

Thread Status:
Not open for further replies.
  1. mbmalone
    Offline

    mbmalone Registered Member

    Firewall Rules Will Not Allow Port Forwarding!

    I have reinstalled already many times, but cannot get the new Beta 5.0.84 to allow my Port Forward to Static IP 192.168.1.2 to function.
    At this point, I'm thinking bug ... Windows 7x86 SP1 :thumbd:

    With ESS v5.0.84 Completely & Properly Removed .... :thumb:

    Success: I can see your service on 72.207.xxx.xxx on port (3389)
    Your ISP is not blocking port 3389 :thumb:
    3389 Remote Desktop
    3389 TCP UDP Microsoft Terminal Server (RDP)

    Success: I can see your service on 72.207.xxx.xxx on port (5800)
    Your ISP is not blocking port 5800 :thumb:
    5800 VNC
    5800 TCP VNC remote desktop protocol—for use over HTTP

    Success: I can see your service on 72.207.xxx.xxx on port (5900)
    Your ISP is not blocking port 5900 :thumb:
    5900 VNC
    5900 TCP UDP Virtual Network Computing (VNC) remote desktop protocol

    With ESS Installed with a "System Rule" Configured .... :thumbd:
    It's the same with an "Application Rule", etc . :thumbd:

    An attempted connection to 72.207.xxx.xxx:3389 timed out. This typically indicates that traffic to that port is being actively blocked by either a firewall or your ISP :thumbd:

    An attempted connection to 72.207.xxx.xxx:5500 timed out. This typically indicates that traffic to that port is being actively blocked by either a firewall or your ISP :thumbd:

    An attempted connection to 72.207.xxx.xxx:5800 timed out. This typically indicates that traffic to that port is being actively blocked by either a firewall or your ISP :thumbd:

    An attempted connection to 72.207.xxx.xxx:5900 timed out. This typically indicates that traffic to that port is being actively blocked by either a firewall or your ISP :thumbd:

    Personal Firewall Log .... :blink:

    ----

    6/20/2011 12:51:42 PM No usable rule found 204.13.248.152:63567 192.168.1.2:5900 TCP C:\Program Files\TightVNC\tvnserver.exe NT AUTHORITY\SYSTEM
    6/20/2011 12:51:39 PM No usable rule found 204.13.248.152:63567 192.168.1.2:5900 TCP C:\Program Files\TightVNC\tvnserver.exe NT AUTHORITY\SYSTEM
    6/20/2011 12:51:29 PM No usable rule found 204.13.248.152:55967 192.168.1.2:5800 TCP C:\Program Files\TightVNC\tvnserver.exe NT AUTHORITY\SYSTEM
    6/20/2011 12:51:26 PM No usable rule found 204.13.248.152:55967 192.168.1.2:5800 TCP C:\Program Files\TightVNC\tvnserver.exe NT AUTHORITY\SYSTEM
    6/20/2011 12:51:04 PM No usable rule found 204.13.248.152:62833 192.168.1.2:3389 TCP System
    6/20/2011 12:51:01 PM No usable rule found 204.13.248.152:62833 192.168.1.2:3389 TCP System

    ----

    http://www.mediafire.com/?ak7ae2m7bp4wqq5

    epfwdata.bin
    EpfwUser.dat
    HipsRules.bin
    HipsRules.xml

    ----

    Attached Files:

    Last edited: Jun 20, 2011
  2. Marcos
    Offline

    Marcos Eset Staff Account

    Re: Firewall Rules Will Not Allow Port Forwarding!

    I presume the problem is that you restricted the rule for specific remote ports 5500, 5800, 5900 (3389 on the first screen) but in fact the remote computer communicates on random ports. Try removing the remote ports from both rules.
Thread Status:
Not open for further replies.