Solved Enter FTP Server issue

[bigchief]

Morning,

We had an issue with our domain controller and ended up rebuilding it a few weeks ago. It also is our DHCP server.
Ever since then, when I do any network boot to FOG, it always makes me type our FOG server IP address.

I checked to make sure I don’t have 2 DHCP servers already and wireshark is showing only 1.
What else can I check?

[bigchief]

@wayne-workman Just noticed I put those settings on a different scope.

Everything is working now.

Thanks!

[Wayne Workman]

@bigchief said in Enter FTP Server issue:

I just made the change, do you think it will work after a bit? It’s been about 15 minutes since I changed it and it’s still not working.

It should immediately work. Windows DHCP settings take effect immediately.
If you want to share a packet capture from when you are trying to network boot a computer and post it here (or email it to me or a @moderators), we will quickly be able to identify exactly what’s wrong on your network. If you do this, try to keep the recording window of the capture as small as possible. I.E. start recording when you turn on the computer, stop recording after it asks for an IP.

[bigchief]

@wayne-workman When our DC went down we decided to setup a backup DHCP server.
I just check its settings and it was not setup with 66 and 67.

I just made the change, do you think it will work after a bit? It’s been about 15 minutes since I changed it and it’s still not working.

[Wayne Workman]

@bigchief said in Enter FTP Server issue:

when I do any network boot to FOG, it always makes me type our FOG server IP address.
I checked to make sure I don’t have 2 DHCP servers already and wireshark is showing only 1.

I’d say check again because that has only ever happened when there are two DHCP servers on the same broadcast domain (and the two also don’t agree on options 66 and 67, typically the rogue one simply not having them). I can probably find a dozen threads where this has been the cause of the problem you describe.

@dclark If DHCP options 66 and 67 were not set on at least one DHCP server, network booting wouldn’t even happen.

[dclark]

Have you set options 66 and 67 on your new DHCP server (assuming Windows)

https://wiki.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG#Windows_Server_DHCP