• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

PXE boot will not work

maxdowd12

Junior Member
Hi guys,

I cannot get PXE to work on my Wyse Vx0 thin clients. My tftp and dhcp server are running on windows server 2008 r2. The dhcp server is configured correctly, but when I PXE boot on the clients (all connected via hub) it's says no dhcp offers were recieved. When connected to my main network, it's recives an ip, but can't find the boot file

Cheers,

maxdowd12
 
If it can't get a DHCP offer when connected via the hub, my guess would be the hub is goofed up - maybe the uplink port needs to use a crossover cable or something.

If it's getting an IP and attempting to PXE boot but isn't getting the boot file on the tftp server, the server is probably configured wrong (or the DHCP server is.)

DHCP server config should include both option 066 (host name of boot server) and 067 (bootfile name.) If you are using a hostname instead of an IP address, make sure DNS is working too.
 
If you're coming from a different sub network (VLAN), you will likely need a helper address to get you to the DHCP server. This is typically enabled in DHCP networks, but may also be needed for the server you are booting from, FYI.
 
It's defined on a switch. You'd have to have access to the switch to configure that sort of thing. If you're within the same broadcast domain, it won't matter. But, for instance, if you have your server IP as 192.168.1.100 and your clients as 192.168.2.10-100 all with a 255.255.255.0 subnet mask, broadcast packets will need to be 'helped' over to the other network.
 
If you're talking about the thing I think you're talking about, it may be listed as "ARP Resolution Forwarding" or something like that.
 
Thanks for all your help guys. Somehow, taking off option 60 made the thin client boot right up and request the tftp files!

Cheers
 
Back
Top