Well, I have been searching for answers for my problem with ESET Smart Security, but it seems NO ONE has posted anything useful on Google or in these Forums so I decided to share my solution since I decided to poke around ESET myself versus trying to seek out help. Why? Just saves time sometimes versus learning how to use a product, hahaha...
Anyway, I have a HOST server that is running a Virtual Machine, this HOST machine has ESET Smart Security set up and I noticed that when I try to set up my Virtual Machine to allow REMOTE DESKTOP CONTROL (My Virtual Machine is running in BRIDGED mode) that I would be unable to connect to RDC. I also noticed that I would be unable to BROWSE the machine through MY NETWORK PLACES, so I found a solution that seems to work and I figured I would share it with everyone in case someone else is having this problem or WORSE I am doing something wrong... ![]()
So how do you solve this:
1) Open HOST and open ESET Firewall and go to ZONE AND RULES SETUP
2) Click on TOGGLE DETAILED VIEW OF ALL RULES and scroll down to BLOCK NETBIOS NAME SERVICE REQUESTS
3) Right click and select CREATE - SIMILAR RULE and change BLOCK to ALLOW
4) Click on REMOTE tab and ADD TRUSTED ZONE, then click OK and make sure RULE is turned ON
NOTE: You will notice that your rule has a number (2) aftewards, why? Well, notice that this rule already EXISTS but for some reason DOES NOT WORK. This is obviously something WRONG with ESET but the rule is broken into 2 rules one allowing traffic OUT and another allowing traffic IN, but this NEW rule allows traffic in BOTH directions in ONE rule, so NOT sure WHY this does NOT work...
5) Anyway, now rule is active and TRY to RDC to your Virtual Machine using the NETBIOS name
6) VIOLA, RDC works and now you can browse it on MY NETWORK PLACES...
I hope this helps the rest of you who are trying out ESET like me. ![]()
