Strange more - while trying around one time I got another IP as the first one (10.8.8.250) - an address from the same subnet, but another switch. The first one was a switch. All PXE-Clients working fine, only in one subnet all clients gave the error with PXE-E32.One thing was sure soon: the TFTP on the WDS Server never got a request from the PXE-client, if the client was in that subnet.With ESX it is easy to change the subnet of a machine, and I found out: the same (virtual) client, the same NIC, the same DHCP-Server, the same WDS-Server - working perfekt in all subnets from this domain, but in that special subnet (the main subnet, whereAll the clients in my building are connected) it did not work!!!After some trying and guessing I recognised that the client got TWO gateways in this subnet (same picture than your client!!!) - the first one I never configured anywhere as a gateway, the second was the right one (10.8.8.252 the wrong one, 10.8.8.254That was strange, because my DHCP-Server had only one (the second one). Advertise in the "Uknown Computer" and Advsertise in the "TEST Collection" where I added the MAC address and gUIDAfter fighting with the same problem for some hours I finally found the error in MY system - and your 2 gateways at the pxe-clients could be a hint that you have the same problem :The story: I have an VMWAre ESX server, connected with many IP-Ranges and many WDS-Servers in many domains.
The IP of the switch with the IP-Helper-Address is the primary gateway that the PXE-client is showing, the real gateway is number two- and he tries to conact the TFTP-Server only over the first gatway.After I removed the "ip helper-address" on the other switches I got only one gateway and the client booted like a charm.You saved my day. Didnt know that this could be a problem.
0 kommentar(er)
