+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 16
O/S Deployment Thread, no contact from pxeboot to wds in Technical; I'm running a vmware environment vmware workstation 10 server 2012 r2 wds MDT 2013 When I pxeboot within vmware everything ...
  1. #1

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0

    no contact from pxeboot to wds

    I'm running a vmware environment

    vmware workstation 10
    server 2012 r2
    wds
    MDT 2013

    When I pxeboot within vmware everything works fine.

    But when i pxeboot from a physical computer I get no connection.

    I get the correct IP address and DHCP address

    I getting thise error

    TFTP.
    PXE-t04: Access violation
    DASH-E36: Error received from TFTP server
    DASH-M0F: Exiting option ROM

    Our network administrator is pulling hairs to figure out what is going on.

    In INFOBLOX we have put in this path \\servername\reminst\boot\x86\wdsnbp.com
    Is that the correct path?


    When my client boot into windows it can ping the wds and vice versa, and see the share \\xxxxx\reminst\boot

    My client is a Lenovo M78 windows 7
    I also tried a "old" HP I got the same error.

    I reinstalled the wds again (twice) with no change.

    Any help is appreciated.

    Also see here for further info.

    ReInstalling wds, the share name is already in use on this server

  2. #2


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    7,046
    Thank Post
    232
    Thanked 922 Times in 791 Posts
    Rep Power
    308
    is the wds server also the dhcp server? does the dhcp server have options 66/67 set appropriately as sometimes these need setting (and ive had o set them here for 1 tye of pc everything else woked fine)

  3. #3

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by sted View Post
    is the wds server also the dhcp server? does the dhcp server have options 66/67 set appropriately as sometimes these need setting (and ive had o set them here for 1 tye of pc everything else woked fine)
    No the wds/mdt is a standard alone (workgroup), the dhcp is on another network.
    BUT the clients gets a IP address from the dhcp when pxeboot.

    Yes option 66/67 is sat up.

  4. #4


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    7,046
    Thank Post
    232
    Thanked 922 Times in 791 Posts
    Rep Power
    308
    what version of server are you running as i diddnt think wds ran on a non domain joined server?

  5. #5

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by sted View Post
    what version of server are you running as i diddnt think wds ran on a non domain joined server?
    server 2012 r2

    yes it does.
    The is actually a switch asking Domain or standalone.

  6. #6
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,282
    Thank Post
    218
    Thanked 237 Times in 205 Posts
    Rep Power
    76
    DHCP option 66 should be set to the IP address of the WDS server. Option 67 should look like:

    Code:
    boot\x86\wdsnbp.com
    That should be it. Make sure these 2 options are set either as a server option on the DHCP or in each separate vlan scope

  7. #7


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    7,046
    Thank Post
    232
    Thanked 922 Times in 791 Posts
    Rep Power
    308
    does vmware need a different kind of nic to so this i know for instance hyper v cant boot to pxe with its default nic type (sorry i dont know vmware) the virtual adapter may not be capable of recieving the info sen as the driver never took it into consideration

  8. #8

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by sted View Post
    does vmware need a different kind of nic to so this i know for instance hyper v cant boot to pxe with its default nic type (sorry i dont know vmware) the virtual adapter may not be capable of recieving the info sen as the driver never took it into consideration

    Mine is sat to bridged
    But since a physical win 7 can ping and get to the netshare boot\x86\wdsnbp.com.... it should work.

  9. #9

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by themightymrp View Post
    DHCP option 66 should be set to the IP address of the WDS server. Option 67 should look like:

    Code:
    boot\x86\wdsnbp.com
    That should be it. Make sure these 2 options are set either as a server option on the DHCP or in each separate vlan scope

    I will check with the men wiser that me.

  10. #10

    Oaktech's Avatar
    Join Date
    Jul 2011
    Location
    Bournemouth
    Posts
    3,203
    Thank Post
    941
    Thanked 642 Times in 501 Posts
    Rep Power
    287
    server firewall?

  11. #11

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,271
    Thank Post
    884
    Thanked 2,749 Times in 2,322 Posts
    Blog Entries
    11
    Rep Power
    785
    Look at the VMware virtual switch and whatever switch it is connected to, is there any form of broadcast filtering or prevention switched on, if there is everything but the initial PXE and DHCP (if it is on the same VM) would work but the those two require reception of a broadcast from the client, you may need to turn on a DHCP helper address or something in your external switch to convert those broadcasts into unicasts so that they get through.

  12. #12
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,282
    Thank Post
    218
    Thanked 237 Times in 205 Posts
    Rep Power
    76
    Which parts of your setup are running as virtual and which bits physical?

    Is the WDS/MDT server running as a virtual machine on VMware? Or is it a physical server?

    And you say that pxeboot DOES work from a VMware workstation client? If so is this running on the same VMware server/PC? Just trying to picture your setup in my head

  13. #13

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by themightymrp View Post
    Which parts of your setup are running as virtual and which bits physical?

    Is the WDS/MDT server running as a virtual machine on VMware? Or is it a physical server?

    And you say that pxeboot DOES work from a VMware workstation client? If so is this running on the same VMware server/PC? Just trying to picture your setup in my head

    My server 2012 r/MDT/WDS is virtuel
    +
    clients (where pxeboot works) (on the same virtuel vmware as the server)



    1 physical client (that can't pxeboot)




    server firewall
    is turned off.


    Look at the VMware virtual switch and whatever switch it is connected to, is there any form of broadcast filtering or prevention switched on, if there is everything but the initial PXE and DHCP (if it is on the same VM) would work but the those two require reception of a broadcast from the client, you may need to turn on a DHCP helper address or something in your external switch to convert those broadcasts into unicasts so that they get through

    I will check with my network administrator.
    Last edited by denmyos; 15th July 2014 at 03:41 PM.

  14. #14
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,282
    Thank Post
    218
    Thanked 237 Times in 205 Posts
    Rep Power
    76
    Definitely sounds more like the virtual switch setting in VMware. I think @SYNACK is on the right track there with the broadcast settings

  15. #15

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by themightymrp View Post
    DHCP option 66 should be set to the IP address of the WDS server. Option 67 should look like:

    Code:
    boot\x86\wdsnbp.com
    That should be it. Make sure these 2 options are set either as a server option on the DHCP or in each separate vlan scope

    We just did option 67

    But still get

    TFTP.
    PXE-t04: Access violation
    DASH-E36: Error received from TFTP server
    DASH-M0F: Exiting option ROM


    we will try this solution
    And see what happens

    Look at the VMware virtual switch and whatever switch it is connected to, is there any form of broadcast filtering or prevention switched on, if there is everything but the initial PXE and DHCP (if it is on the same VM) would work but the those two require reception of a broadcast from the client, you may need to turn on a DHCP helper address or something in your external switch to convert those broadcasts into unicasts so that they get through.


    Just learned that our switches are

    Distribution Cisco 3750
    Access HP A5120


    I just installed wireshark on the vmware server,, it seems like the pxeboot is getting through.?
    pxeboot.PNG
    Last edited by denmyos; 16th July 2014 at 10:04 AM.



SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. WDS + MDT No response from server
    By magikmike in forum Enterprise Software
    Replies: 7
    Last Post: 24th July 2013, 10:37 AM
  2. [WDS] I have 3 computers that now won't connect to WDS ..
    By soveryapt in forum O/S Deployment
    Replies: 5
    Last Post: 13th September 2012, 05:02 PM
  3. [WDS] Clients boot to WDS no matter what option 66 and 67 are set to
    By bart21 in forum O/S Deployment
    Replies: 8
    Last Post: 13th May 2011, 05:18 PM
  4. [WDS] Connecting to WDS Server
    By edsa in forum O/S Deployment
    Replies: 4
    Last Post: 27th January 2011, 12:22 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •