• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. KevinDM82
    K
    • Profile
    • Following 1
    • Followers 0
    • Topics 2
    • Posts 8
    • Best 1
    • Controversial 0
    • Groups 0

    KevinDM82

    @KevinDM82

    1
    Reputation
    173
    Profile views
    8
    Posts
    0
    Followers
    1
    Following
    Joined Last Online

    KevinDM82 Unfollow Follow

    Best posts made by KevinDM82

    • RE: Unable to PXE boot on an isolated network

      @george1421 GEORGE THANK YOU SO MUCH!!! YOU HELPED SO MUCH

      posted in FOG Problems
      K
      KevinDM82

    Latest posts made by KevinDM82

    • RE: Unable to PXE boot on an isolated network

      @george1421 GEORGE THANK YOU SO MUCH!!! YOU HELPED SO MUCH

      posted in FOG Problems
      K
      KevinDM82
    • RE: Unable to PXE boot on an isolated network

      @george1421 I checked that conf file and made some adjustments.
      Now the moment of truth. this is current status.

      kevin@ET1WS3239A:~$ ps aux|grep dhcp
      dhcpd 1102 0.0 0.1 35484 13260 ? Ss 22:12 0:00 dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
      kevin 4292 0.0 0.0 14228 928 pts/0 S+ 22:46 0:00 grep --color=auto dhcp

      systemctl status isc-dhcp-server
      ● isc-dhcp-server.service - ISC DHCP IPv4 server
      Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled)
      Active: active (running) since Tue 2017-12-26 22:12:02 CST; 37min ago
      Docs: man:dhcpd(8)
      Main PID: 1102 (dhcpd)
      CGroup: /system.slice/isc-dhcp-server.service
      └─1102 dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.con

      Dec 26 22:12:03 ET1WS3239A dhcpd[1102]: Wrote 0 class decls to leases file.
      Dec 26 22:12:03 ET1WS3239A dhcpd[1102]: Wrote 0 leases to leases file.
      Dec 26 22:12:03 ET1WS3239A dhcpd[1102]: Listening on LPF/eno1/b8:ca:3a:8e:15:14/192.168.1.0/24
      Dec 26 22:12:03 ET1WS3239A sh[1102]: Listening on LPF/eno1/b8:ca:3a:8e:15:14/192.168.1.0/24
      Dec 26 22:12:03 ET1WS3239A sh[1102]: Sending on LPF/eno1/b8:ca:3a:8e:15:14/192.168.1.0/24
      Dec 26 22:12:03 ET1WS3239A sh[1102]: Sending on Socket/fallback/fallback-net
      Dec 26 22:12:03 ET1WS3239A dhcpd[1102]: Sending on LPF/eno1/b8:ca:3a:8e:15:14/192.168.1.0/24
      Dec 26 22:12:03 ET1WS3239A dhcpd[1102]: Sending on Socket/fallback/fallback-net
      Dec 26 22:12:03 ET1WS3239A dhcpd[1102]: Server starting service.
      Dec 26 22:49:23 ET1WS3239A systemd[1]: Started ISC DHCP IPv4 server.

      posted in FOG Problems
      K
      KevinDM82
    • RE: Unable to PXE boot on an isolated network

      @george1421 After checking the status I think this confirmed that what I thought that DHCP just wasn’t operational.

      isc-dhcp-server.service - ISC DHCP IPv4 server
      Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled)
      Active: failed (Result: exit-code) since Tue 2017-12-26 22:02:30 CST; 7s ago
      Docs: man:dhcpd(8)
      Process: 5095 ExecStart=/bin/sh -ec CONFIG_FILE=/etc/dhcp/dhcpd.conf; if [ -f /etc/ltsp/dhcpd.conf ]; then
      Main PID: 5095 (code=exited, status=1/FAILURE)

      Dec 26 22:02:30 ET1WS3239A sh[5095]: Not configured to listen on any interfaces!
      Dec 26 22:02:30 ET1WS3239A sh[5095]: If you think you have received this message due to a bug rather
      Dec 26 22:02:30 ET1WS3239A sh[5095]: than a configuration issue please read the section on submitting
      Dec 26 22:02:30 ET1WS3239A sh[5095]: bugs on either our web page at www.isc.org or in the README file
      Dec 26 22:02:30 ET1WS3239A sh[5095]: before submitting a bug. These pages explain the proper
      Dec 26 22:02:30 ET1WS3239A sh[5095]: process and the information we find helpful for debugging…
      Dec 26 22:02:30 ET1WS3239A sh[5095]: exiting.
      Dec 26 22:02:30 ET1WS3239A systemd[1]: isc-dhcp-server.service: Main process exited, code=exited, status=1/FAILURE
      Dec 26 22:02:30 ET1WS3239A systemd[1]: isc-dhcp-server.service: Unit entered failed state.
      Dec 26 22:02:30 ET1WS3239A systemd[1]: isc-dhcp-server.service: Failed with result ‘exit-code’.

      posted in FOG Problems
      K
      KevinDM82
    • RE: Unable to PXE boot on an isolated network

      @george1421 During installation I choose the option to allow Fog to take care of DHCP, then after completing the install changed the /etc/network/interface file from dhcp to static and changed the address’s accordingly

      posted in FOG Problems
      K
      KevinDM82
    • RE: Unable to PXE boot on an isolated network

      https://drive.google.com/open?id=1685QBOnQZ51n-dMxmGr-jBkfdt-wPwpg

      posted in FOG Problems
      K
      KevinDM82
    • Unable to PXE boot on an isolated network

      I am in the exact same situation cdutko was in at the point where it isn’t booting PXE. How did he go from the netstat verifying port pxe wasn’t bound to port 67 to working? I would appreciate any help.

      Base Linux: Debian
      Detected Linux Distribution: Ubuntu
      Server IP Address: 192.168.1.1
      Server Subnet Mask: 255.255.255.0
      Interface: eno1
      Installation Type: Normal Server
      Internationalization: 0
      Image Storage Location: /images
      Using FOG DHCP: Yes
      DHCP router Address:

      posted in FOG Problems
      K
      KevinDM82