• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3111
  • Last Modified:

Symantec Ghost 2.5 Ghostcast PXE Boot

My goal: To PXE boot multiple machines into ghostcast server and push images to clients.

My problem:  It's not working.

My equipment:
Ghostcast server: Dell OptiPlex 780 running Windows 7 Professional x86
Switch: TP-Link TL-SG1016D Gigabit Switch
Clients:  Dell OptiPlex 960's and OptiPlex 760-780's

What I have done so far:
 I have loaded ghostcast server, as well as the 3com boot service package.  I created a boot file in ghost using the Windows PE package. I added the driver files for the NIC cards of all the machines to the boot package.  I also loaded TFTPD32 and have configured this as my DHCP server as well as my TFTP server.  The bootfile in the DHCP options is set to /boot/pxeboot.n12.  

Results:
I can PXE boot the client into the Windows PE environment and ghost will run.  I try to run multicast and the client will never find the ghostcast session.  I am showing a local IP of 127.0.0.1 on the client.  For some reason it is not booting into the Windows PE environment with the IP assigned via the DHCP server.  I can not get a connection to the ghostcast session.

Any help would be appreciated.
0
deshaunstyles
Asked:
deshaunstyles
1 Solution
 
Aaron TomoskySD-WAN SimplifiedCommented:
Fist step is to get dhcp working. Until ghost cast server and clients both have ip addresses, nothing else matters
0
 
vivigattCommented:
Multicast is hard to configure, especially if you have multiple subnets.
First: make it work in unicast mode.
Since you are able to PXE boot, the first steps (DHCP and PXE based) seem to be working.
You have the WinPE environment OK, now make sure that this WinPE image can access the network, at first in Unicast. It means, in particular, that you need the corresponding Network drivers in your WinEP image. When this works, try to use ghost in Unicast mode, maybe at first just by opening a ghost image that sits on a remote shared folder
0
 
deshaunstylesAuthor Commented:
I needed to load my network drivers into the WinPE image just like you said.  Once I did this, my ip address was showing up and I could connect to the ghostcast server.  Thank you so much!!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now