Ghost Solution Suite

There's lots of things it could be - a search of "remote client" or something like that will kick up a ton of stuff on the forums here.  Offhand, if you're using Ghost 7.5, it won't Remote Install in a Workgroup, it has to be a Domain.  I think since Ghost 8, that restriction went away.

Otherwise, the usual suspects - filesharing is on, remote registry service is on, simple filesharing is off, etc.

On your 2003 system, open up a terminal window, and just see if you can "net use Z: \\mytargetremoteclient\c$" and see if that works.  Give it the same credentials as you entered into the Console when doing the remote install.  If that basic net use doesn't work, then the Ghost console won't work for you either.  It's a cheap, easy check.

PH

Usually it's that Simple File Sharing is turned on, which is often the default for machines that aren't joined to domains.

[ A good historical explanation of this is at this post by one of the guys who originally worked on Lan Manager which explains how the administrative filesharing system came to exist at all. ]

I don't remember if there was Simple File Sharing thing on 2000 or not, but poke around anyway.  It could be remote registry service (if that existed in 2k.)  Another thing to check is the NTLM level on your 2003 server.  Set it back down to just plain old NTLM or even just LM.  Again, don't recall if 2000 speaks any of the newer NTLMv2 and stuff.

If the basic net use stuff doesn't work, then definitely that's where to start.  Make sure the 2K clients actually have File/Printer Sharing turned on (lot of times, it's off for security reasons - most *clients* don't really need to share out in a domain, that's what the servers are for.)

Good luck!
PH

While anything is possible, I doubt you wiped out the EEPROM on your target client machine.  I think what happened was simply that Ghost's virtual partition is trying to boot and is failing.  Since you can get into the BIOS, you should be ok.  You can always reflash your BIOS via floppy.  I bet the problem is the system is just trying to boot off a hard disk that's messed up.  Set your BIOS to boot off Floppy and nothing else and then reflash and reset your BIOS.  Then boot again off a Ghost Boot disk made using the Ghostboot Wizard on the Console machine.  If you still have your previous image from before, push that back down to the system.  If you used the *exact* same image-create task, then the image file probably got hosed when the image-create task started (and then failed) so your existing image file probably won't work. 

When you get the flashing cursor, just try a simple Ctrl-C.  It might bring you back to a DOS prompt.  Type ghreboot and that should let you boot into the normal drive partition.  Push comes to shove, you may have to reinstall from CD, but if it really was just a image-create task, your hard drive should actually still be ok.  You just may have some weird virtual partition or something.

PH