Posts made by Wolfbane8653

Rename your old unionly.kpxe and attempt this undionly.kpxe file. Before you downgrade.
[CODE]wget -O /tftpboot/undionly.kpxe https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/CODE]

undionly.kpxe–r1312 --> GOLD STAR!..at least on all my machines

FOR ME I get these results with undionly_ROM.kpxe

Attempt(s) ==> Configuring (net0 xx:xx:xx:xx) …

After: Initializing …ok ==> different machines show a bit of a different output

Dell D610’s, Dell D630’s, HP DC5700’s read:
Waiting for linkup …ok
Configuring (net0 xx:xx:xx:xx) …

Dell E6410’s and HP DC7800 read:
Configuring (net0 xx:xx:xx:xx) …

[B]Round 1: (1st boot)[/B]
VM --> over 20 attempt(s) didn’t get to the “Fog Menu”
Dell D610 --> 1 attempt(s) to get to “Fog Menu”
Dell D630 --> 2 attempt(s) to get to “Fog Menu”
Dell E6410 --> 1 attempt(s) to get to “Fog Menu”
HP DC5700 --> 1 attempt(s) to get to “Fog Menu”
HP DC7800 --> 1 attempt(s) to get to “Fog Menu”

[B]Round 2: (2nd boot)[/B]
VM --> over 20 attempt(s) didn’t get to the “Fog Menu”
Dell D610 --> 3 attempt(s) to get to “Fog Menu”
Dell D630 --> 1 attempt(s) to get to “Fog Menu”
Dell E6410 --> 7 attempt(s) to get to “Fog Menu”
HP DC5700 --> 1 attempt(s) to get to “Fog Menu”
HP DC7800 --> 5 attempt(s) to get to “Fog Menu”

Hmmm…so I downloaded the undionly.kpxe directly from ipxe.org and threw it up on my /tftpboot folder. Renamed it to wolf.kpxe and changed my dhcp 67 to wolf.kpxe. I embedded nothing. Guess what error message I get for most of my machines?

0x040ee119

So there is nothing wrong with your embeded scripts! its all ipxe

The infamous pxelinux.0 may need to come out of retirement.

Can you upload an image and then reupload on top of it? The case being to update the original image? or is that still untested.

[B]–Add the revision version to node=about[/B]
[CODE]Version: 1.0.1-rXXXX[/CODE]

[B]–Add Apache2 error log under Fog Log Viewer and anything else that would be needed for debugging.[/B]

Under create host you don’t need to add the OS just the image. The image has the OS information in it.

[quote=“Tyler Coles, post: 27188, member: 24184”]Hey, Tom. Just wanted to let you know that this DID fix the issue for me. The error appears a couple of times but doesn’t immediately boot me out. I guess the dhcp process now has time to finish and the computers are booting. Nice work![/quote]

With the 0x040ee119 error looping until the iPXE gets a renewed address is not a good fix. Now if you line up 30 computers at once it will be random on which comes up first, instead of guaranteeing on first try.

I had sometime to test on a lab…yes 30 computers at once. I rebooted them all at once (Deepfreeze ) and I watched them closely. It was to the point that each computer would randomly get to the “Fog Menu”. Sometimes on the first try for iPXE sometimes on maybe the 7th. I had two that just finally looped until almost 20 times, then I shut them down myself and rebooted. Then these last two got to the “FOG Menu” on the first try. This was not an issue with pxelinux.0, nor with undionly.kpxe for fog 0.33b but in the upgrade to 1.0.0 and 1.0.1 this issue continues. This is on both physical Desktops/laptops and VM’s.[I] I’m leaning towards and environmental issue.[/I] Maybe something wrong with my switches or my DHCP. DHCP is handing out addresses on a live network, so don’t ask if its working. Still exploring all possibilities.

FYI:
Cisco switches ENABALE portfast (otherwise PXE/iPXE will not work)
Netgear DISABLE STP (otherwise iPXE will not work)

So you don’t have any rights to login to the DHCP server? …opps someone left the door open or the old credit card tricks are no good? No way you can remote desktop in or ssh?

What are your error messages?

Seeeeeee TOOOOOMMMMMMM"“”"SSSSSSS [I][U][B]signature[/B][/U][/I] and update your kernals this way on Ubuntu machines!

you may need to add [B]sudo[/B] infront of these commands

