• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. TTellez
    3. Posts
    T
    • Profile
    • Following 0
    • Followers 0
    • Topics 13
    • Posts 86
    • Best 4
    • Controversial 0
    • Groups 0

    Posts made by TTellez

    • RE: Had to hard code ENET adapter, now I can't update because I can't get an internet connection

      @Tom-Elliott So I literally just
      ifconfig eth0:0 123.123.22.22
      then when I am done

      # ifconfig eth0:0 down
      

      And my original connection stays as is?

      posted in Hardware Compatibility
      T
      TTellez
    • RE: Had to hard code ENET adapter, now I can't update because I can't get an internet connection

      @Tom-Elliott gotcha. Ill try it with my remedial linux skills. LOL.

      posted in Hardware Compatibility
      T
      TTellez
    • RE: Had to hard code ENET adapter, now I can't update because I can't get an internet connection

      @Sebastian-Roth 1_1500479637091_image2.JPG 0_1500479637091_image1.JPG

      posted in Hardware Compatibility
      T
      TTellez
    • RE: Had to hard code ENET adapter, now I can't update because I can't get an internet connection

      I know this Tom. You and I worked for a good two hours to get it to work one Sunday.

      posted in Hardware Compatibility
      T
      TTellez
    • Had to hard code ENET adapter, now I can't update because I can't get an internet connection

      Working with someone from here, we got my Fog server working by hard coding the enet adapter in the server, but now when I plug it into an external network connection to try and update it, I get no internet connection.

      One thought I have is to disable the network connection that is hard coded and create a new connection, but I don’t want to lose that one. In Ubuntu, is it possible to create a new connection using the same adapter, then switch back to the old connection?

      Thoughts? Suggestions?

      posted in Hardware Compatibility
      T
      TTellez
    • RE: SO CLOSE .... "Ensuring node username and passwords match...."

      @Tom-Elliott you’re a gentleman and a scholar. I won’t believe the things they say about you again. Lol.

      posted in FOG Problems
      T
      TTellez
    • RE: SO CLOSE .... "Ensuring node username and passwords match...."

      @Tom-Elliott is there a simple command to completely replace the dhcpd.conf file? I’ve created a secondary file with the changes you made.

      (sorry, really an Ubuntu NEWB here, but I am loving this and learning SO MUCH. Thank you.)

      posted in FOG Problems
      T
      TTellez
    • RE: SO CLOSE .... "Ensuring node username and passwords match...."

      @Tom-Elliott HA we posted the SAME thing at the same time. How can I correct that?

      posted in FOG Problems
      T
      TTellez
    • RE: SO CLOSE .... "Ensuring node username and passwords match...."

      @george1421 ok I know its sunday, so I am sorry for the barrage of responses.

      I think I found something. the Fog server IP/Address is “localhost” or 10.1.1.10 but the DHCP server seems to be assigning the client 10.1.10.X IP addresses. So the subnet is not the same. I am guessing this is an issue. BUT, I don’t know how to change that.

      posted in FOG Problems
      T
      TTellez
    • RE: SO CLOSE .... "Ensuring node username and passwords match...."

      @george1421 OK, got my DHCP working. Also have my TFTP active and good, however, on PXE boot, I get the PXE-E11 error still in spite of having green lights on the TFTPD and DHCP statuses. DHCP assigns the client the IP and it moves on to TFTPD and then ffailes with the ARP timeout/

      posted in FOG Problems
      T
      TTellez
    • RE: SO CLOSE .... "Ensuring node username and passwords match...."

      @george1421 here is the text of my dhcp.conf file. Anything glaring out at you?

      # DHCP Server Configuration file\n#see /usr/share/doc/dhcp*/dhcpd.conf.sample
      # This file was created by FOG
      #Definition of PXE-specific options
      # Code 1: Multicast IP Address of bootfile
      # Code 2: UDP Port that client should monitor for MTFTP Responses
      # Code 3: UDP Port that MTFTP servers are using to listen for MTFTP requests
      # Code 4: Number of seconds a client must listen for activity before trying
      #         to start a new MTFTP transfer
      # Code 5: Number of seconds a client must listen before trying to restart
      #         a MTFTP transfer
      option space PXE;
      option PXE.mtftp-ip code 1 = ip-address;
      option PXE.mtftp-cport code 2 = unsigned integer 16;
      option PXE.mtftp-sport code 3 = unsigned integer 16;
      option PXE.mtftp-tmout code 4 = unsigned integer 8;
      option PXE.mtftp-delay code 5 = unsigned integer 8;
      option arch code 93 = unsigned integer 16;
      use-host-decl-names on;
      ddns-update-style interim;
      ignore client-updates;
      # Specify subnet of ether device you do NOT want service.
      # For systems with two or more ethernet devices.
      # subnet 136.165.0.0 netmask 255.255.0.0 {}
      subnet 10.1.10.0 netmask 255.255.255.0{
          option subnet-mask 255.255.255.0;
          range dynamic-bootp 10.1.10.10 10.1.10.254;
          default-lease-time 21600;
          max-lease-time 43200;
          option routers 10.1.1.1;
          option domain-name-servers 127.0.0.1;
          next-server 10.1.1.10;
          class "Legacy" {
              match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
              filename "undionly.kkpxe";
          }
          class "UEFI-32-2" {
              match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
              filename "i386-efi/ipxe.efi";
          }
          class "UEFI-32-1" {
              match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
              filename "i386-efi/ipxe.efi";
          }
          class "UEFI-64-1" {
              match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
              filename "ipxe.efi";
          }
          class "UEFI-64-2" {
              match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
              filename "ipxe.efi";
          }
          class "UEFI-64-3" {
              match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
              filename "ipxe.efi";
          }
          class "SURFACE-PRO-4" {
              match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016";
              filename "ipxe7156.efi";
          }
          class "Apple-Intel-Netboot" {
              match if substring(option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
              option dhcp-parameter-request-list 1,3,17,43,60;
              if (option dhcp-message-type = 8) {
                  option vendor-class-identifier "AAPLBSDPC";
                  if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) {
                      # BSDP List
                      option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47;
                      filename "ipxe.efi";
                  }
              }
          }
      }```
      posted in FOG Problems
      T
      TTellez
    • RE: SO CLOSE .... "Ensuring node username and passwords match...."

      @george1421 thanks for the prompt response george.

      As I am a NEWB I don’t know how to use putty. 😞 Wish that made things easier, but I don’t.

      Based on the way I had configure the install, I unplugged the network connection, and it immediately completed. However, now, I get the PX-e11 ARP Failed error… why can’t this just work. 😞

      I go to verify my DHCP and this is what I get (sorry about the screenshot)
      0_1491755556447_dhcpissue.png

      posted in FOG Problems
      T
      TTellez
    • SO CLOSE .... "Ensuring node username and passwords match...."
      Server
      • FOG Version: 1.3.5
      • OS: Ubuntu 16.04 LTS
      Description

      Finally got my installer to work, thanks to @Wayne-Workman and @george1421 But after the DB was configured and I am finally able to get to the management portal, we are stuck HERE. ARGH. 0_1491752137173_error1

      Do I wait it out? Is there a quick fix?

      Thanks in advance

      posted in FOG Problems
      T
      TTellez
    • RE: DHCP stopped working after power outage

      @Wayne-Workman I ran

      chmod 755 ./installfog.sh

      and it works now. Thanks for pointing that out.

      posted in FOG Problems
      T
      TTellez
    • RE: DHCP stopped working after power outage

      @Wayne-Workman the WE I meant was us here. I am nothing but appreciative of the help you offered. We have a linux pro here, and even he couldnt figure it out. I wasn’t being impatient with you.

      posted in FOG Problems
      T
      TTellez
    • RE: DHCP stopped working after power outage

      @Wayne-Workman we wasted too long working on this. I wiped the machine and am working on a fresh install, but now for some reason I am getting the Stopping Web Services …Failed and then it gets stuck at Adding needed repository, during install. I WANT THIS TO WORK! lmao.

      posted in FOG Problems
      T
      TTellez
    • RE: DHCP stopped working after power outage

      @Wayne-Workman @george1421 any ideas?

      posted in FOG Problems
      T
      TTellez
    • RE: DHCP stopped working after power outage

      POST reinstall, I restarted the DHCP server and checked the status again, and got this notification.

      0_1491576859098_IMG_0305.JPG

      posted in FOG Problems
      T
      TTellez
    • RE: DHCP stopped working after power outage

      I’ve decided to try a reinstall of the FOG server. I received a 404 error when i attempted WGET, but I was able to download the ZIP file from GitHUb.

      Currently installing. Will update.

      posted in FOG Problems
      T
      TTellez
    • RE: DHCP stopped working after power outage

      When I check the DHCP server status this is what I get. 0_1491568693968_IMG_0303.JPG

      posted in FOG Problems
      T
      TTellez
    • 1
    • 2
    • 3
    • 4
    • 5
    • 2 / 5