Symantec Ghost & Win 2K Problems

[jc999]

Firstly, I realise that this forum may not be the most appropriate for queries regarding Ghost, so if anyone could suggest better/more specific forums then this would be appreciated - I can't seem to find any.

Secondly, I am having a lot of trouble with Symantec ghost Corporate Edition 8.0 and it does run on a w2k server so am thinking some people here may have some ideas.

The basic problem is this: I have installed Ghost Console and Tools to a win2k server which seems to have gone OK. I can then install the Ghost client remotely to computers of my choice on two subnets. (The server has 2 NICs, serving two subnets/vlans(?)). However, although the client installs and it starts running the syamantec client service on the pcs - none of the clients appear in the console.

What I need to know really is how to diagnose what the problem is. I have tried numerous reinstall's, reboots, virtually all ghost config settings to no avail. The strange thing is that I had it working perfectly for about 4 hrs. Tried it out on test machine/s and then when I went to roll it out to twenty pcs it wouldnt work at all. Now it just doesn't work full stop.

I am not sure whether it is Ghost(quite possibly doesn't seem very robust), my W2K server (maybe, I had to patch it to SP4 to get ghost to work at all - some config may be wrong) or general network(everything passes through 3com 4400 switches).

As far as the original problem goes - I can see all my clients from AD and map to them, ping them etc but the Ghost clients just don't appear in the console!

Anybody have any ideas on how I might go about fixing this? Unfortunately, we don't have any extra support from symantec. Their support site is of no use to me. Can't seem to find any way of diagnsoing it.....

Any ideas / links to good forums / good support appreciated.

 

[IAMINFO]

I had a similar problem here are somethings to check.

1. Ghost does not like 2 nic cards in a pc
2. On a vlan make sure multicasting is turned on (routers)
3. Make sure the ghost clients are the same version as the server.
4. Make sure dhcp is running if they are not using static addresses.

 

[mfryguy]

In addition to what IAMINFO has said:

4. Load balancing is turned off and IGMP enabled on switches
5. WINS service gateway is enabled across routers
6. NETBIOS over TCP/IP is set on the client and console
7. You have set the slot number for the desired nic in the protocol.ini in it's template
8. You have downloaded the most recent NDIS2 driver for the desired nic from the nic's manufacturer website, created a template, and applied it to the client properties of the client in the machine group

To check client network connectivity hold down the CTRL key while the mouse rest on the top left hand corner of the screen, a gold like disk will appear in the task tray near the clock, right click on this and choose show debug console, a dos like screen will appear, note what is being said (may have to wait a few minutes before any text appears)If it is saying only Polling for bound server, it can't find the console, If it is ACK/NAKing with sending status too acknowledge by and so forth by the correct IP address of the console server either you have a blown console DB, the configuration server service needs to be stopped and re-started, or the console server needs to be rebooted.