Friday, March 30, 2018

DHCP Issue stumping me

Hello friends,

I have been working with a colleague to try and figure out this issue but have run into some confusion which will probably seem completely academic to you.

We have a device in question which is a hardware controller (http://www.wiznet.io/product-item/wiz550io) . This controller is set to allow for dhcp, and has a default IP of 192.168.1.2.

In our main office, which has DHCP running on a windows 2012r2 server, it is able to connect properly and go through the standard handshake process.

When I take the same device to our other office down the street, which has DHCP running off of our firewall (fortigate 60e) it fails. port mirroring and wireshark shows the device constantly sending out the discovery broadcast but never receiving a response. Other devices can get addresses just fine on this same port.

The wireshark capture shows that the source is the 192.168.1.2 (default address) and destination is the broadcast domain 255.255.255.255. I wagered that this was probably the issue but was stumped by how it was then able to work in our other location with a Windows DHCP server. note that we do not have a 192.168.1.0/x subnet in either location.

Before submitting this post, my colleague confirmed that once he set the default ip to 0.0.0.0 it was able to successfully obtain an address in our remote office



No comments:

Post a Comment