GL error code 1203

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

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

    coyoteworks Registered Member

    Hey, I'm getting the following error during a pushout from the Remote Administrator to a client PC:

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

    I checked and found this in an earlier post, so I know where to go to look up the GLE error codes, but I still couldn't find the solution.

    Any ideas?
  2. coyoteworks
    Offline

    coyoteworks Registered Member

    Following up on my post... Here is what the Microsoft site says about GLE error code 1203:

    ERROR_NO_NET_OR_BAD_PATH
    1203 The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.

    Here's the site: http://msdn.microsoft.com/library/d...debug/base/system_error_codes__1000-1299_.asp

    I got this far from a prior post at Wilders.

    But the message is kind of vague. I've got the Remote Administrator Server and Console installed on a Windows Server 2003 machine. I've created a Windows NT/2000/XP package from the latest available downloads. And I've successfully pushed the package to a couple machines, but the majority are giving me this error (described in my original post).

    Maybe this additional information will tickle someone's brain.

    Thanks.
  3. coyoteworks
    Offline

    coyoteworks Registered Member

    I'm posting this here, for anyone who comes across this or any other obscure error. I got through to a tech at Eset, and he sent me an awesome :)thumb:) summary of all the critical server and client settings for making remote installation happen. Using these settings, we were able to make the GLE 1203 error disappear.

    Here is his email to me, more or less in full. I am also posting it as a separate post. (Any minor deviation from his email is noted with []'s.)


    "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:

    TCP
    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)

    ICMP
    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.

    [Check] the log from the server[...] - C:\Program Files\Eset\RA\nod32ra.log

    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."
  4. YeOldeStonecat
    Offline

    YeOldeStonecat Registered Member

  5. MidSpeck
    Offline

    MidSpeck Registered Member

    I have a similar issue, but some unique circumstances. I am simply curious as to anyone has any ideas for me. If this should've been under a different thread, feel free to move it.

    I am trying to install NOD32 onto some laptops that are spread throughout the country. They are not joined to a domain. Some run XP Home, some XP Pro.

    We have our NOD32 RA Server on a private LAN, but I have opened up the external firewall ports 2222, 2223, and 2224 such that our outside computers can contact the server.

    The only way that I can install it (with all of our settings, at least) is to e-mail them the nod32installer.exe and have them run it with:
    nod32installer.exe SERVER=xx.xx.xx.xx (our external IP)

    An excerpt from nod32installer.log on a computer running Windows XP Home edition:
    Code:
    Status 1: NOD32 Installer (1.0.14) is preparing to install.
    Status 1: NOD32 Installer is trying to connect to 'xx.xx.xx.xx:2224'.
    Status 1: NOD32 Installer is sending installation request.
    Status 2000: Could not set up IPC connection to target computer (SC error code 6, GLE error code 1203)
    Status 1: Request failed. NOD32 Installer has administrator rights, trying to continue.
    Status 1: NOD32 Installer is creating a temporary file.
    Status 1: NOD32 Installer is downloading an installation package 'Company Antivius" from server 'xx.xx.xx.xx:2224'.
    Status 1: NOD32 Installer is installing NOD32.
    Status 1012: Failure during NOD32 install - exit code: -1073741819.
    Due to the spread out nature of our company, I cannot get everyone to shutoff their firewalls, forward ports from their NAT boxes, etc. So I doubt that we will ever get that IPC connection it wants. It seems like it was about to install though, and failed.

    I don't need things to be completely automated: just simple enough that all the end user has to do is run a file and it'll install NOD32 with the settings that I have set in the package.

    Thanks for your time.
  6. Marcos
    Online

    Marcos Eset Staff Account

    Any negative code like -1073741819 means the installer crashed. You should run setup.exe on that computer manually using the parameter "/test" and send nsetup.log to technical support for perusal.
  7. YeOldeStonecat
    Offline

    YeOldeStonecat Registered Member

    You need network access as if on a local LAN, or a wide area network such as done with router to router VPN tunnels. You'd certainly not want to open up netbios and networking ports on the firewalls.

    Starting to realize the drawbacks of having large networks that are simply peer to peer, time to start looking into active directory and WAN control, else antivirus management will be the first of many network management issues.
Thread Status:
Not open for further replies.