@jamcdonald120 said:

if we assume that the DHCP setting of the router are correct (they worked before) …

I am sure I have heard phrases like this more than a hundred times and it quite often turns out …

Asking the web to see what other things could cause this issue I see that the error message you posted is not quite the same most other people report - which is: PXE-E53: No boot Filename received (see the difference between ‘File’ and ‘Filename’?). Your positive test of trying to load the undionly.kpxe (how do you know your server is using this file and not ipxe.kpxe which we also use sometimes?) binary file makes me believe that your TFTP and the files on it are fine. This would emphasize even more that something is wrong with the DHCP! The message essentially says: “I got an answer from a DHCP server but no information on what file to load for PXE booting”.

You need to understand that DHCP is always a bit of an issue. This is because even if neither you nor any colleague changed the “original” DHCP server you can still run into problems if someone added another DHCP server answering requests in your network.

Please try this: Make one of your clients ready for turn on and PXE boot. Install and run tcpdump - a tool to capture network traffic - on your FOG server.

sudo -i apt-get install tcpdump tcpdump -w /tmp/dhcp_traffic.pcap port 67 or port 68 or port 69 or port 4111

Leave that command as is and start up the client till you see the error message on screen. Then stop the tcpdump command (Ctrl-c) and upload that packet dump file (/tmp/dhcp_traffic.pcap) from your server to the forum here.

@rbasart Well, that certainly could do it I suppose.

As far as it “partially” working, the switch IS the IP address, and FOG had “listeners” on that IP.

As the switch received the data, the FOG Server would perk up as well.

Glad you figured it out for sure there. Sorry I didn’t recognize this, but hey one more thing to “look” for.

how i mark solved?

Sounds like your hdd might be full. You can check with df -h look for partitions with 99% or 100% use.

In addition to what Jaymes asked below, also look through your apache error logs.

@craigcoulson said in Debian + svn = error:

nevermind all - i rebuilt the server with only minimal packages and re-ran the svn install of Fog and it worked fine - go figure.

Glad to hear you got it working 😉

@Tom-Elliott This, this is why we love you.

@dloudon96 Is 10.31.97.240 your fog server’s address? What OS is the fog server running? What version of FOG?

@RobTitian16 Thank you for your reply.

Did you build your Windows 10 image from scratch or are you using a modified version of the pre-installed os?

You could try wiping the drive of all partitions, adding a blank one and imaging again. We have had trouble with partitions on the disk that were put there as a factory recovery point. (I know Dell, HP, etc are known for having a recovery partition).

@psyfer9983 After changing the OS’s addressing & dns and gateway and such, the tool in here called updateIP will change all the needed spots for FOG’s files. https://github.com/FOGProject/fog-community-scripts

It will also re-write dhcpd.conf properly if the box is configured to do dhcp - and will do so correctly even for up to 4 interfaces on one system.

@MotD If you’re trying to set a password you can do it right from the installer with:

snmysqlpass='SomePasswordHere' ./installfog.sh -y

@Wayne-Workman Good point. Thanks for your help

@taflad said in TFTP service - Unit Not Found:

, I tried to restart the tftp servic.e However, I get “failed to start tftp.service: unit not found”

The service should be called xinetd and not tftp.

Also this might help:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

@Tom-Elliott
Thank you so much let you know once im done with it

See my post here: https://forums.fogproject.org/topic/9437/upgrading-fog-on-a-standalone-network

@Ric41 What other services appear? What’s OK?

@butch2861 said in Fresh install Ubuntu 16.04.1 Fog 1.3.4 Error:

The problem above is on the CLIENT end, not there server…server is okay from what I can tell

The server wasn’t OK at the time I posted what I did, it was out of space. This was not a fresh install of Ubuntu 16 /w fog if you were already out of space. The title of this thread should be changed.

@Sebastian-Roth - it is - ill start a different thread tho as it doesnt look the same to you
0_1486081090166_fog_error.JPG

@george1421 Yeah, maybe that was it - just a cold boot after the BIOS update to 'bed things in". Like I said, I was stunned to see the NUC suddenly behaving, so I went back in to BIOS and undid my changes to confirm if that was the cause - still boots w/o issue.

I recall there being a Wiki page somewhere listing hardware that is known-to-work with FOG. Would be good to update that with this information. Not sure if this account has permissions to update…otherwise I’ll create a new one.

@FallingWax Good to hear.