Ghost Solution Suite

 View Only

  • 1.  GSS 2.0: clients not visible in console

    Posted Mar 21, 2007 10:56 AM
    Hello,

    I've got the following problem (among others):
    after installing GSS 2.0 console doesn't see some clients.
    I've looked in ngctw32.log on client systems and i see that client sees the console server:
    C:\Program Files\Symantec\Ghost\ngctw32.exe 11.0.0.1502
    21:51:11 08 March 2007

    16:51:13 130.37.24.144:1346 sending status to 130.37.20.129:1347
    16:51:13 130.37.24.144:1346 acknowledged by 130.37.20.129:1347

    Other clients, located on the same subnet and the same switch are visible in the console.


  • 2.  RE: GSS 2.0: clients not visible in console

    Posted Mar 23, 2007 08:04 AM
    Sounds very odd.
     
    Cheked if it is a firewall that is blocking?
    Are you running with a temp serial, that would only alow you to use 10 users!


  • 3.  RE: GSS 2.0: clients not visible in console

    Posted Mar 23, 2007 09:16 PM

    I've looked in ngctw32.log on client systems and i see that client sees the console server:

    C:\Program Files\Symantec\Ghost\ngctw32.exe 11.0.0.1502
    21:51:11 08 March 2007
    16:51:13 130.37.24.144:1346 sending status to 130.37.20.129:1347
    16:51:13 130.37.24.144:1346 acknowledged by 130.37.20.129:1347

    Other clients, located on the same subnet and the same switch are visible in the console.

    This sounds to me like you're being bitten by the duplicate UUID problem; in GSS2, we tried to switch towards using a special embedded BIOS ID that is guaranteed (in the specification) to be unique to any machine that has it. Unfortunately, some manufacturers have been building machines that have the same "unique" ID in every machine, and that can cause a problem where the server thinks two machines are the same one.

    We do have a fix for that, and you can get it by e-mailing me at nigel dot bree at gmail dot com

    Cheked if it is a firewall that is blocking?

    The fact that the ngctw32.log is showing that the client is in contact means that it's not a firewall issue; if the client is in contact but you aren't seeing it in the console then the likelihood is that the machines don't have unique BIOS IDs.


  • 4.  RE: GSS 2.0: clients not visible in console

    Posted Mar 28, 2007 10:36 AM
    Hi,
    I've also got this problem, and emailed Nigel at the gmail addr.
    Machines are all Dell Optiplex 260, 270, 280, and GX620 FYI...
    Many, but not all, have gone missing... BANGS and disconnected.

    About 30% of my clients show exclamation points after the upgrade and the first task being run, which should have upgraded the Windows clients.
    Also:
    I use hard, not virtual, GHOSTBOOT partitions, and when just the boot partition is installed and attempt to force an upgrade by running a configuration task, the client appears to upgrade, returns to polling/acknowledged, but the icon in the console still shows the BANG and also indicates disconnected.

    Re-imaging with the older version 1.1 bootpart restores the connection..

    Some machines, which show only a MAC had a 'refresh configuration' task run on them, which failed, says client timed out. But, the icon name changed from the machine name to just the MAC... Some machines have upgraded, others have become disconnected.
    The icon in the system tray show ok (no 'x') and the log shows polling/ack ok.


  • 5.  RE: GSS 2.0: clients not visible in console

    Posted Apr 13, 2007 11:14 AM
    Hi Nigel
     
    We are experiencing the same issue after installing GSS 2.0, may I send you out ngserver.log so I can get that patch from you ? The local firewall is disabled and clients are in contact.