Posts made by Eazis

@george1421 Ok thanks for your reply. In the past i already did some research and found the arch 7 flags.

I will check out the uuid and come back with results. Thanks.

I have already a long time a problem with my DHCP on all clients (EEETop ASUS ASUSPRO A41GAR) .

My DHCP config is this:

class "UEFI-64-1" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
   #filename "ipxe.efi";
   filename "snponly.efi";
}

The system EEETop ASUS ASUSPRO A41GART needs to use snponly.efi and the system EEETop ASUS E1600WK needs to use ipxe.efi.
All the other system can also use ipxe.efi.

I have also tried other efi files but there is not any file which works for all the system.

When this happens my collegue ask me to change the dhcp settings and restarting the dhcp service, but when i’m a day off they have problem to image such system who needs snponly.efi

How can i solve this problem?

@Tom-Elliott Yes this resolves the issue.

@kamburta said in LDAP plugin:

PHP Fatal error: Uncaught TypeError: ldap_unbind(): Argument #1 ($ldap) must be of type resource, null given in

ldap is enabled in php.

I have the same problem when installing the same version.
Did anyone resolve this issue?

@tom-elliott Many thanks!! I used now the internal ip address of the AD server … This was the whole problem.
A vaild domain name here did not work.

Normally this AD server is reachable with this fqdn YYYY.XXXX.com (it’s not the real domain). I can’t type public this domain here for security reasons.

I can now login with users from my AD into FOG.

Anyone who can help me with this?

@astrugatch Yes, i tried this, but no result…

@astrugatch

@george1421 sorry for my delay. Weekend between…

TechnischeDienst is a OU.
My AD browser is already in advanced mode. What you mean with the FOG admin group??

@george1421 I tried it with both settings but no luck…

@george1421 So you say:

Search Base DN: DC=YYYY,DC=XXXX,DC=com
Group Search DN: DC=YYYY,DC=XXXX,DC=com
Admin Group: TechnischeDienst

Is this correct?

I’m trying to make everything in our business work with LDAP. The last thing that not will work is FOG.
At the moment i’m pretty new with LDAP but so far all our other applications works fine.
I have read and tried all the information here on the forums but it won’t work at all.
The next two articels on this forum where one of the guides which i tried. For sure i do something wrong, but i don’t what and in the logging there is nothing that i can relate to solve this.

https://forums.fogproject.org/topic/11531/how-to-setup-microsoft-ad-ldap-for-fog-1-5-0
https://forums.fogproject.org/topic/14178/ldap-plugin-install

I have installed php-ldap.

OS: CentOS 7
PHP: 7.4.33
FOG Version: 1.5.9.204

The following settings are no set for LDAP:

Can anyone help me to get this work? Or give me any advice?

@Sebastian-Roth we have just tried some multicast sessions and it looks like that everything is working well now.

@Sebastian-Roth i will try this and i come back if this fix the solution. It could take some days.

@Sebastian-Roth

I’m starting the multicast session in this way:

• Create a group or use an exsisting group
• Add the members to the group (most of the time 10 members are in this group)
• Add a group image to this group
• Add snapins to this group
• Basic tasks -> Multicast

Hello,

First of all, FOG is very nice tool and i already have more then 1500 hosts in the listing.

But now I have a problem with the multicast session after i updated FOG to 1.5.8
The problem is when a multicast session is ended the udp-sender still exsist and there is still a record in the database from this session.
When i start next time a multicast session with other clients the session won’t start at all. I need to clear the database, kill the upd sender and need to restart the FOGMulticastManager and then i need to restart the multicast session and all clients in the group should be restarted.

mysql -u root <-p password> fog
truncate table multicastSessions;
truncate table multicastSessionsAssoc;
exit;

sudo service FOGMulticastManager stop
sudo killall udp-sender
sudo killall udp-sender
sudo killall udp-sender
sudo service FOGMulticastManager start

I’m out of any suggestions to try. Is there anything that i can try?

Thanks in advance!

Sorry for the delay. I had some other problems to resolve.

Now the ASUS (EEE family) A4110 can boot from the PXE network. But i still have some clients with UEFI that can’t boot.
They have the following error:

Server IP address is 10.54.68.102
NBP filename is ipxe.efiÿ
NBP filesize is 0 Bytes
PXE-E23: Client recieved TFTP error from server

It looks like that this ÿ is wrong. Any suggestions to resolve this? I have included tcpdump on the following link.
http://www.eazis.com/output.pcap

Many thanks.

@george1421

There is no hardware issue, because if i rule out the workstation to the imaging network it boot into iPXE with UEFI

@george1421

Yes indeed.
That’s the strange thing…it don’t boot into iPXE
If i do the following command on the “client network” in Windows it download succesfully the file

F:\>tftp -i 10.54.68.102 GET ipxe.efi
Transfer successful: 994176 bytes in 1 second(s), 994176 bytes/s