Set-Up VMware Workstation Bridged Networking with ESET Smart Security 4 Firewall

Below are the steps to follow to get a network connection working with the VMware Host and ESET Smart Security 4 firewall, when Bridged Networking is set.

1. Open the main program window by clicking Start -> All Programs -> ESET -> ESET Smart Security.

2. Press the F5 key to open the Advanced Setup window.

3. From the Personal Firewall tree on the left, Click IDS and Advanced Options, and then select Allow communication for bridged connections from the Allowed Services tree.

22 comments to Set-Up VMware Workstation Bridged Networking with ESET Smart Security 4 Firewall

  • Psycho Nelo

    Thanks. Just tried it and it worked.

  • Godo

    You are the best.

    Thaks a lot.

  • seplevova

    Other variant is possible also

  • Bimbbluerie

    Hi people! Very much interesting site. We enjoyed visiting your website very much. .. … Bye

  • Dickimitync

    Hello, Good site – you’re a pretty good writer…..very creative. Good luck!

    • Jose

      I own both VMWare and Parallels. Even though VMWare is faster, it has some drawbacks that leave me using Parallels instead.

      1. I use SecureCRT for Windows to access the character-based version of the back-office software my company resells. The software (SouthWare Excellence Series) uses keystrokes that VMWare doesn’t properly pass to the program, but Parallels does. (I’ll eventually get around to reporting this to VMWare to see if they can resolve it.)

      2. Parallels allows me to double-click a file in Finder and open it in a Windows program. This is important because a lot of my clients send me MS Office files, and it just saves time to be able to default to opening in Office XP.

      3. In Parallels, if I have a Windows program open, I can drag a file from the finder into the programs application window, and Parallels will translate the UNC path and open the file from the network . This also works in a file open dialog on Windows; just drag the file from Finder to the file open dialog, and it translates the path. The same action causes VMWare to copy the file to the Windows VM before opening it so I’m not actually editing the original, but a copy of it.

      Perhaps VMWare has improved some of these issues with its latest update; I just haven’t had time to test.

  • I’ve recently started a blog, the information you provide on this site has helped me tremendously. Thank you for all of your time & work.

  • educational grants

    well written blog. Im glad that I could find more info on this. thanks

    educational grants

  • Lisabeth Marze

    hello, thank for this astonishing information. Therefore, I would like to ask for your permission to add some of this information in my blog. Of course, I will provide a link to your website, as a source of my quoted information.


    • Leo

      I think you’re right. This is something that reetlcny changed in VMware Server, so that virtual switches behaved more like real switches, and less like hubs. It was raised as a performance and security concern in the past.The recommended way to monitor VMs is the way you described, from the host OS. If you use the non-free ESX Server, you can do more advanced things like configure virtual VLANs, etc.By the way, have you seen ? They have some interesting concepts on monitoring VMs from the outside.

  • Forest Schroot

    Your blog is so informative ¡­ keep up the good work!!!!


    • Ifikl

      0Really great list of apps. These apps are looking inttreseing. But i havn’t any app from the list. I will try to install some apps in my android phone.Thanks.

  • kit ricarica cartucce

    Great blog. I like the way you have it laid out. How can I subscribe to RSS? Thanks. Cartucce

  • Chelsea Handler

    Cheers, great blog post.

    • Robert

      Had the same problems and goolge pointed me to this blog.I am running VMware server 1.0.4 build-56528 and have two openbsd VMs connected to vmnet1 (host-only) and was not able to see the ping traffic from host to VM1 on VM2.

      The following steps fixed this:1.) stop vmware server2.) chgrp vmadm /dev/vmnet*3.) chmod g+rw /dev/vmnet*The UID which is used to run the VMs needs to be in the group vmadm.

      Now the OS in the VMs is able to put the interface into promiscuous mode and see the packets for the other VM on the same vmnet network.

  • Kyra Houtchens

    Hi I have been reading your blog for the past two weeks and it is interesting, do you have a RSS feed?

  • Flores

    I was just doing some web browsing on my Phone during my lunch at work , and I came across something I thought was interesting . It linked over to your website so I jumped over. I can’t really find the relevance between your site and the one I came from, but your site good anyway.

  • Mike

    Great blog. I have myself started blogging and I like to keep up with the technology news and trends. Please do visit

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>





This site uses Akismet to reduce spam. Learn how your comment data is processed.