Hello Mr. Krebs, I'm new (today) to the Lyris form so this information may or may not be beneficial. If by opening ALL ports on the FW resolves the problem, possible use the "netstat" syntax to determine which ports are active, addressing "VIPRE Enterprise Console uses to establish a UDP connection with the server" Note: The NETSTAT command will show you whatever ports are open or in use, but it is NOT a port scanning tool. Open Command Prompt and type: C:'WINDOWS>netstat -an |find /i "listening" TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING TCP 0.0.0.0:1084 0.0.0.0:0 LISTENING TCP 0.0.0.0:2094 0.0.0.0:0 LISTENING TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING You can redirect it to a text file by adding >c:'openports.txt to the command, if you want to: netstat -an |find /i "listening" > c:'openports.txt
netstat -an |find /i "listening" > c:'openports.txt You can also change "listening" to "established" to see what ports your computer actually communicates with: C:'WINDOWS>netstat -an |find /i "established" TCP 192.168.0.100:1084 192.168.0.200:1026 ESTABLISHED TCP 192.168.0.100:2094 192.168.0.200:1166 ESTABLISHED TCP 192.168.0.100:2305 209.211.250.3:80 ESTABLISHED TCP 192.168.0.100:2316 212.179.112.230:80 ESTABLISHED This may help tract down which exact ports need to be configured through the FW. Hope this helps. Ken _____ From: Dennis Krebs [mailto:dennis.kr...@advancedav.com] Sent: Tuesday, April 20, 2010 10:57 AM To: NT System Admin Issues Subject: VIPRE Enterprise Console 4.0.4283 Firewall Issues We installed VIPRE Enterprise Console 4.0.4283 on a local workstation and attempted to create a site connection to a SQL database that resides on our VIPRE server. Initially we were only able to get this to work by disabling the firewall on the server. Using TCPView we determined that the client was trying to establish a remote TCP connection via port 55167. We created a firewall rule on the server to allow this traffic through, turned the firewall back on and, much to our dismay, the client still didn't work. Again, using TCPView, we determined that the client initially tries to establish a UDP connection of some sort. Unfortunately, because TCPView only samples in 1 second increments, we haven't been able to determine the remote port number it's actually using. If we create a rule on the server to allow all UDP traffic the client works as expected. Does anyone know the remote port number VIPRE Enterprise Console uses to establish a UDP connection with the server? I contacted Sunbelt support for this. Unfortunately, their response has been very, VERY disappointing. They basically sent me a couple of tech documents via email (neither of which contained the term UDP) and continue to read from some sort of standard troubleshooting script without actually listening to what I've already done. Any help would be appreciated. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
