Bruno Neves

Actually that examples are from servers and workstations. They are always on the same VLAN 24/7h UP, ip it's always the same.

Hi guys, I am the manager of ESET in the company where I work. And we're always having this problem ... example 1: example 2: Can someone explain to me why this happens and if I can do something to prevent this from happening again? I usually clean the duplicate products from time to time... Thx alot, Bruno Neves

Sorry. I have the version 6.5.522.0 of ESET Remote Administrator and 6.6.2046.0 of ESET Endpoint Antivirus. I see that on cmd after a use the netstat command. Meanwhile i resolve the problem So i configure the machine with the name ESETMANAGEMENT and the server was working. After sometime for some reason i change the name to ESETConsole and was that what ruin my console. Probably the querys of sql crash because the name of the machine change and sql can't resolve that new name. (i think you can close the topic) Sorry for take your time and thanks for helpfulness, Bruno Neves

Hi guys, I use Eset remote Administrator 6 and i test with few computers last month, all work really great. Then last friday e extend the installation to more machines and nothing happen on the console. The agent it's fine i go to openELA and the license is attributed but in the console don't get any change. So i go after the problem and i see this: 127.0.0.1:2223 "the name of the machine here is the eset console":xxxxx So this mean that is communicate only to himself Someone have this problem and solve it or know the resolution to this problem ? If i force the port to be open in the IP of the set server will work? it will be worst? Thx, Bruno Neves