WDS _ PXE Booting not working on SOME machines

[Ric_]

Since updating to WDS (Legacy Mode) I have not imaged any of my Dell Latitude D505 laptops. I have used WDS with Dell Optiplex machines and PXE boot also works on a HP n8000 laptop.

I do not receive any error message, it simply displays the DHCP bit with the ´twirling´ line and LOTS of dots.

Help is needed! :cry:

[tosca925]

We had this problem with Dell's IIRC. I think in the end for a quick fix we had to take the TFTP server options out of DHCP to get it to work.

I know this i not an option for you as you have thin clients, but this DHCP settign screwed WDS upf or us. As soos as i took the setting out it worked.

Try it it may not be the issue in your case.

[Ric_]

@tosca925: That seems to have done the trick (removing option 66 and 67)... fortunately I´m removing the last Thinstation client as we speak

[tosca925]

Now you know what i was going through when i was picking your brains when we tried out thinclient here. I still want to use thin cliet for certain rooms but this forces me to manula change the DHCP options before or after school so i can re-image a pc/laptop then change them back so the thin clients can log on next day.

I wish/hope their is a way round it.

I take it Ric that you never had any trouble with RIS? only now you do with WDS?

[Ric_]

@tosca925: RIS was fine... just this blasted WDS that buggered it all up :cry:

[Geoff]

I wish/hope their is a way round it.

It's called a VLAN.

[tosca925]

Expalin more Geoff?

[Geoff]

If you put your thin clients on a separate VLAN you will separate out the broadcast traffic (and thus DHCP) from the rest of your network.

[bazuk]

Hi all
I dont know how you do it in windows network but in a unix system you can set up a pool for thin machines which point to a bin file to boot them into a thin client system then have another pool for the rest, usually done via mac address, this is because the next server option for the isc dhcp can be set locally or globally, you just run 2 tftp servers on differrent ip addresses one for booting thin the next for ghosting, means you cant ghost a thin machine but then why would you want to???

for our thin booting we use a pxelinux.0 bin file on the tftp server i have found its easier to ghost machines using a usb key with all the network card drivers installed on it in a little menu thing, this is easier as all our new systems allow usb booting via bios

regards baz