denmyos Posted July 15, 2014 Posted July 15, 2014 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. http://www.edugeek.net/forums/o-s-deployment/139450-reinstalling-wds-share-name-already-use-server.html
sted Posted July 15, 2014 Posted July 15, 2014 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)
denmyos Posted July 15, 2014 Author Posted July 15, 2014 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.
sted Posted July 15, 2014 Posted July 15, 2014 what version of server are you running as i diddnt think wds ran on a non domain joined server?
denmyos Posted July 15, 2014 Author Posted July 15, 2014 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.
themightymrp Posted July 15, 2014 Posted July 15, 2014 DHCP option 66 should be set to the IP address of the WDS server. Option 67 should look like: 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
sted Posted July 15, 2014 Posted July 15, 2014 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
denmyos Posted July 15, 2014 Author Posted July 15, 2014 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.
denmyos Posted July 15, 2014 Author Posted July 15, 2014 DHCP option 66 should be set to the IP address of the WDS server. Option 67 should look like: 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.
SYNACK Posted July 15, 2014 Posted July 15, 2014 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.
themightymrp Posted July 15, 2014 Posted July 15, 2014 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
denmyos Posted July 15, 2014 Author Posted July 15, 2014 (edited) 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. Edited July 15, 2014 by denmyos
themightymrp Posted July 15, 2014 Posted July 15, 2014 Definitely sounds more like the virtual switch setting in VMware. I think @SYNACK is on the right track there with the broadcast settings
denmyos Posted July 16, 2014 Author Posted July 16, 2014 (edited) DHCP option 66 should be set to the IP address of the WDS server. Option 67 should look like: 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.? Edited July 16, 2014 by denmyos
denmyos Posted July 16, 2014 Author Posted July 16, 2014 (edited) Solved!! My bad, wrong ip address etc Now its gettin weird,, I'm suddenly getting the same error from within my vmware environment.?? Other problem with psysical client still persist.! Edited July 16, 2014 by denmyos
denmyos Posted June 19, 2015 Author Posted June 19, 2015 This solved the problem. set commands - ip forward-broadcast on the necessary vlan-interfaces in the distribution.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now