Posts made by plegrand

@Tom-Elliott i upgraded to 4059 but i cant join domain, there is no more error message in apache error.log
do i have to use domain\user ?

@Uncle-Frank Thanks a lot for your answer, for the moment i use a “classic” password and it works fine.
This morning it didnt works anymore with a classic password. If i understand i’ve got upgrade svn and it will work again?
Thanks again

@Jbob after installing the latest framework (4)
it works

New problem with the last svn version to join samba domain i’ve got this error message in fog.log file :
The specified domain either does not exist or could not be contacted , code = 1355

And this in the apache error log :
PHP Warning: strpos(): needle is not a string or an integer in /var/www/fog/lib/client/HostnameChanger.class.php on line 12

I use an admin password without special characters, and it works manually

Thanks for your help

@ch3i Hello
to explain my problem :
cf schema here : http://plegrand1.free.fr/fog.png

I’ve got 2 servers
My own dhcp-tftp server named " PXE "
the dhcp server is configured like that
next-server 192.168.151.247;
filename “pxelinux.0”;
where 192.168.151.247 is PXE server address

And the fog server named " FOG "

I want to keep for the moment my own PXE server
Then FOG is configured to not act as a dhcp server

All my client boot pxe on my PXE server without problem.

To use fog and boot pxe, i done the following
copy the ipxe.krn file from /tftpboot of the fOG server to the /var/lib/tftpboot of the PXE server
Add configuration on the PXE server (tftp) :
KERNEL fog/ipxe.krn dhcp && chain http://192.168.39.243/fog/service/ipxe/boot.php?mac=${net0/mac}

i made a test with a first machine everything works fine :
the client first arrive of the menu of my PXE server
I choose the fog option
then the client arrive on the menu of the FOG server
i choose any option and it works

i made a test with a second machine :
the client first arrive of the menu of my PXE server
I choose the fog option
then the client arrive on the menu of the FOG server
i choose any option
and then it loop on the message : “sending discover”

these first tests was made with the latest svn version of FOG, but the ipx.krn file came from the stable version of fog (1.2)
then i made the test again with the latest ipxe.krn from the svn version
then nothing works :
tftp://192.168.39.243/default.ipxe… no such file or directory (http://ipxe.org/2d12603b)

and finally i made a test with the ipxe.krn file downloaded from ipxe.org and … it works !!!

To be honest i dont know what is the problem
may be somebody could explain me ??

@cml Have you got an idea about the way to make works my installation ?

i dont understand everythong but thanks

@Wayne-Workman as i said before it’s the new client
I can install the legacy

On a windows xp sp3 i cant install the “New FOG Client Service”. It finish with this error message :
Fog service setup wizard ended prematurely.
I’ve got the log of installation made with :
msiexec /i fogservice.msi /L*V “install.log”
may be i can paste it somewhere ?

Thanks for your help

It works if i dont use my own pxe, only my own dhcp server
then i think my configuration to use my own pxe server is no good.
But i cant find a way to configure it

@cml Hello,
in first i explain my configuration.

We’ve got our own PXE server (dhcp, tftp, pxe on linux server) configured like that

DHCP :
next-server 192.168.39.247;
filename “pxelinux.0”;
192.168.39.247 is the address of the dhcp server itself

TFTP :
i copy ipxe.krn /var/lib/tftpboot/fog directory and
i add to my pxelinux conf this line :
LABEL FOG_ETUDIANTS
MENU LABEL Clonage de postes avec FOG pour les postes ETUDIANTS
KERNEL fog/ipxe.krn
APPEND dhcp && chain http://192.168.39.243/fog/service/ipxe/boot.php?mac=${net0/mac}
192.168.39.243 is the address of the fog server.
Then we dont use the dhcp of the fog server.
After that everything i test on a client windows works fine.

Then i try on other client windows :
NEC ML470 with this network card : 82566DM-2 : FAILED ( “sending discover” loop)
DELL OPTIPLEX 760 with this network card : 82567LM-3 : FAILED ( “sending discover” loop)

During the pxe boot, the client get an ip address from our dhcp server, it seems that it loose this address after.
I try resetting the BIOS default without success
I upgraded bios without success
What do you mean by " What switching do you use? "

Thanks for your help

Hello,

I’m using fog svn 4050 and i’ve no problem with other machine

I’ve got a problem with an old machine that i try to inventory or capture…
It’s a NEC ML470 with only this network card : 82566DM-2

Each time i try to boot on PXE i’ve got, in first, this error message : “bios bug #0[00000031]” found
and the after that i’ve got this loop message “sending discover”
I cant understand what happen

On the same machine (windows xp) i cant install the new client
Installation works fine but at the end without error message nothing is installed in program file

Someone to help me ?

Thanks

@Tom-Elliott Hello, Is it planned to correct the problem concerning specials characters in the domain administrator password ? Or do i have to use a password without special characters ?

I’ve got another little problem, on the host page : i’ve got “No response” with an exclamation point in a red circle as fog didnt see the host .
Nevertheless i can see the host add snapins etc…
Thanks for your help

For informations, for each tests i make on fog (installation, download, upload, samba domain, snapins…), i write a little (french) procedure, are you interested by that ?
Thanks again

@Tom-Elliott As i said just before it seems that the problem come from an apostrophe into the domain administrator password, it works if i use an other domain admin test without apostrophe .
Is it a bug ?

@Tom-Elliott
Here is what i’ve donne

cd /home
mkdir svn
cd svn
svn checkout https://svn.code.sf.net/p/freeghost/code/trunk
at the end i’ve got this information : Révision 4048 extraite.
cd /home/svn/trunk/bin
./installfog.sh

At the end of installation i’ve got this message :
You still need to install/update your database schema.
This can be done by opening a web browser and going to:

  http://192.168.39.243/fog/management

Press [Enter] key when database is updated/installed.

On the serveur fog is installed in /var/fog

I go on the web page, and in the cloud : 4738

To update (run svn up) i’ve got to go into /home/svn/trunk then ?

For the snapins problem it works fine

Just in the hosts list, for my machine test, i’ve got “No response” with an exclamtion point in a red circle
as fog didnt see the host .
Nevertheless i can see the host add snapins etc…

Then thanks again for your help and for this great application

@Tom-Elliott i’m going to make a new install with the good path and i come back to tell you.
But i’ve got the same problem than robza about loop reboot with snapins task

@robza Same problem here
In fact i havent same version … idont really understand versionning
when i do svn up it says 4044
And on fog, in the cloud at the top of the page it says 4700

@ch3i YESSSS it works with a password without apostrophe
May be it could be possible to correct the client to make possible the utilization of specials characters in the password ?

Thanks for your help

@Tom-Elliott Is it possible that the problem comes from an apostrophe in the password of the Samba domain administrator?

@Tom-Elliott
To summarize i use a trunk version of fog : In th e litle cloud at the top of the page : 4700
I use the “new client”
I’m sure of my user wich is able to join windows client into samba domain.
I can join my windows machine test manually and with powershell script
On the “Active Directory” Host configuration i dont use the “Domain Password Legacy” field only the “Domain Password”.
Here is how i do :
Join Domain after image task “checked”
Domain name “samba_domain”
Organizational Unit “blanck”
Domain Username administrateur
Domain Password : contain this " ’ "
i’ve got this error message :
HostnameChanger Logon failure: unknown username or bad password, code = 1326

I didnt configure anything else on fog server

Thanks for your help

@Tom-Elliott sorry i made some tests with the legacy client and some with the new one.
Actually i try with the new client