Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Client “Trying to locate [servername]” - Not Finding Ghost Server

Updated: 21 May 2010 | 4 comments
benevolent jim's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Ghost Console version 11.0.2.1573

I successfully performed a Remote Client Install but the client does not show up in Machine Groups or when browsing for Targets.

Client Machine E6400GHOST-LAB
IP Address: 192.168.10.187
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.10.1

Ghost Console Machine IRGMGMT01
IP Address: 192.168.10.179
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.10.1

I restart the client service and I get these every 2 minutes in ngctw32.txt

  • 192.168.10.187:1346 polling for bound server irgmgmt01

The balloon tip shows displays the message:

  • “Trying to locate irgmgmt01

The client is running Windows Firewall but Symantec Ghost Client Agent is added as an exception.

Why can’t the client locate the server? It’s 1 hop away.

Thanks in advance for your assistance.

discussion Filed Under:

Comments

mihailescu's picture
16
Jul
2009
0 Votes 0
Login to vote

Did u try to drop the

Did u try to drop the firewall on the client and see if the client connects, in ordert o eliminate that possibility? Ben

benevolent jim's picture
16
Jul
2009
0 Votes 0
Login to vote

I just turned off the Windows

I just turned off the Windows Firewall and restarted the Symantec Ghost Client Agent and I still get these messages and no connection:

12:40:29 PM 192.168.10.187:1346 polling for bound server irgmgmt01
12:40:39 PM 192.168.10.187:1346 polling for bound server irgmgmt01
12:40:59 PM 192.168.10.187:1346 polling for bound server irgmgmt01
12:41:39 PM 192.168.10.187:1346 polling for bound server irgmgmt01
12:42:59 PM 192.168.10.187:1346 polling for bound server irgmgmt01

Kurbycar32's picture
16
Jul
2009
0 Votes 0
Login to vote

ports

the firewall or antivirus on the server could also be blocking this traffic.  heres a document that shows what type of network traffic that needs to be cleared.  also if you are using an antivirus that has any type of network protection it may be blocking certain types of multicast traffic to prevent mass mailing worms and as a result killing your ghost traffic.  mcafee enterprise does this by default.  for troubleshooting i would disable the antivirus and firewall on both the client and server

service1.symantec.com/SUPPORT/ghost.nsf/ppfdocs/2002101612025325

benevolent jim's picture
16
Jul
2009
0 Votes 0
Login to vote

Thanks for the link...

Yes, since these are both in a lab environment and sitting right next to each other in my office; neither machine have TrendMicro installed (yet) and I went ahead and left the firewall off.

Thanks for the link. That gives me something to chew on for a while.