@Tom-Elliott said:

Linux is not windows. Change this hosts kernel device to either blank or the real device in linux.

How did you know?

@Tune389 said:

@ch3i okay thanks for the info. I try now to downgrade my fog version back to 1.2 …

That’s not supported nor advised…
To “downgrade” requires either restoring a previous snapshot (via a virtual machine) or rebuilding your FOG server from scratch…

You are exactly right. The fog server was not authenticated to the firewall. I’ll need to add a rule to automatically let it out.

Thanks!

Can you run the troubleshooting script found here: https://forums.fogproject.org/topic/4581/let-s-make-scripts

And see if it points anything out?

Run updates on the main server and nodes, make them all match.

[CODE]apt-get update
apt-get upgrade[/CODE]

Ensure FTP functions correctly on your nodes.

Also, it sounds like you’re using the location plugin ??
Ensure the locations are set properly. Reset them if you need.

https://www.bootix.com/support/problems_solutions/pxe_e51_no_dhcp_or_proxydhcp_offers_were_received.html

E51 means the system is not getting DHCP

@tvigneau 😄

You have to create the node on the gui

@TheKoR said:

Up to 3480 : no problem anymore

Wild.

@Alex-Grier we have multiple sites across the UK utilizing the Multiple TFTP servers, Location Plugin (where you can also specify that the node is TFTP if you do not want to use multiple tftp servers) and imaging is as quick on remote sites as it is local (since Junkhackers speed increases - 1GB LAN 14.68gb/min averaging out at 8.58gb/min!!) and images sync pretty quick thanks to Tom’s awesome addition to the replication allowing multiple streams and you can also control the bandwidth by adding bandwidth limits.

files in Linux that begin with a period are hidden.

ls lists files.
-a includes hidden files.
-l shows permissions and ownership.
-R is the recursive flag.

So this command would show every single file in /images and it’s sub-directories:
[CODE]ls -laR /images[/CODE]

You could pipe that with grep, which is a powerful searching tool and just search for .mntcheck

[CODE]ls -laR /images | grep .mntcheck[/CODE]
That will only show all instances of .mntcheck inside the /images directory.

There should be two.

I’d recommend (just for the purposes of troubleshooting) these things:

Default OU blank
use your domain Administrator as the default user
Administrator password

then, I’d play with the domain name…
Try your FQDN (fully qualified domain name)
Try your sloppy domain name (example for My.SchoolDistrict.k12.mo.us you’d just put in “My”)

No need to change any php files. This is FOG Trunk, the days of editing PHP files are over.

The rest of your settings look good.

Now, if none of this works… keep in mind that this client is in BETA. If you want to pursue this further, please contact @Jbob

Does your legacy client work?

Solved as the Apache error is corrected for in latest svn.

@Jeroen-Brussich said:

Let’s bump an old topic 🙂

Do I have to tag my FOGserver in all VLANS in order to get this plugin working?
And configure all VLANS on my FOGserver?

/etc/network/interfaces eth0.1 (default vlan) eth0.100 (vlan 100) eth0.1000 (vlan 1000)

No.

The WOLBroadcast plugin just needs your networks broadcast addresses specified. Once specified, you will likely need udp-directed-broadcast enabled on your switches. After that, fog will send WOL packet to each of the broadcast addresses.

This may have to do with another issue i am having…
https://forums.fogproject.org/topic/5068/unable-to-connect-to-storage-node-with-ver-1-2-0

Ah ok! Maybe this is default behaviour now? Tom will probably weigh in soon.

I’ll upgrade to SVN later and see what happens myself.

@Trevelyan Yes, I just restarted it to test, and it came right back up and I was able to login. So it looks good so far! Thanks for trying to help so much btw, I really appreciate it.

There might be relevant parts in that article, but it was last updated in 2011.

I should re-write it… I’ll put it on my to-do list (I actually have a to-do list here).

If you can get another HDD in, format it, mount it, etc, you could simply add a new storage node and point the path to your new HDD. Set your permissions on that new directory as 777 and it ought to work.

Firstly, please check back to this thread because a developer might provide a solution.

So, normally, when a client “exits” from the FOG PXE environment (when it sees that there are no tasks waiting for it), it can hand off control to the local system in three different styles, all of which assume booting from the local HDD.

See picture:

ExitToHardDriveType.png

Somehow, one of those (or add a new one?) will need to be modified to detect if said system needs to boot to the HDD or to the network. Because currently all of those point to the local HDD.

Chainloading to the appropriate boot-file will be involved for the systems that need to boot to network.

The Advanced Configuration Options will likely need to be used to accomplish this:

advancedconfigoptions.png

I’m not sure how that’d be accomplished.

@techpromise said:

Thanks for the help guys, I decided to manually add the images back in as the SQL dump carried over some errors from the old system.

How do I mark this as solved?

Ask us and we will oblige.