nice summary of remote installation settings

Discussion in 'NOD32 version 2 Forum' started by coyoteworks, Sep 5, 2006.

Thread Status:
Not open for further replies.
  1. coyoteworks

    coyoteworks Registered Member

    Sep 1, 2006
    I got this from an Eset tech recently. Hopefully it will help some of you out like it did me. It's a nice, concise summary of required server/client settings for remote administration. (Not all settings are absolutely necessary, but together they are sufficient, unless you've got some kind of software conflict.)


    "Following is a list of ALL crucial points and details I can think of that you might check:

    Can you ping the client <-> server both ways?
    Have the WinXP workstations disabled Simple File Sharing? (From any Windows folder window, Tools->Folder Options->View tab->bottom of list)
    Have the workstations got firewalls running that are blocking the remote configuration? (only needs to be disabled during installation period)
    Can you remotely log on to the client(s)?
    Can you make sure you have a correct administrator Username and Password set in the RA Console remote installation setup?
    From one of the workstations, can you run the Command Prompt: net use \\servername\ipc$ (to establish IPC connection to the server - make sure the 'spaces' are entered exactly as I've shown them)
    "File & Print Sharing for Microsoft Networks" must be enabled (Control Panel -> Network Connections > Network > Properties) --- (only needs to be disabled during installation period)
    Administrator password (or administrative user used to install) cannot be blank.
    The Remote Procedure Call (RPC) service needs to be running on the target.
    The Remote Registry service needs to be running on the target.
    The RPC Locater service should be set to "manual" and need not be running.
    NOD32 and RAS use the following ports:

    80 - client (normally only the 'Mirror' client) to Eset update servers.
    2222 - client communication with the server.
    2223 - RAC communication with the server.
    2224 - installer communication with the server.
    2846 - server replication (on the receiving, or 'upstream' server)
    8081 - client to local update 'Mirror' (default setting is 8081 but can be changed)
    445 - server to client, to request information and set up IPC connection (port 445 is the normal Microsoft "File & Print Sharing" port)

    Type 8 (echo request) - The server pings the client before attempting to install.
    Note: This is the port on the destination side of the connection. The source side will use a random, unused port above 1024.
    Personal firewalls (like WinXP SP2) need to have ports open for any of these, depending on the features you will use, but most are on the server side. A typical end-user workstation needs only inbound exceptions for 'File & Print Sharing', and to allow ICMP echo requests during the push install.

    If everything checks out correctly, and you still cannot connect to certain workstations, maybe you could try re-installing RAS. Uninstall first (Start > Control Panel > Add or Remove Programs > NOD32 Remote Administrator Server > Remove). There shouldn't be any need to re-start the server, but if it doesn't disrupt your network too much, it might be a useful step to take. Maybe download a fresh installer for RAS, and then re-install."
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.