Eset's Remote Administrator Console - wrong computer names and IPs

[Clockworks]

We are doing a small little test run of Eset's NOD32. I love the AV, it's great. I got it to work on the server and it was able to pull up a list of nearly all the machines in the domain (only one - small company). Problem is, a lot of these machines have the wrong IP or are just plain missing (such as mine) from the list. How do I fix this?

 

I tried to Deploy NOD32 to the machine that has my IP but it fails to do anything of the sort.

[leco]

Which version of NOD32 are you running? I guess you've tried Refresh on the console? So if you have a DHCP server and/or DNS server then check those for incorrect data. NOD32 often cannot deploy to computers with a firewall turned on, but you would normally get a message about that. What messages are in the install tab? Also isn't there an Events tab for messages about what's been going on? Sorry dragging up images from my memory as my own Eset console isn't working currently.

[Clockworks]

Which version of NOD32 are you running?

Whatever the latest is, got it this morning.

I guess you've tried Refresh on the console?

Yes, it refreshes every 30 or so seconds

 

So if you have a DHCP server and/or DNS server then check those for incorrect data. NOD32 often cannot deploy to computers with a firewall turned on, but you would normally get a message about that.

Not sure, will have to check on it...

 

What messages are in the install tab?

Could not set up IPC connection to target computer (SC error code 6, GLE error code 1396)

Also isn't there an Events tab for messages about what's been going on? Sorry dragging up images from my memory as my own Eset console isn't working currently.

I honestly have no idea, just got this thing.

 

My thoughts with your quote.

 

It should not be this friggin difficult to install this damn program.

Edited August 24, 2010 by Clockworks

[leco]

To be going on with try this link for the Eset Forum. I'll have a look as well since two heads tend to be better etc. etc. I agree on the difficulty bit it does get frustrating sometimes. However, in the eight or so years I've been using it, I think it's worth it.

 

Take a look at this thread on the forum for some ideas to check.

Edited August 24, 2010 by leco

[OverWorked]

Did you get anywhere with this? I'm having the exact same error on a few machines.

 

Could not set up IPC connection to target computer (SC error code 6, GLE error code 1396)

 

I have a room of 17 machines. All XP installed from the same RIS image, all with the same GP settings.

 

For some reason, four of them will not install NOD32, when pushed from the ERA. I have tried entering the domain admin account credentials and several others.

 

Is there a way of installing manually from the client, like there is with Sophos?

 

Utterly frustrated.

[bio]

 

Is there a way of installing manually from the client, like there is with Sophos?

 

Utterly frustrated.

 

check here : http://www.eset.eu/knowledge-base/ess-eav-specific-installation

 

bio..

[OverWorked]

Thanks for the suggestion.

 

I've found the cause and ifxed it it was a good old DNS error. The clients weren't registering their new IP addresses, so the DNS records were out of date and ERA couldn't find the clients.

 

As simple as that. Funny how a lot of problems are down to DNS.

[witch]

TBH if in doubt I just ring them up - they are some of the nicest and most helpful support people I have ever dealt with