Could be few reasons:

1. No connection between client and server.

2. Public-private certificates dont match.

3. Version mismatch, eg. beta software vs. production release.

Can you ping client from server machine and visa-versa?

I have/had similar issue recently.  I had to re-enable WINS on the DHCP servers in order for the clients to start showing up again.  I'm currently having multicast issue which is why i had to go back to WINS.

Just remember...its not an instant thing...but to test...once you have it set up correctly ...just delete a few workstations from dhcp leases and reboot them...or if your at one just do the release renew in cmd.

Reboots work better.  Once i did this my clients started showing up again.

However i still can't ghost.  :(

Hope it helps.

Here's what I get from my error log.

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date:  1/13/2009
Time:  8:23:23 AM
User:  N/A
Computer: NODE08
Description:
Application popup: Symantec Ghost Client Agent : The following information has been placed on the clipboard. Visit the Ghost forums at https://forums.symantec.com/syment/board?board.id=109 and supply this information to gain help with this error.
Symantec Ghost Client Agent
An exception has occurred of type C0000008
C:\Program Files (x86)\Symantec\Ghost - C:\Program Files (x86)\Symantec\Ghost\ngctw32.exe 11.5.0.2113
C:\WINDOWS\system32\ntdll.dll!RtlValidateHeap+0xA8C3
C:\WINDOWS\system32\ntdll.dll!RtlCheckForOrphanedCriticalSections+0x4D
c:\depot\ghost\gsstrunk\ghost\configureagent\library\src\aio\completion.cpp#764:Library::Aio::OperationBase::sendCallback
    unsigned int bytes = 0x42FA00
c:\depot\ghost\gsstrunk\ghost\configureagent\library\src\aio\pipeio.cpp#224:Library::Aio::PipeListener::beginAccept
c:\depot\ghost\gsstrunk\ghost\configureagent\library\src\win\pipeservice.cpp#574:Library::Win::PipeService::startListen
c:\depot\ghost\gsstrunk\ghost\configureagent\client\clientstate.cpp#65:ClientService::initialize
0xFEDCBA98
0x89ABCDEF
C:\WINDOWS\syswow64\RPCRT4.dll!NdrConformantStructMarshall+0x12B
0x90909090

Hi Matthew,

There was a similar issue on the server side (same back trace) which turned out to be related to number of CPUs in the system. In your case, what is the hardware config of the client? especially the number of CPUs?

Does this happen all the time (when ever you restart the machine or ngclient service)?

Krish

Hi,

What is the version of your client? If you look at the ngctw32.log file at client, it will tell you the build number.

If I remember correct, it was not expecting more than 16 CPUs and configuraiton data could not be read.

Krish 

Hi,
The built number that appears at ngtw32.log is 11.5.0.2141, does appears in any documentation the maximum number of CPUs that are supported? , is predicted in some later version the solution for this problem?

Thaks

Hi,

Sorry for the delay, do you have the same OS in 8 Proc machines too?

Number of processors in a machine grew rapidly in last couple of years with multicore systems. I think this was not documented as a limitation since such systems were not available. I will see when it was fixed and if it is before 2141, this could be a different situation.

Krish

 Hi,

I will have to look further, the issue I was thinking about was fixed before 2141. By any chance, do you use any other OSs than 2k8 64bit with these systems? If so, are they working fine?

Krish

Hi,
There are several OSs in our GSS 2.5 clients, Win 2K Enterprise, Win 2003 Server Standar & Enterprise x32, Win 2003 Server Standar & Enterprise  x64 and the mentioned Win 2k8 Enterprise x64, all of them works fine unless Clients with 2k8 and 24 Processors.
Thaks

 Hi,

This appears to have fixed after 2113. Since your client seems to be failing before upgrade to the new version, could you uninstall and re-install the new client?

Krish

Hi,
We instaled new server three days ago with 24 Processors too and  version 2141 and the problem persist.

 Hi,

Sorry for the delay, for what ever reason, I just got the notification. 

Could you post the error dump from the build 2141 client? That will help us a lot to identify the issue.

Krish

HI,
Here's what I get from my error.

Log Name: Application
Source: Application Error
Date: 6/18/2009 2:02:36 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application ngctw32.exe, version 11.5.0.2141, time stamp 0x48c09eeb, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0xc0000008, fault offset 0x0005986b, process id 0x1830, application start time 0x01c9f00cab49b89c.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-06-18T12:02:36.000Z" />
<EventRecordID>5486</EventRecordID>
<Channel>Application</Channel>
<Computer>
</Computer>
<Security />
</System>
<EventData>
<Data>ngctw32.exe</Data>
<Data>11.5.0.2141</Data>
<Data>48c09eeb</Data>
<Data>ntdll.dll</Data>
<Data>6.0.6001.18000</Data>
<Data>4791a783</Data>
<Data>c0000008</Data>
<Data>0005986b</Data>
<Data>1830</Data>
<Data>01c9f00cab49b89c</Data>
</EventData>
</Event>