This content has been marked as final. Show 5 replies
Just reading the release notes and it reads like alph or beta release, its got a huge amount of issues.
Definetely waiting till patch 1, shame as we have a few 64 bit machines with no protection ATM.
Guess I'll be the guinea pig till patch 1. Anyone else running this yet? Any big problems?
The only problem I've run into is a really complex issue with vmware bridged mode. Basically the firewall isn't acting statefully so I have to manually open up inbound ports to get around the issue (it's at tier III right now and I expect it to be resolved soon). Other than that problem, no issues at all.
What ports do you have to open?
We have an issue with XP vm's running on ESX servers. Sometimes RDP sessions do not work. A reboot is required.
We have to manually open whatever port is needed by the specific application for the return response. For example, if I do an outbound dns lookup request I have to have a rule that opens up the port for the inbound reply (53) and this rule has to be for all IPs. If I try to write a rule that targets only the bridged address the reply will get blocked. It's an ugly problem but I expect that we'll get it resolved shortly.
Did you get a response on VMware Bridged Network Stateful Firewall issue?
When I deployed HIPS 7.0 globally for 7000 desktops, now all VMware workstation sessions cannot communicate to other network resources unless either I turn off the firewall or change ethernet settings from Bridged to NAT.
NAT might be the workaround but there are a few VMware sessions that require real IP address that were issued by corporate DHCP server.
If you have any idea or workaround, please let me know. Thanks,