NOD32 RAS Breaks Network Browsing

We have hit a major problem while running a trial of NOD32 Business & RAS.

Our network is configured into various subnets - our corporate, engineering, test, build etc.
Our main corporate network is where the majority of our Windows servers live, however we also place a single Windows server into each Subnet and promote it to be a Domain Controller.
This helps with local subnet logon and also network browsing as the Windows DC will win any elections and be the Master Browser.

After installing RAS onto the DC on our Engineering network, the DC can no longer correctly retain browse lists.
The machine can see other machines on the local subnet but not on any other subnet.
If we disable the Computer Browser service then the machine can retrieve a list from another machine.
However re-enable that service and as long as NOD32 & RAS are installed it will not browse correctly.

Removing all of the NOD software from the server does not fix the issue.
If however we totally wipe the machine, reinstall the OS then Network Browsing works absolutely fine - no issues at all.
The minute you reinstall the NOD32 software it breaks everything and to the point where you need to do an OS reinstall.

Has anyone seen this problem at all and have any ideas on what the NOD32 software maybe doing?

Right now we have two choices:

1. Run the NOD32 RAS on a different server - not ideal but a solution.
2. Stick to our Symantec solution that doesn't cause any network browsing issues

 

RAS(Remote Access Service) on a DC as a computer browser? Computer Browser does not support multi homing. Google it and you will find Microsoft says it's not supported.

I'd say move your Computer Browser to a server or PC not doing RAS. I assume you mean RAS and not eSet RA (Remote Admin.) If you meant that, then different problem.