[QUOTE][SIZE=12px]Have you searched the forums for your issue yet?[/SIZE]
[SIZE=12px]Have you checked the [/SIZE][URL=‘http://fogproject.org/wiki’][SIZE=12px]wiki[/SIZE][/URL][SIZE=12px] yet?[/SIZE]
[SIZE=12px]Kernel Issues: [/SIZE][URL=‘http://fogproject.org/wiki/index.php/FAQ’][SIZE=12px]http://fogproject.org/wiki/index.php/FAQ[/SIZE][/URL][/QUOTE]

Open Terminal or SSH into your fog server…
Then mount the NFS if not done so already.
cd to the mounted folder. In my example it would be /images2
Just do a quick [CODE]sudo nano test.txt[/CODE]. Edit the file type in anything and save.
Then jump on to the windows machine and see if the file exists. Then create a folder using the windows machine.
See if you can see the folder in linux.

[B]If you have any issues with this then there is a security/sharing/permissions setting that is incorrect.[/B]

what happens when you do a:

[CODE]sudo restart tftpd-hpa[/CODE]

???

Attempt here please. [url]http://sourceforge.net/projects/freeghost/files/FOG/fog_1.0.0/[/url]

It seems that you don’t have the rights configured. I also forgot one other security setting in the above post.

[ATTACH=full]756[/ATTACH]

[ATTACH=full]759[/ATTACH]

Make sure you do this for C:\images, and C:\images\dev

I will add for future reference.

[B][SIZE=14px][FONT=sans-serif][COLOR=#252525]Kerberos[/COLOR][/FONT][/SIZE][/B][SIZE=14px][FONT=sans-serif][COLOR=#252525][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English’][COLOR=#0b0080]/[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ˈ[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]k[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ɛər[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]b[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ər[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]ə[/COLOR][/URL][URL=‘http://en.wikipedia.org/wiki/Help:IPA_for_English#Key’][COLOR=#0b0080]s[/COLOR][/URL][URL='http://en.wikipedia.org/wiki/Help:IPA_for_English’][COLOR=#0b0080]/[/COLOR][/URL][/COLOR][/FONT][/SIZE][SIZE=14px][FONT=sans-serif][COLOR=#252525] is a [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Computer_network’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]computer network[/COLOR][/FONT][/SIZE][/URL][URL=‘http://en.wikipedia.org/wiki/Authentication’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]authentication[/COLOR][/FONT][/SIZE][/URL][URL='http://en.wikipedia.org/wiki/Cryptographic_protocol’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]protocol[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525] which works on the basis of ‘tickets’ to allow [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Node_(networking)’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]nodes[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525] communicating over a non-secure network to prove their identity to one another in a secure manner. Its designers aimed it primarily at a [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Client–server’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]client–server[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525] model and it provides [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Mutual_authentication’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]mutual authentication[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525]—both the user and the server verify each other’s identity. Kerberos protocol messages are protected against [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Computer_insecurity#Eavesdropping’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]eavesdropping[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525]and [/COLOR][/FONT][/SIZE][URL=‘http://en.wikipedia.org/wiki/Replay_attack’][SIZE=14px][FONT=sans-serif][COLOR=#0b0080]replay attacks[/COLOR][/FONT][/SIZE][/URL][SIZE=14px][FONT=sans-serif][COLOR=#252525].[/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=sans-serif][COLOR=#252525]~[URL=‘http://en.wikipedia.org/wiki/Kerberos_(protocol)’]Wiki[/URL][/COLOR][/FONT][/SIZE]

[url=“/_imported_xf_attachments/0/756_Security 2.png?:”]Security 2.png[/url][url=“/_imported_xf_attachments/0/759_Security 2.png?:”]Security 2.png[/url]

Good morning!

Unfortunately its not a good morning for the new update for fog.

[QUOTE]Configuring (net0 xx:xx:xx:xx:xx:xx)… Error 0x040ee119[/QUOTE]

The new update intermittently works on the VM and a Dell D610. The VM was working well enough in the evening but this morning I can only get it to boot to fog about 1/8 times. BUT this is[B] greatly improved from yesterday[/B] being 1/30+.

The first way is to download it off Tom’s page: [url]https://mastacontrola.com/downloads.html[/url]

The second way is to follow instructions on this posting: [url]http://fogproject.org/forum/threads/keep-up-to-date-with-all-the-fog-0-33-updates.10300/[/url]

Shhhh…Left the password blank. I only use this machine for Fog.
[CODE]
/*

• DATABASE VARIABLES

• ---

*/

define(‘DATABASE_TYPE’, ‘mysql’); // mysql or oracle
define(‘DATABASE_HOST’, ‘localhost’);
define(‘DATABASE_NAME’, ‘fog’);
define(‘DATABASE_USERNAME’, ‘root’);
define(‘DATABASE_PASSWORD’, ‘’);
[/CODE]

BUT it is working on a VM, so I’m leaning towards it will work in the morning.

LOL Couldn’t wait!

[ATTACH=full]750[/ATTACH]

File does however exist!

[CODE]fog@fog-Latitude-D630:/$ locate boot.php
/fog-rc/packages/web/service/ipxe/boot.php
[B]/var/www/fog/service/ipxe/boot.php[/B][/CODE]

This occurred on first boot after update. Then next the 0x040ee119 error. Then it booted to the bzImage 5 times after that. SO for giggles I deleted the Lease from the DHCP server for that IP and it still worked after that.

This was perform on a VM, so I will test physical HW in the morning! Can’t wait!
Thanks Tom!!!

[url=“/_imported_xf_attachments/0/750_boot_php.png?:”]boot_php.png[/url]

Updating in the morning and will report back asap!