Ghost Imaging using PXE and WDS booting clients across layer 3 network

[petben]

I have been using Ghost Imaging using PXE and WDS for many years. I have just had a layer 3 routing network put in and now Ghost is not working, the clients can F12 boot but it finds no server.

 

The network engineer thinks it can be fixed by adding DHCP server options of 066 'Boot Server File Name' and 067 'Bootfile name'. These options were never there before...I have tried a few options in the Bootfile name and I can get the boot menu to appear and choose the Ghost session to start, but it can never actually contacts the server.

 

any ideas?

[MatthewL]

You need to do this on your DHCP server as seen in screen grab attached.

 

[free780]

One subnet or many?

[FN-GM]

I wouldn't use the DHCP option. I would use a IP Helper Address on your VLAN and point this to your PXE server. What switches do you use?

[petben]

I wouldn't use the DHCP option. I would use a IP Helper Address on your VLAN and point this to your PXE server. What switches do you use?

 

we use netgear switches, with a netgear layer 3 core switch. what and where do I put the helper address. I'm very new to this outing stuff.

[petben]

You need to do this on your DHCP server as seen in screen grab attached.

 

[ATTACH=CONFIG]22945[/ATTACH]

 

ok but what do I actually put in the 067 boot file name?

[FN-GM]

Sorry I don't know how to do it on netgear. Never used them. I have only dealt with Cisco really.

[free780]

RTM? Google the router model should come up with netgear support.

[Asgard]

On a Layer3 netgear switch (is it the GSM7352S) do it in

 

System -> Services -> UDP Relay

 

Add in the IP Address and Port

 

Then go into maintenance and save the config.

 

We run NetGear here and had a case study performed on it

 

http://techdataukinfo.co.uk/microsites/public-sector/docs/netgear/netgear_case_study.pdf

Edited February 19, 2014 by Asgard