Ghost Solution Suite

 View Only
Expand all | Collapse all

Odd PXE Behavior

  • 1.  Odd PXE Behavior

    Posted Dec 06, 2016 04:37 PM

    I'm trying to network boot to the server with GSS 3.1 but I'm getting different results from different clients.  The clients are the same  and I've had networking admins look at the settings various times and we can't identify the differences.  

    For some, the client boots to the menu as I'd expect.  Others exit the network boot right away.  

    I've included the MTFTP logs below if that might help (with the IP Addresses redacted).  That seemed like the log with the most difference and the only ones I noticed with anything specific to the clients.

    Thank you in advance for any help available!!

    NOT WORKING

    D [16:00:37.688 12/06] (2604): HandleTFTP: action: create  IPAddr=<<IPADDRESS>>:2070
    D [16:00:37.693 12/06] (2604): Enter: CreateUCast(...) IP: <<IPADDRESS>>
    D [16:00:37.698 12/06] (2604): Enter: RemoveClient: <<IPADDRESS>>:2070
    D [16:00:37.702 12/06] (2604): RemoveClient: Client not found - No files open by this client
    D [16:00:37.728 12/06] (2604): CreateUCast: Ucast client: <<IPADDRESS>>
    D [16:00:37.733 12/06] (2604): Enter: GetSlot(...)  Transfer Table Size: 200
            (2604)Transfer Table: available slot = 1
            (2604)CreateUCast: File Name: wdsnbp.com
            (2604)RestrictFilename: File Search: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\images\wdsnbp.com
            (2604)RestrictFilename: Search Results: false [0]
    D [16:00:37.759 12/06] (8920): InUseStatus: >>- MTFTP Service  (1481053618)  status=In use  exit=False
            (2604)RestrictFilename: File path not found [183]
            (2604)File Open: unavailable - C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\images\wdsnbp.com
            (2604)MySendTo completed: len = 24
    D [16:00:37.780 12/06] (2604): CloseUCast: client: <<IPADDRESS>>
    D [16:00:37.785 12/06] (2604): Enter: RemoveClient: <<IPADDRESS>>:2070
    D [16:00:37.791 12/06] (2604): RemoveClient: Client not found - No files open by this client
    D [16:00:40.075 12/06] (8920): InUseStatus: >>- MTFTP Service  (1481053618)  status=Not in use  exit=False

     

    WORKING

    D [15:58:58.447 12/06] (2604): HandleMTFTP: action: create  IPAddr=<<IPADDRESS>>:1758
    D [15:58:58.453 12/06] (2604): Enter: CreateMCast(...) IP: <<IPADDRESS>>:1758
    D [15:58:58.458 12/06] (2604): Enter: RemoveClient: <<IPADDRESS>>:1758
    D [15:58:58.486 12/06] (2604): RemoveClient: Client not found - No files open by this client
    D [15:58:58.491 12/06] (2604): CreateMCast: Mcast client: <<IPADDRESS>>
    D [15:58:58.496 12/06] (2604): Enter: GetSlot(...)  Transfer Table Size: 200
            (2604)Transfer Table: available slot = 1
            (2604)CreateMCast: File Name: Bstrap\X86PC\BStrap.0
            (2604)RestrictFilename: File Search: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\images\Bstrap\X86PC\BStrap.0
            (2604)RestrictFilename: Search Results: true [1]
            (2604)RestrictFilename: Path found: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\images\Bstrap\X86PC\BStrap.0
            (2604)RestrictFilename: Match Root: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\images
            (2604)FM_Open: Max Slots:128  Used Slots:0
    D [15:58:58.561 12/06] (2604): INIT Transfer Table Slot: Current Information
            (2604)     File Name: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\images\Bstrap\X86PC\BStrap.0
            (2604)       File Hd: 1
            (2604)        IPAddr: <<IPADDRESS>>
            (2604)          Port: 1758
            (2604)          Type: 1
            (2604)    Last Block: 0
            (2604)          Wrap: ffffffff
            (2604)          Done: no
            (2604)     File Size: 23285
            (2604)   UCast Sends: 1
            (2604)  Segment Size: 768
            (2604)CreateMCast: Open File: SUCCESS - Mcast client: <<IPADDRESS>>  FHd: 1  File: Bstrap\X86PC\BStrap.0
            (2604)SendMCast: TblIdx = 1 blk = 0  IPAddr: <<IPADDRESS>>
    D [15:58:58.635 12/06] (8920): InUseStatus: >>- MTFTP Service  (1481053618)  status=In use  exit=False
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
            (2604)        On create MCast, try UCast first.
            (2604)MySendTo completed: len = 772
    D [15:58:58.670 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 0 want blk: 1
            (2604)SendMCast: TblIdx = 1 blk = 1  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.699 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 1 want blk: 2
            (2604)SendMCast: TblIdx = 1 blk = 2  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.728 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 2 want blk: 3
            (2604)SendMCast: TblIdx = 1 blk = 3  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.756 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 3 want blk: 4
            (2604)SendMCast: TblIdx = 1 blk = 4  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.784 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 4 want blk: 5
            (2604)SendMCast: TblIdx = 1 blk = 5  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.812 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 5 want blk: 6
            (2604)SendMCast: TblIdx = 1 blk = 6  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.858 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 6 want blk: 7
            (2604)SendMCast: TblIdx = 1 blk = 7  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.886 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 7 want blk: 8
            (2604)SendMCast: TblIdx = 1 blk = 8  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.913 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 8 want blk: 9
            (2604)SendMCast: TblIdx = 1 blk = 9  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.941 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 9 want blk: 10
            (2604)SendMCast: TblIdx = 1 blk = 10  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.968 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 10 want blk: 11
            (2604)SendMCast: TblIdx = 1 blk = 11  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:58.995 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 11 want blk: 12
            (2604)SendMCast: TblIdx = 1 blk = 12  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.023 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 12 want blk: 13
            (2604)SendMCast: TblIdx = 1 blk = 13  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.051 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 13 want blk: 14
            (2604)SendMCast: TblIdx = 1 blk = 14  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.078 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 14 want blk: 15
            (2604)SendMCast: TblIdx = 1 blk = 15  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.107 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 15 want blk: 16
            (2604)SendMCast: TblIdx = 1 blk = 16  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.135 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 16 want blk: 17
            (2604)SendMCast: TblIdx = 1 blk = 17  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.163 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 17 want blk: 18
            (2604)SendMCast: TblIdx = 1 blk = 18  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.191 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 18 want blk: 19
            (2604)SendMCast: TblIdx = 1 blk = 19  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.218 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 19 want blk: 20
            (2604)SendMCast: TblIdx = 1 blk = 20  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.246 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 20 want blk: 21
            (2604)SendMCast: TblIdx = 1 blk = 21  IPAddr: <<IPADDRESS>>
            (2604)ReadFile: cache 0 update, return size: 7157
            (2604)cache info [off:len](lbr): #0[16128:7157](0), #1[16384:6901](0), #2[0:0](0), #3[0:0](0)
            (2604)Read to Cache 0 Data Returned
            (2604)MySendTo completed: len = 772
    D [15:58:59.286 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 21 want blk: 22
            (2604)SendMCast: TblIdx = 1 blk = 22  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.314 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 22 want blk: 23
            (2604)SendMCast: TblIdx = 1 blk = 23  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.342 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 23 want blk: 24
            (2604)SendMCast: TblIdx = 1 blk = 24  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.370 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 24 want blk: 25
            (2604)SendMCast: TblIdx = 1 blk = 25  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.398 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 25 want blk: 26
            (2604)SendMCast: TblIdx = 1 blk = 26  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.426 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 26 want blk: 27
            (2604)SendMCast: TblIdx = 1 blk = 27  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.455 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 27 want blk: 28
            (2604)SendMCast: TblIdx = 1 blk = 28  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.486 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 28 want blk: 29
            (2604)SendMCast: TblIdx = 1 blk = 29  IPAddr: <<IPADDRESS>>
            (2604)Cache 0 Data Returned (refread:1)
            (2604)MySendTo completed: len = 772
    D [15:58:59.516 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 29 want blk: 30
            (2604)SendMCast: TblIdx = 1 blk = 30  IPAddr: <<IPADDRESS>>
            (2604)ReadFile: cache 0 update, return size: 245
            (2604)Cache 0 Data Returned end of file.
            (2604)GetNextBlk: Data smaller than requested on Read
            (2604)        :        m_uiFile: 1
            (2604)        :   current block: 30
            (2604)        : m_usSegmentSize: 768
            (2604)        :        uLOffset: 23040
            (2604)        :    return unLen: 245
            (2604)        :    m_ulFileSize: 23285
            (2604)        :         bResult: 1
            (2604)MySendTo completed: len = 249
    D [15:58:59.598 12/06] (2604): HandleMTFTP: action: next block  IPAddr=<<IPADDRESS>>:1758
            (2604)HandleMTFTP: P_ACK for blk: 30 want blk: 31
            (2604)SendMCast: TblIdx = 1 blk = 31  IPAddr: <<IPADDRESS>>
    D [15:58:59.616 12/06] (2604): RESET Transfer Table Slot: Previous Information
            (2604)     File Name: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\images\Bstrap\X86PC\BStrap.0
            (2604)       File Hd: 1
            (2604)        IPAddr: <<IPADDRESS>>
            (2604)          Port: 1758
            (2604)          Type: 1
            (2604)    Last Block: 31
            (2604)          Wrap: ffffffff
            (2604)          Done: yes
            (2604)     File Size: 23285
            (2604)   UCast Sends: 0
            (2604)  Segment Size: 768
            (2604)CloseFile: reference count = 0
    D [15:59:02.052 12/06] (8920): InUseStatus: >>- MTFTP Service  (1481053618)  status=Not in use  exit=False

     



  • 2.  RE: Odd PXE Behavior
    Best Answer

    Posted Dec 07, 2016 11:27 AM

    fjwolz19,

     

    Since some clients boot successfully to PXE you know your configuration is working properly. Things to look for on the machines that are not booting correctly would be 

    Bios Version: Is the bios version identical to the machines that are booting properly.

    Boot Order: Is the boot order set to boot to PXE by default

    Network Location: Are the machines that are not booting on the same Vlan/Subnet as the others. If they are on a different subnet, dhcp options will need to be set correctly for imaging across vlans.

    Option 1: Using IP Helpers
    PXE not crossing subnets or VLANs
    https://support.symantec.com/en_US/article.TECH12651.html

    Option 2: Manually Setting DHCP Scope Options
    Vendor-specific PXE Forced Mode
    https://support.symantec.com/en_US/article.HOWTO7071.html

     



  • 3.  RE: Odd PXE Behavior

    Posted Dec 07, 2016 02:11 PM

    Thanks for the reply.  

    I should have mentioned that the two machines are on the same subnet and VLAN, and I've even swapped their locations so it doesn't even seem switch related.  

    The BIOS is also identical and I've confirmed every single setting (manually and by exporting the settings) in the BIOS is identical.

     

    Looking at the log, one seems to be UCAST and the other is MCAST.  That's the first point I notice a difference in the logs, any ideas what would cause that?



  • 4.  RE: Odd PXE Behavior

    Posted Dec 07, 2016 02:16 PM

    Are the clients showing in the console? If so can you remove them and do a manual boot to pxe to see if they will boot up properly.



  • 5.  RE: Odd PXE Behavior

    Posted Dec 07, 2016 02:53 PM

    None of the computers are showing up in the console.  I'm not sure if this is because of how I set it up or what.  I'm doing a manual network boot everytime, which is how I plan to use it always.  Unless I need to, I'm not intending to use the console or jobs or anything, I just want it to boot to PXE, give me the menu and let me choose from the 2 winpe options I've configured.  The ones that are working are doing exactly that.  The others do the network boot but skip straight out of it before showing the menu.

     

    Thanks!!



  • 6.  RE: Odd PXE Behavior

    Posted Dec 07, 2016 04:22 PM

    I assume you set your pxe up following the below article?

    https://www.symantec.com/connect/articles/creating-pxe-boot-image-ghostcasting-ghost-solution-suite-3

     

    By default when you boot to pxe/automation the first time the dagent gets installed on the machine. From there on out it will show in the console and will never boot to initial deployment again.

    If you followed the above article... where do your non working machines stop when you boot them to pxe? Do you have a screenshot?



  • 7.  RE: Odd PXE Behavior

    Posted Dec 07, 2016 04:48 PM

    Yes, I did follow that particular article.

    I'm just trying to deliver a basic Ghost boot disk that launches the ghost executable, like the article says.  I'm not sure I'm understanding how or where an agent could be installed on the machine in this preboot environment, or why I would want that.

    As far as where they are stopping, I've attached a picture of the results on each client.

     

    Thanks!!



  • 8.  RE: Odd PXE Behavior

    Posted Dec 07, 2016 04:56 PM

    Lets have you try navigating to your pxe settings -> Multicast and disable MTFTP. 

    Save your PXE settings and then reboot the machines and try to connect once more.

    Also check your MAC Filter tab and verify nothing is listed in this tab (unless you are specifically MAC filtering). 

    These machines are identical hardware, manufacturer etc..?



  • 9.  RE: Odd PXE Behavior

    Posted Dec 08, 2016 11:48 AM

    I disabled MTFTP as instructed and both machines still behave the same (one works one doesn't).  For good measure, I tried the other settings in that section as well with the same results.

    Use MAC Address Filtering is not checked.

    The machines are identical.  This is a lab environment and they were all purchased at the same time through a government contract, so hardware, manufacturer, etc are all the same.



  • 10.  RE: Odd PXE Behavior

    Posted Dec 08, 2016 11:59 AM

    Hmm. if both machines are identical and configured the same (bios settings, versions etc..) I see no reason why the 2nd machine is not booting correctly.

    Your first machine boots just fine so we know your PXE environment is not the issue.

    There must be something that is different with that second machine.... have you verified the bios version on the second machine or are you assuming it is the same version because they were purchased altogether? You may search and see if a bios update is available for that model and get it on the latest version.



  • 11.  RE: Odd PXE Behavior

    Posted Dec 08, 2016 12:07 PM

    I have verified that the BIOS version is identical on both machines.  I also went one by one (luckily they are next to each other) through each setting and confirming they are the same.

     

    Yeah, it seems like something has to be different, but I can't think of what...especially since I've swapped the ports and the problem stuck with the computer, not the port.



  • 12.  RE: Odd PXE Behavior

    Posted Dec 08, 2016 12:20 PM

    Is secure boot enabled in the bios?

    What format are you booting Legacy or UEFI?



  • 13.  RE: Odd PXE Behavior

    Posted Dec 08, 2016 03:58 PM

    The BIOS for the two main ones I am testing with do not have Secure Boot.  I do have another model which does have Secure Boot, however, when I turn on Secure Boot, the Legacy boot options are unavailable.  And, like the other two I've been testing with, Network is not an option under UEFI.  So that also answers the UEFI vs Legacy question - Legacy is the only one with Network, so that's what I am using.



  • 14.  RE: Odd PXE Behavior

    Posted Dec 13, 2016 02:59 PM

    I'm afraid we have been through everything I can think of on this... I would check the manufacturer for a new bios version and verify the network cards are the same for both machines.

    We know pxe is working correctly so there must be an issue with that one machine. Maybe the card is malfunctioning and not able to network boot? Do you have another ethernet card you can put in that machine to test with?



  • 15.  RE: Odd PXE Behavior

    Posted Dec 13, 2016 03:30 PM

    Thanks for all your help.  I have tried updating the BIOS just in case but that didn't make a difference.  Unfortunately, it's not just one machine, and they definitely have the same network cards (on-board).

    I'm still working with the Network Admins through some ideas on that front, so maybe we'll find something there.  I'll report back if so.  Thanks,