On a multi-homed server, there seems to be no way to select the NIC on which the GhostCast Server presents a session.GhostCast Server 8.x will create a Windows Firewall exception for itself but the exception still needs to be enabled manually.GhostCast Server uses (UDP) port 6666 for communications.Symantec’s knowledge base suggests that this may be down to TCP/IP issues and I’m pretty sure that packet-level network drivers are required with the MS-DOS client (the Windows server can use the normal Windows network settings) but, even with a suitable packet driver loaded, I gave up after a few hours without success. Ghost 6.x Enterprise has a multicast option but I couldn’t get it to work (it was always greyed out for me).Using Ghost in peer-to-peer mode does require the slave and the master machines to be running the same version of Ghost – it will present a version mismatch if you try and run different versions.If I had the Microsoft Deployment Toolkit 2008 set up at home then that would be reasonably straightforward but I don’t, and the old drive imaging technologies will be fine for this – at least that’s what I thought until I spent half the night and a good chunk of this morning fighting with Symantec Ghost… So, here’s a few of the things that I’ve (re-)discovered about Ghost in the last few hours. I need to rebuild one of my PCs before lending it to someone for a few days but before I do that I want to take an image of it. Please be warned that the information here may be out of date.

I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time.

Symantec ghost multicast server