I'm having trouble with Outpost Firewall 2008 and VMWare workstation 6. I've already searched the forums and the knowledge base for solutions, but nothing has worked so far. I created the two low-level rules according to instructions I found on the forums. Because of that the virtual machine is now able to properly obtain an IP address via DHCP and can ping any other system on the LAN and browse windows shares.
It CANNOT get out on the internet in any fashion. I have vmware.exe set as trusted, and I created the two low-level rules, but anytime I attempt to access anything on the internet, outpost blocks it with the rule "block transit packets" ( it shows the process as "" ). VMWare is running in bridged mode. I found a few posts related to transit packets, but they mostly recommended creating low level or system-wide rules using the option "packet type" which does not appear to exist anymore in OP 2008, or at least I couldn't find it as an option in either low level or system-wide rules. I also marked the 192.168.121.0 and 192.168.5.0 networks as trusted in Outpost's LAN config.
It works if I switch Outpost to Allow Most mode, but that's not really an acceptable solution for me. Anyone have any ideas?
Actually, forget what I said about it working in Allow Most mode, it apparently still blocks the transit packets in Allow Most mode. I need to completely shut down the firewall and stop the service to allow the VM to have Internet Access.
Hi,
I had this problem myself with VMware Workstation 6 and Outpost Pro 2008 (which I installed yesterday). I'm now using the following rules and seems to have full internet access:
Under System-wide rules --> Low-level Rules:
Where the Protocol is UDP
and Local Ports is: BOOTPC, BOOTPS
Allow
and
Where the protocol is IP
and IP Protocol type is ICMP, IGMP, TCP, UDP
and Local address is
Allow
I personally use static address so that may help? and I have the vmware applications (vmware.exe, vmnat.exe, etc) using automatically created rules.
Hope this helps,
>>>>F-4>>>>
I had those rules already, but I was able to figure out the problem. When I saw people say things like "vmware address" and "virtual machine address" I thought they meant the LANs of the two VMWare virtual network adapters (192.168.121.* and 192.168.5.*) so that was what I was allowing. What needed to be on the rules was its real LAN IP (192.168.1.x). I have it working now.
 I could use some help again...
 Lost Licences |
VMware problem with Transit Packets