Hey Ed,
Am 07.02.24 um 20:39 schrieb Ed Hammond via PacketFence-users:
I have tried installing both the ISO and Zen versions of PacketFence 13.1 and I
keep getting this error in the packetfence.log when I try to connect to Active
Directory:
Feb 7 17:53:11 packetfence pfperl-api-docker-wrapper[1360]: pfperl-api(12)
WARN: [mac:[undef]] Problem trying to run command: LANG=C
/usr/local/pf/bin/impacket-addcomputer
I checked the bin folder and I do not have impacket-addcomputer
Is this a bug?
I ran into the same problem after the upgrade from 12.x to 13.1.
The way this works is very misleading in my opinion:
/usr/local/pf/containers/pfperl-api/Dockerfile contains a command to
symlink /usr/share/doc/python3-impacket/examples/addcomputer.py to the
location you're looking at: /usr/local/pf/bin/impacket-addcomputer
Therefor to find out what impacket-addcomputer looks like you need to
look at /usr/share/doc/python3-impacket/examples/addcomputer.py .
To find the environment where the script is started you can look inside
the container pfperl-api:
```
root@pf-demo:~# docker exec -ti pfperl-api /bin/bash
root@pf-demo:/usr/local/pf# ls bin/impacket-addcomputer
bin/impacket-addcomputer
root@pf-demo:/usr/local/pf# exit
exit
```
In my case I ended up finding that in my lab environment my DNS didn't
answer with the right IP-Address for my DC.
Chris
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
