Troubleshooting PXE – WDM Tips!? Any gurus out there?

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #1270
    AvatarPeteWyser
    Member
    • Total Post: 7
    • Newbie

    Hi everyone,

    I have some wyse thin clients i’m trying to manage with WDM and right now everything is plugged into the same switch, they’re on the same subnet/ip range for testing, and for the life of me I can’t get the thin clients to boot up and display as being ‘Imagable’ in WDM. *Sometimes* it shows up for a few seconds, but then goes from Imagable: “Yes” to “No”….

    My proxy server is passing along options 186 and 187, I see the logs of WDM and it looks like it’s communicating….I don’t have any other PXE servers on the network…I can send commands to the thin client to reboot and it works fine…WOL works ok…I turned the write filter off on the client…not sure what else might be holding things up.

    Any thoughts?
    Pete

    #13244
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    Hi,

    what do you see while the unit is booting? Does it send out the PXE request? How is it answered?
    Do you see things like “Local Boot” or “Rapport PXE” messages there?
    What units are you using?

    CG

    #13245
    AvatarPeteWyser
    Member
    • Total Post: 7
    • Newbie

    Well, I looked through some various posts and tried deleting my machine from the device manager in WDM and adding it manually and selecting ‘Imagable” and it seems happy and lets me schedule packages.

    Problem is, whenever the thin client boots it just sits at the DHCP prompt with the spinning cursor and doesn’t go anywhere..it sits there at “DHCP….” then after 20 seconds or so says “no DHCP or ProxyDHCP offers were received”

    Is option 186/187 the only options you need to set in DHCP for a thin client to connect to the WDM/Rapport server? There’s a couple ports that WDM uses – when the documentation says “For Option 187, enter the port of the WDM server”…which port are they referring to? I have Hserver at 80, so i’m using “80” for option 187 and “80” as the port number within the Rapport properties within the control panel on the XPe thin client.

    Pete

    #13246
    AvatarPeteWyser
    Member
    • Total Post: 7
    • Newbie

    BTW – I’m using S90/S92 clients.

    In the log on my wyse Rapport diagnostic report, I see
    [DHCP] – Packet is DHCPREQUEST from device….

    that’s it…

    #13247
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    Looks for me like there are some fundamentals going wrong.
    Do the following:
    – Delete the device from WDM
    – Log in to the S90 as admin and open Control Panel-WDM (maybe called Rapport)
    – Enter the IP of your WDM server there
    – Reboot the device
    – It should now appear in the WDM console again
    – Reboot it again
    – It should show up with PXE enabled now

    If not,
    – check WDM – Configuration Manager if DHCP Proxy is activ
    – delete all option tags on your DHCP server that are not needed by non Wyse clients, like 60, 186, 187

    In the moment when your S90 waits for the DHCP reply for 20+ seconds, it should directly reply with either “Local boot” or “Rapport PXE” as soon as the client is know by WDM.

    CG

    #13248
    AvatarPeteWyser
    Member
    • Total Post: 7
    • Newbie

    I did the delete from WDM, then logged into the client and noticed somehow it dropped the IP address (still had the port) listed within the Rapport control panel settings.

    I put the IP in, rebooted, logged in…ensured the IP was still there…rebooted again… and it still doesn’t appear back in WDM by itself. I’m not doing anything on WDM other than hitting ‘refresh’

    I had been testing with/without the DHCP relay enabled in the WDM, and now that it’s enabled with this config you described, I do see at bootup now after the 15 or so seconds:

    “No boot filename received”

    #13249
    AvatarPeteWyser
    Member
    • Total Post: 7
    • Newbie

    Few minutes later the device popped into WDM as Imageable:No, and I rebooted but it stayed that way…will leave it for a while to see if anything changes..

    Pete

    #13251
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    There is something blocking the DHCP broadcast to the WDM server, make sure there is nothing blocking the communication between the client and the server.

    Load netmon on the WDM server and boot the client, did you see a DHCP REQ. packet from the wyse client? If not look for VLANS, firewalls or other issues,

    Cheers,
    -TT

    #13278
    AvatarPeteWyser
    Member
    • Total Post: 7
    • Newbie

    They’re on the same switch in the same subnet, same ip range …I didn’t think it would require any ip helpers or anything along those lines I did a trace with Wireshark and see a lot of arp broadcasts so it looks like I’m seeing traffic related to the thin client broadcasts for the windows dhcp server and such, but don’t know exactly which of these i’m supposed to be looking at?

    Pete

    #13282
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    Is the device directly connected to the switch or is it for example connected via some IP Phone?
    What’s the message you are getting now as the device is listed in WDM while PXE boot?

    CG

    #13309
    AvatarPeteWyser
    Member
    • Total Post: 7
    • Newbie

    The dhcp server is plugged into the port next to one the client is plugged into (literally). I’m not quite sure I understand what you’re looking for in the second question… I’m getting the same client messages from the last couple posts… The server says it’s PXE Imagable, but every time the client boots it doesn’t see anything to boot to, so it ends up booting to the XPe OS already on the thin client. Any ‘tasks’ I assign it from the WDM server just get ignored…they aren’t showing as ‘failed’, attempted, or anything like that…

    #13311
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    I am going to get out of ideas.
    Last thing you can do is to do a trace. Use tools like MS Netmon or Wireshark. Install it on WDM server, assign a job to the client, start the trace and then boot the unit. You can stop the trace in the moment when XPe starts booting.
    Maybe you can upload that trace somewhere and I will take a look at it.

    CG

    #13329
    AvatarCory
    Member
    • Total Post: 53
    • Back Stage Pass
    • ★★★★

    You say your DHCP server is connected to the same switch – but what about your WDM server? Are all devices and server on the same subnet? If not, you’ll need a helper address, even if they are the same physical hardware. Any router VLAN’s configured? Just throwing out anything I can think of that I’ve run into in the past.

    The only subnet I can connect to that doesn’t need a helper is the same as my WDM server. All others require it.

    And for the record; we don’t have ANY dhcp options configured for WDM (at least in the Active Directory DHCP scopes), XPe doesn’t need them. Our environment is all 9150’s and V90L’s, with WDM Enterprise 4.5.3.

    #13332
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    All Excellent advice Cory!

    PeterWyse you say:

    see a lot of arp broadcasts

    What you are looking for is a DHCP REQ (request) and it will be from the MAC of the terminal. WireShark will display these really clearly for you.

    Get a Wyse device and note the MAC address (there is a sticker on the unit with its MAC)

    Start the capture on the WDM server then boot the device, did you see the DHCP REQ from MAC 008064XXXXXX? If not the broadcast did not make it to the WDM server and you will need to work out why.

    Simple test to see if its the WDM server, load DHCP turbo on your notebook with a DHCP scope configured (same subnet as your WDM server). Then plug the WDM server, your notebook and the Wyse device together on a really simple switch or hub (One of those 4 port $10 ones form Fries). Now boot the device. If it works you have a network issue. If it still does not work your server is broken,

    Cheers,
    -TT

Viewing 14 posts - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.