@Tom-Elliott

The IP the machine is getting both in PXE and when selecting any menu option is 192.168.91.242… within the specified range for that vlan. FOG server is on 192.168.91.243. No, the nic is an onboard broadcom nic on a dell optiplex 580

@Tom-Elliott said in No DHCP response (Multiple VLAN setup):

55.255.255.192

It is supposed to be .192. This is also reflected on the fog server as well as all DHCP clients on that vlan.

@Tom-Elliott said in No DHCP response (Multiple VLAN setup):

the host machine when it’s in PXE mode, but in the FOS System, it’s unable to communicate to the Client Machine anymore. This leads me to think it’s getting an IP Address that can’t route anywhere.

Its getting the same IP in PXE mode as it is when I select the option to register host. They exact same IP. Which is in the same vlan as the fog server… they are actually only 1 IP apart. I can have a continuous ping going and from the FOG server I can get replies up to the point there I select the register host option. At that point the replies stop. I can then reboot the client and once it start the PXE boot process the pings start replying again… from the same IP. Its really odd… while in PXE it gets DHCP with all the correct information… but once we go anywhere in the Fog menu we lose all connectivity. When running the route command on the client once in debug I see the following:

Destination Gateway Genmask
default 192.168.91.193 0.0.0.0
192.168.91.192 * 255.255.255.192

192.168.91.193 is the correct gateway for this vlan but is unpingable from the client at this point.

@george1421

Understood. I was trying to illustrate that there did not appear to be a communication issue between devices on the vlan in question by stateing that they communicate just fine up to a certain point.

@Tom-Elliott

Based on what I see that would appear to be the case… except I know its not the case. When the system is pxe booting I am able to ping from the fog server to the client. While at the main fog menu I am able to ping from fog server to client. The moment I select full host registration I am no longer able to ping from fog server to client.

@Tom-Elliott

Sorry, I did the second… after doing it the correct way the number 7 was returned.

@Tom-Elliott

I added to the end of the curl command you sent me and it still just drops me back at the command line with no output.

@Tom-Elliott

Yes, valid IP and netmask.

@Tom-Elliott

The command executed. Didn’t generate anything… just ran and nothing. I’m not able to ping from the client to fog server or the other way around. Which is odd because I can ping from the fog serve to every other IP on the VLAN that I’ve attempted.

@Tom-Elliott

Ok, I am sitting at debug windows now… any steps you suggest I perform. ifconfig looks as it should. Its on the same vlan as fog server with correct netmask. No errors, no drops.