13 Replies Latest reply on Feb 3, 2009 12:34 PM by scottunify

    Invalid MAC address

    Apprentice

      Hi all

       

      When the PXE Boot Menu loads and we select ANY image, we are getting a DOS screen with "Error: Invalid MAC address</RunScriptResult></RunScriptResponse></soap:Body></soap:Envelope>  Press enter to continue".

       

      We have followed the 4 suggested fixes in the LANDesk Support doc to no avail http://community.landesk.com/support/docs/DOC-1079.

       

      - We have checked there are no instances of this machine (PXE client) in the core server, so there should not be a duplicate device problem.
      -  We have checked that ALL LANDesk services, including the Inventory service, ARE running as normal.
      - We have stopped the Inventory service, moved all .SCN mini-scan files from \...\LANDesk\ManagementSuite\ldscan to a backup folder then restarted the Inventory service.
      -  We have also restarted the IIS Admin service & WWW Publishing service.
      - From our experience, a successful PXE boot sends a miniscan (.SCN file) of the machine to the database.  However, when monitoring the \...\LANDesk\ManagementSuite\ldscan folder this does appear to be happening so this could be the root cause of the problem.  We have tried different machines also.

       

      We are still getting the "Invalid MAC address" error when PXE Booting ANY machine from different PXE Reps.  Can anyone offer any help please?

       

      Thanks
      Scott

        • 1. Re: Invalid MAC address
          phoffmann SupportEmployee

          You don't stand much of a chance of "seeing" a mini-scan with the naked eye, as they're 1 KB, and get processed as a priority by the Inventory Service.

           

          The way to check what's going on via scanfiles is this.

           

          1 - Open the 32-bit Console on the Core.

          2 - Go to CONFIGURE => SERVICES

          3 - Select the "Inventory"-tab on the new window.

           

          4 - Click on the "Advanced Settings"-button.

           

          5 - Find the line "Store Scans" and set the value to "1".

          6 - Click "OK" to close the settings window.

          7 - Click "OK" to close the Service Configuration window.

           

          NOTE -- you'll be prompted for a restart of the inventory service to apply the change

           

          You'll now notice a subdirectory under "\\YourCore\ldmain\ldscan\" called "storage" -- ALL incoming files (scn / ims) will have a copy dumped into here. I'd suggest doing this during a known quiet period, as this can eat quite a bit of I/O at the wrong time of the day.

           

          This will give you a better idea of what's going on regarding incoming mini-scans and their contents .

           

          Paul Hoffmann

          LANDesk EMEA Technical Lead

          • 2. Re: Invalid MAC address
            Apprentice

            Thanks Paul

             

            I have done as you suggested and I can see a 517kb .SCN file in the storage folder but I'm not sure where to go from here.  I'd like to upload the .SCN file for your analysis but there's quite a bit of data I'd rather not publicise.

             

            Can you advise please?

             

            Thanks

            Scott

            • 3. Re: Invalid MAC address
              phoffmann SupportEmployee

              You're looking for a ".IMS" file.

               

              SCN == "normal scan file"

              IMS == "miniscan file"

               

              The OSD process sends miniscan files, they're the ones you're interested in .

               

              And they're pretty much only 4-5 lines ... *digs* ... here's what one usually looks like:

              {code}

              Device ID = {3D1111EB-7073-EB44-9E4F-4F1D472203E9}
              Network - NIC Address = 0010A4F77BC3
              Network - TCPIP - Adapter 0 - Subnet Mask = 255.255.255.0
              BIOS - Serial Number = SERIAL11
              BIOS - Asset Tag = ASSETTAG-123-1
              Display Name = MACHINE1

              {/code}

               

              ... that's off a template file that's 4 years old, but it gives you the idea of things - the important stuff is the network information. Which can be a problem if you have multiple NIC's in that thing (we may end up pulling a NIC with an IP of 0.0.0.0 for instance) ...

               

              Paul Hoffmann

              LANDesk EMEA Technical Lead

              • 4. Re: Invalid MAC address
                Apprentice

                There are no IMS files, just SCN files.  Perhaps this is the problem then?

                • 5. Re: Invalid MAC address
                  phoffmann SupportEmployee

                  It certainly would be pointing towards it .

                   

                  What OSD environment do you use? If it's WinPE, the problem's going to be most likely with the detection of the NIC on whatever hardware you use.

                   

                  Pretty much "Name Resolution" (of the Core) or "NIC driver" account for 99% of this sort of problems.

                   

                  Paul Hoffmann

                  LANDesk EMEA Technical Lead

                  • 6. Re: Invalid MAC address
                    Apprentice

                    We're using DOS imaging.  Does your advice still count?  If it helps, we've never had a problem imaging a Toshiba M10 laptop in our LDMS 8.5 environment so assumed it would work in our new LDMS 8.8 environment.  Wrong assumption?

                    • 7. Re: Invalid MAC address
                      Apprentice

                      I ran \\core\ldmain\landesk\vboot\NICInfo.exe on a desktop and a laptop.

                       

                      1) HP 7800DC desktop.  The contents of dosnic.txt reads:-

                       

                      8086

                      10BD

                       

                      2) Toshiba M10 laptop.  The contents of dosnic.txt reads:-

                       

                      8086

                      103D

                       

                      nic.txt within LDVBOOT.IMG contains:-

                       

                      ven=8086 "Intel"
                            dev=103d "PRO/100 VE Network Connection"
                            dev=10bd "Intel PRO/1000 Gigabit Desktop Adapter"
                            drv="E1000"

                       

                      I have also checked that E1000.DOS (28/06/2005) exists within LDVBOOT.IMG.

                       

                      We have re-deployed the PXE Rep and tried both machines but we're still getting the "Invalid MAC address" error.

                       

                      I then noticed the following during the PXE Boot script process just before the PXE Boot Menu appears:-

                       

                      MS-DOS LAN Manager v2.1 Netbind

                      Microsoft DOS TCP/IP 1.0a

                      NET0135: Duplicate hostname:

                      xxx.xxx.xxx.58 vmscott

                       

                      Perhaps this explains why we are getting the "Invalid MAC address" error?  I have checked vmscott responds to a different IP address and is off anyway.  The IP address referenced is a different machine name altogether and is online.  I do not know where to go from here.

                       

                      Any ideas please?

                       

                      Thanks

                      Scott

                      • 8. Re: Invalid MAC address
                        Employee

                        Have you tried scouring the console for the MAC address of the NIC and deleting any records out? Sometimes cleaning out any and all records fixes this kind of issue.

                        • 9. Re: Invalid MAC address
                          Apprentice

                          Hi IronMike

                           

                          We had already checked that the MAC address of the NIC does not exist in the console.  The Inventory service is running fine so I'm not sure why the miniscan (including MAC address, etc...) is not sent to the core during the PXE Boot operation.

                           

                          Any ideas please?

                           

                          Thanks

                          Scott

                          • 10. Re: Invalid MAC address
                            Employee

                            If you are not even getting the miniscan on the core server, then there are two things I would consider:

                             

                            1) The NIC driver. I know you probably have gone through this exercise already. However, sometimes new revisions of the same NIC can be problematic. If you have a NIC in a machine that works, try moving it to the problematic machine to see if the problem goes away. This test would either put the driver issue to rest or prove it is the cause of the failure.

                             

                            2) The PXE booting machine may be send the inventory scan somewhere else than where you expect it to go. Do you have more than one PXE rep? If you look carefully at the PXE booting process you should see the PXE proxy IP address, which will be the IP of your PXE rep. Make sure this matches your PXE rep. Also crack open the dosundi.1 and bootmenu.1 files (with something like WinImage) that somewhere under \LANDesk\PXE directory on the PXE rep. Look for and extract the startenv.bat file and verify it's pointing to your core.

                            • 11. Re: Invalid MAC address
                              Apprentice

                              Thanks for your suggestions IronMike...


                              1) We don't have any machines that successfully PXE Boot, i.e. get passed the "Invalid MAC address" error.  Also, I would be surprised it if was the NIC driver because a) we have tried various laptop and desktop models b) these laptop and desktop models all PXE Boot fine in our LDMS 8.5 environment.


                              2) We have checked the Proxy IP matches the correct PXE Rep and startenv.bat is pointing to the correct IP address for our LDMS 8.8 core server.

                               

                               

                              The following occurs during the PXE Boot script process just before the PXE Boot Menu appears:-

                               

                              MS-DOS LAN Manager v2.1 Netbind

                              Microsoft DOS TCP/IP 1.0a

                              NET0135: Duplicate hostname:

                              xxx.xxx.xxx.58 vmscott

                               

                               

                              We're not sure how to track down this apparent duplication.

                               

                              What do you think causes this please?

                               

                               

                              Best Regards

                              Scott

                              • 12. Re: Invalid MAC address
                                ahe Expert

                                Hello Scott,

                                 

                                strange thing.

                                 

                                Some questions, did you test the PXE boot without the use of miniscan? (set comments in the OSD script)

                                 

                                Did you try your old boot files ldvboot.img, etc. of 8.5? (if the server is changed, change the ip or servename in the files)

                                 

                                Did you test (for "fun") the boot process with WinPE?

                                 

                                We used DOS 'til migration to 8.7 SP5 on 8.5 and 8.7. But we use everytime our own boot files (they are memory optimized :-))

                                 

                                Regards

                                Axel

                                • 13. Re: Invalid MAC address
                                  Apprentice

                                  Hi Axel

                                   

                                  We have already tried our old boot files ldvboot.img, etc. from the 8.5 environment (we also changed the IP of the core in the files), but we still get the "Invalid MAC address" error.

                                   

                                  WinPE is not validated so we cannot test this, we may look at paying to validate it at a later date but for now, we just want to get our DOS imaging environment working,

                                   

                                  Can you share your own "memory optimized" boot files?

                                   

                                  We have never tested the PXE boot process without the use of miniscan.  We have looked in the OSD script and think we need to comment out the following line:-

                                   

                                  REMEXEC39=r:\dos\fworkcl.exe /c r:\guid.pds 0 1 \LDISCAN.CFG

                                   

                                  Can you confirm if this is correct and if not which line we need to comment out please?

                                   

                                   

                                  Cheers

                                  Scott