Wilders Security Forums  

Go Back   Wilders Security Forums > Archived Forums > Closed Sub-Forums > Archived ESET Support Forums > NOD32 version 2 Forum
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
 
Thread Tools Search this Thread
  #1  
Old July 21st, 2005, 05:14 AM
barry2005 barry2005 is offline
Infrequent Poster
 
Join Date: Jul 2005
Posts: 3
Default rac problems

We are testing a network installation of nod32 right now, thus including remote installation console. The push installs work fine, the monitoring of clients does not however. In the console settings we chose default connection (localhost port 2223). What settings should we push in the config.xml file in the section 'remote administration server' and port number? Is the use of unc paths needed here perhaps?
  #2  
Old July 21st, 2005, 09:30 AM
webyourbusiness's Avatar
webyourbusiness webyourbusiness is offline
Very Frequent Poster
 
Join Date: Nov 2004
Location: Throughout the USA and Canada
Posts: 2,582
Default Re: rac problems

Quote:
Originally Posted by barry2005
We are testing a network installation of nod32 right now, thus including remote installation console. The push installs work fine, the monitoring of clients does not however. In the console settings we chose default connection (localhost port 2223). What settings should we push in the config.xml file in the section 'remote administration server' and port number? Is the use of unc paths needed here perhaps?

push the ip address of the machine running the remote administration server and the port... should work fine.

regards

Greg
  #3  
Old July 21st, 2005, 11:49 AM
alglove alglove is offline
Frequent Poster
 
Join Date: Jan 2005
Location: Houston, Texas, USA
Posts: 904
Default Re: rac problems

On the client side, go to the NOD32 Control Center --> NOD32 System Tools --> NOD32 System Setup --> Remote Administration tab. Make sure the "Connect to Remote Administration Server" box is checked, the "Server address" is set, and the "Port" is set to 2222. See the attached picture.
Attached Images
 
  #4  
Old July 22nd, 2005, 12:09 PM
anotherjack's Avatar
anotherjack anotherjack is offline
Frequent Poster
 
Join Date: Jun 2003
Location: Louisiana
Posts: 224
Default Re: rac problems

Quote:
Originally Posted by barry2005
We are testing a network installation of nod32 right now, thus including remote installation console. The push installs work fine, the monitoring of clients does not however. In the console settings we chose default connection (localhost port 2223). What settings should we push in the config.xml file in the section 'remote administration server' and port number? Is the use of unc paths needed here perhaps?

I run the RA Console on a different machine than my users connect to for updates. If that's also your case, you need to add the machine that your users are reporting to to your console server list:

Tools / Console Options / Add/Remove / enter your server name / Click Add / Click OK

That should do it.

Jack
 

Wilders Security Forums > Archived Forums > Closed Sub-Forums > Archived ESET Support Forums > NOD32 version 2 Forum « Previous Thread | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -4. The time now is 11:48 PM.


Powered by vBulletin® Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums