Optiplex 390 with Realtek NIC
-
-
Something I noticed about this picture I did not notice prior. This is showing two gateways. There should only be one. I booted up a Latitude 3330 with an Intel nic and I get the correct gateway. I rebooted the same 390, now instead of 3.62, it shows 3.70, along with the 1.1. I have never seen that before in 10 years.
EDIT: Digging a little more, the 3.xxx IP address are the DHCP reservations of our access points. going to investigate farther. Still doesn’t make sense why only the realtek machines are seeing this. -
@adukes40 Is the FOG server on the same subnet (vlan) as these 390?
If they are then we can get a quick answer if you follow the instructions in this tutorial: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
If they are not, getting the answer is a bit harder but possible. You can use wireshark on a computer that’s plugged into the same subnet as the 390s to capture part of the dhcp/pxe boot process. That will give us an idea who the actors are during this pxe boot.
Having the FOG server collect the pcap will give us the best quality pcap since it will see the entire conversation. But the client has to be on the same subnet as the fog server to do that.
Upload the pcap to dropbox or a google drive and share the link with us or DM me directly and I’ll take a look at it for you.
-
@adukes40 said in Optiplex 390 with Realtek NIC:
Still doesn’t make sense why only the realtek machines are seeing this.
Possibly realtek’s PXE implementation is a little different and that’s why. But this definitely looks like an interesting issue that you better look into using George’s advice on wireshark/tcpdump…
-
The building where this is failing is on the same campus as the FOG server, but they are separate subnets. I will take the machine over there and see if it does the same thing. If so I will attempt the pcap.
-
Welp, took the 390 over to the other building. only sees one gateway… something must have got jacked in this building during the switch configs. I will need to contact our state guy that handles these. I will see if I can get info out of them.
-
Quick update, I have tested at the building where the FOG and DHCP server reside. the 390s there work just fine. I’m assuming the DHCP server grabs the request before the AP’s get a chance to. On the other hand, we took a 390 to a remote site where AP’s need to relay to the DHCP server. Having the exact same issue as my building. It seems the AP is passing the DHCP correctly, but it cannot do theTFTP, which is where the timeout is occurring.
This is going to be a fun one. I will try to keep it updating as I find out new information regarding the Realtek nics and Aerohive APs.
-
@adukes40 Can you explain a bit more about your network? Why are AP’s handing out DHCP addresses? Are you using consumer APs in your network?
A pcap will tell you a bit more about what is going on. I can tell you we had issues (many moons ago) with 780 and 790 with spanning tree enabled on the building switch (with and old netgear switch). We finally found that we needed to enable fast spanning tree on the switch port. Actually the device was not getting a dhcp address during pxe boot, but via windows it was working fine. Not saying that this is your case here, but you might want to ensure that its not a spanning tree issue either. Placing an unmanaged switch between the computer and the building switch is a quick test to see if its a spanning tree issue.
-
They are supposed to handle the wireless clients getting DHCP. We have one DHCP server, the APs relay DHCP requests to the server. This is in all buildings. Its really just odd that its Realtek acting this way. All the Intel nics do not act the same way, and none of them have this issue. Plus these AP’s were not in this building until December, which is why they imaged this summer just fine.
So they aren’t actually handing out addresses, they are just relaying it. Not sure why a wired client is trying to relay thru the AP. and why only Realtek. (thankfully we only have a handful of these)
-
Just as an FYI, we had to remove the DHCP relays on the AP’s. As the switches were apparently handling the relays anyway, the ones on the AP’s were not needed.
