![]() ![]()
I see that the messagesĪre originating from 10.216.127.3. ![]() The DHCP Discover messages are being received on the DHCP server. When I started testing with devices in the remote subnet (10.216.127.0/24) things are not working as expected. Also an address leaseīecomes visible for the authorized device. #Open mesh wired client never receives dhcp offer macWhen I authorize the MAC address of one of these devices, immediately an IP address is being handed out to this device and the DHCP Statistics are being incremented: 1 Offer, 1 Request, 1 Acks. The dropping of these messages is visible in the DHCP Server event log and also in the DHCP Statistics as these messagesĪre counted in DHCP "Discovers". ![]() So the Discover messages are basically ignored by the DHCP server. Messages up I think because both NIC's are connected to the same VLAN (1323) and there is an active scope for 192.168.11.0/24 so the DHCP can hand out IP adresses via the NIC with IP number: 192.168.1.1.Īll these devices are not authorized in the DHCP (MAC) filter defined. The DHCP Discover messages from these devices are received by the server and visible in Wireshark. There are some clients in this network with network cards that have "Obtain an IP address automatically" configured. Based on this test I concluded: DHCP/WDS server basic setup is working.Īfter this successful step I started testing with the main network number 2. DHCP DORA flow is completely visible with Wireshark on the DHCP/WDS Server VM. Client receives IP address and is able to do a PXE boot. When I PXE boot a client VM in the first networkĮverything works as expected. Network one only exists at the moment to verify if the DHCP server could hand out IP addresses to "local" devices. In DHCP two active scopes have been setup for network 1 & 3. The DHCP server has the following IP addresses in the two above networks: A DHCP Relay agent has been setup on the network device that is used for the routed connection between network 2 & 3. It has an routed connection to another (third) network (10.216.127.0/24) in which the clients are located that should get an IP address from the DHCP server in the first The first network is only a dhcp test network. The two networks are using the following IP For both of these networks in VMM, IP Pools have been created but the IP ranges in the pool have been completely excluded from IP assignments by VMM. The VM has two NIC's which areĬonnected via a VMM logical switch to two networks (subnets). #Open mesh wired client never receives dhcp offer windowsNext to the DHCP role also the Windows Deployment Services role is deployed on this server because it will have to provide PXE boot services. The DHCP server is setup on a VM running on a Windows Server 2012 R2 Hyper-V host. I have an issue with a DHCP server that is not responding to "some" DHCP Discover messages that it receives. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |