If you specify the server IP and force a non-multicast transfer using these switches you should be able to do cross-subnet image transfers just fine (although it may be worth your time investigating whether you can enable your network for cross-subnet multicast). The server IP can be forced using ' -jaddr=' and the transfer mode (unicast, subnet-directed broadcast, multicast) can be forced using ' -jm=' where the mode is a letter 'M' for multicast, 'D' for directed broadcast, and 'U' for unicast. It's not in the help page for some reason, but there are command-line parameters for just about everything you can do in the Ghost UI. > I noticed that there's no parameter for server's ip address to use with ghost.exe This was one of the Top Download Picks of The Washington Post and PC World. We recommend Security Task Manager for verifying your computer's security. Therefore, you should check the ghost.exe process on your PC to see if it is a threat.

Important: Some malware camouflages itself as ghost.exe. Given the large volume of data involved in distributing Ghost images, multicast and imaging are a great fit when it comes to making the best use of a network, provided you can enable it. Ghost.exe is able to record keyboard and mouse inputs. IP multicast is the method that Ghost uses by default both to get in touch with the image server and to distribute the image data efficiently (there's a nice overview of IP multicast at ). It's likely that the routers connecting the subnets in your network are blocking IP multicast traffic for some reason. Problem seems to be that client machines and GhostCast server are in different subnets

Commentarydb ghost exe