Posts made by Junkhacker

just this one [url]http://fogproject.org/forum/threads/fog-0-33b-edit-pxe-menu.10403/#post-26420[/url]

minor correction for tom: each line of the ipxe file is seen as a new command, so the || at the end of a line only meand ‘do this’ “or” ‘nothing’
if ‘do this’ fails, this is a failure to execute a command, if there is a “or” ‘nothing’ then the line is a success, because it successfully does nothing.
each line after a ||
will be executed

there are several versions of the undionly.kpxe file mentioned in that thread. which one did you use? i think the current recomendation is 1312
[FONT=Consolas]wget -O /tftpboot/undionly.kpxe [url]https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/url][/FONT]

this sounds to me like either the DHCP options 66 or 67 are set incorrectly, or the tftp service on the fog server is not running.
your options should be set to your fog server’s ip, and undionly.kpxe

have you tried updating your kernel?

the imaging process does not use the tftp service. the tftp service provides the pxe boot configuration, and that is all. you need to check the ftp service. that password stored in /commons/config.php is not used anymore in 1.0+ versions of fog, and is right under a banner stating as much. if you changed the password in the webgui, you also need to change the password of the fog user. yes, the password in the webgui must match the password set for the user “fog” for both the [FONT=arial][COLOR=#262626]FOG_TFTP_FTP_PASSWORD in fog settings, and [/COLOR][/FONT][FONT=arial][COLOR=#262626]The Storage Management -> NODE -> fog password.[/COLOR][/FONT]
[SIZE=2]is the system [/SIZE]currently[SIZE=2] working for you[/SIZE]

or to test independently of anything fog related, use etherwake. [url]http://manpages.ubuntu.com/manpages/quantal/man8/etherwake.8.html[/url]
i think you will find that if fog fails to do it, so will this. because the problem is not in fog.

does a wol packet sent manually from the server work?

check your fog.log in the c:\ of the client, is it connecting to the server? are there any errors?

fog relies on a DHCP server providing options 66 and 67 (next-server and boot-filename) on DHCP requests. that’s how clients get the information on “what” and “where” the network boot information is. i don’t know of any linksys router that can do that with the stock firmware, so you will most likely need to set up DNSMasq [url]http://www.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]

you will be able to complete the configuration of the server from any computer with a web browser that can communicate with the server. however, the error you’re getting is most likely from the server not having the mySQL password set in the /var/www/fog/commons/config.php file. the web server cannot connect to the database.

do you have a bluetooth device plugged in to this computer?

are there active tasks for this client in the active tasks or the active snapin tasks? if so, please delete them and create a new snapin task, and upload the fog.log again. it may take up to 5 minutes for the client to request the snapin task.

fyi, the fog client software has the ability to join computers to AD by itself.
i have found that plaintext based snapins, like vbs or bat files, must have a space or carriage-return after it’s last character in order for the client to know the file has completed downloading. the file may end up with an added #!OK on it’s last line if it does not have this.
as a test of your snapin system, you can create a .bat file with these contents
[CODE]@echo off
echo “HELLO I INSTALLED SNAPIN1 ON MY SYSTEM” > C:\installedSnapin1.txt
[/CODE]
and add it as a snapin.
this will create a text file in the root of the drive, and verify that snapins are working.

you’ve been using fog for 5 years, right? do you have a custom compiled [FONT=sans-serif][COLOR=#000000]HostnameChange.dll on your images? will this match the passkey used in fogcrypt?[/COLOR][/FONT]

does WOL work if you run it from a different computer on your lan? i suspect the network is the issue, not fog.
you can use this to test [url]http://www.nirsoft.net/utils/wake_on_lan.html[/url]

The upload speed is slow because of compression. in the latest version of fog, the compression is set to 9, previously it was set to 3. i personally set this to 6. this primarily affects uploads, downloads are quite fast. i regularly get speeds downloading in the 3GB range.

well, if you’re looking for “dumb” things that can keep this from working, here’s some mistakes i’ve made in the past…
make sure that “Join Domain after image task” is set, with the proper information, under “Host Management” > “Active Directory”
make sure that the “Hostname Changer” under “Service configuration” setting is enabled under “Service Settings”

the kernel refers to a part of the fog system that is used for creating and deploying images. fog uses a 64bit kernel now, for hosts that support 64bit. this does not require any changes to the hosts being imaged.

unfortunately, the easiest way to do that would probably be directly in the database. fog database, hosts table, hostKernel column, i think
(i use phpMyAdmin for these kinds of tasks, but someone better at command line stuff could probably tell you how to do it with a single command)