WDS2012 - cannot boot from a VM into PXE
H Experts,
I have installed a WDS2012 Server for deployment.
The boot image and capture images are done.
For test I want to use a vm from vmware.
But I cannot boot via pxe.
Do you have any ideas ?
or is it not possible with a vm ?
I have installed a WDS2012 Server for deployment.
The boot image and capture images are done.
For test I want to use a vm from vmware.
But I cannot boot via pxe.
Do you have any ideas ?
or is it not possible with a vm ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
now I want to boot from a physical client into PXE and I have the same error.
TFTP timeout...
Why TFTP ?
In services I cannot see any TFTP server service running.
TFTP timeout...
Why TFTP ?
In services I cannot see any TFTP server service running.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok I will check this now
ASKER
still not working.
Is it a problem when the gateway shows always 0.0.0.0 ?
Is it a problem when the gateway shows always 0.0.0.0 ?
ASKER
see the picture...
cannot-boot-from-vm.JPG
cannot-boot-from-vm.JPG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Strange is, last week it was working and no changes were made.
What can be the problem with the WDS ?
What can be the problem with the WDS ?
ASKER
WDS role is installed
Boot Image is created
Capture Image is set
All was working, now I always get
NO RESPONSE FROM WINDOWS DEPLOYMENT SERVICES
Boot Image is created
Capture Image is set
All was working, now I always get
NO RESPONSE FROM WINDOWS DEPLOYMENT SERVICES
ASKER
now I also changed the NIC type from VXNET3 to E1000
But the same error.
But the same error.
ASKER
has ist to do with the broadcast of the client, because it is another subnet ?
ASKER
do you have any idea ?
because I cannot boot from VM into PXE.
See below:
The Following Client started TFTP Download:
Client IP: 10.2.4.51
Filename: boot\x64\pxeboot.com
File Size: 25358
Client Port: 2072
Server Port: 64970
Variable Window: false
The Following Client completed TFTP Download:
Client IP: 10.2.4.51
Filename: boot\x64\pxeboot.com
File Size: 25358
Client Port: 2072
Server Port: 64970
Variable Window: false
A Non-Shared buffer created for reading file C:\RemoteInstall\boot\x64\
because I cannot boot from VM into PXE.
See below:
The Following Client started TFTP Download:
Client IP: 10.2.4.51
Filename: boot\x64\pxeboot.com
File Size: 25358
Client Port: 2072
Server Port: 64970
Variable Window: false
The Following Client completed TFTP Download:
Client IP: 10.2.4.51
Filename: boot\x64\pxeboot.com
File Size: 25358
Client Port: 2072
Server Port: 64970
Variable Window: false
A Non-Shared buffer created for reading file C:\RemoteInstall\boot\x64\
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Look, I have two DHCP servers.
From one site it is working with a physical client.
The vm is in another location and connects to another DHCP server.
See the picture before. The settings are ok.
But I am still not possible to connect to the WDS with a vm....
From one site it is working with a physical client.
The vm is in another location and connects to another DHCP server.
See the picture before. The settings are ok.
But I am still not possible to connect to the WDS with a vm....
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the vm gets the ip 10.2.4.x
This is the site where the vmware is located.
The wds server has the ip 10.2.1.90
This subnet is for servers.
You have seen the client gets the dhcp settings....
I do not understand what is wrong ?
This is the site where the vmware is located.
The wds server has the ip 10.2.1.90
This subnet is for servers.
You have seen the client gets the dhcp settings....
I do not understand what is wrong ?
ASKER
the physical client on another site works with another dhcp server.
The client has IP 10.1.4.x
The WDS server has 10.2.1.90
And in this scenario the gateway is also set automatically.
You see the subnets are different, but I can boot with pxe.
The client has IP 10.1.4.x
The WDS server has 10.2.1.90
And in this scenario the gateway is also set automatically.
You see the subnets are different, but I can boot with pxe.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
our network is devided in two parts.
PART A has all DHCP client 10.1.4.x
here the pxe boot with a physical machine works.
And I tested another VM from proxmox, this also works.
Here the DHCP settings ok, I think.
PART B has all DHCP client 10.2.4.x
here the pxe boot is not working.
Both DHCP servers are set up with 66 and 67
Where is the error here ?
PART A has all DHCP client 10.1.4.x
here the pxe boot with a physical machine works.
And I tested another VM from proxmox, this also works.
Here the DHCP settings ok, I think.
PART B has all DHCP client 10.2.4.x
here the pxe boot is not working.
Both DHCP servers are set up with 66 and 67
Where is the error here ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Look,
yesterday I found out, in NETWORK A it is working with the DHCP settings.
And in NETWORK B pxe boot with vmware vm´s is not working.
The subnet is a 16bit subnet mask.
Yesterday I also enter the same data to the DHCP B, like in DHCP A.
As you can see in the picture, the IP of the WDS is 10.2.1.91
The WDS works very well with the NETWORK A, 10.1.4.x /16
Routing is ok here.
boot-from-proxmox-vm-to-pxe.JPG
yesterday I found out, in NETWORK A it is working with the DHCP settings.
And in NETWORK B pxe boot with vmware vm´s is not working.
The subnet is a 16bit subnet mask.
Yesterday I also enter the same data to the DHCP B, like in DHCP A.
As you can see in the picture, the IP of the WDS is 10.2.1.91
The WDS works very well with the NETWORK A, 10.1.4.x /16
Routing is ok here.
boot-from-proxmox-vm-to-pxe.JPG
ASKER
On the NETWORK A , I have a /16 subnet
On the NETWORK B , I have a /21 subnet
On the NETWORK B , I have a /21 subnet
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, here they are:
DHCP NETWORK B
IP Pool 10.2.4.10-10.2.4.200, subnet: 255.255.248.0
003-router 10.2.1.254
006-DNS 10.2.1.1 , 10.2.1.2
015-DNS Domain domain.local
042-NTP server 10.2.1.1
044-WINS 10.2.1.1
046-WINS NBT 0x8
066-Deployserver
067-boot\x64\wdsnbp.com
And I made a test for routing.
The vm client always gets the IP 10.2.4.46
Now I gave this IP to a WIN8 test vm.
From this vm I could ping the WDS server.
And from the WDS server I could ping the WIN8 test vm.
Any ideas what is wrong here ?
DHCP NETWORK B
IP Pool 10.2.4.10-10.2.4.200, subnet: 255.255.248.0
003-router 10.2.1.254
006-DNS 10.2.1.1 , 10.2.1.2
015-DNS Domain domain.local
042-NTP server 10.2.1.1
044-WINS 10.2.1.1
046-WINS NBT 0x8
066-Deployserver
067-boot\x64\wdsnbp.com
And I made a test for routing.
The vm client always gets the IP 10.2.4.46
Now I gave this IP to a WIN8 test vm.
From this vm I could ping the WDS server.
And from the WDS server I could ping the WIN8 test vm.
Any ideas what is wrong here ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes the IP of WDS is 10.2.1.91.
NETWORK A and NETWORK B are two different sites locations.
We are connected over WAN.
Therefore we have 2 DHCP servers, but the scope is different of course.
What I don´t understand, in each manual about setting up WDS2012, they also explain to set 66+67 in DHCP. Now you say not.
But how the client can find the WDS server over the network, when booting in PXE mode ?
How and where to setup the DHCP relay or IP HELPER ?
Yes I have checked the logs on WDS, nothing strange.
NETWORK A and NETWORK B are two different sites locations.
We are connected over WAN.
Therefore we have 2 DHCP servers, but the scope is different of course.
What I don´t understand, in each manual about setting up WDS2012, they also explain to set 66+67 in DHCP. Now you say not.
But how the client can find the WDS server over the network, when booting in PXE mode ?
How and where to setup the DHCP relay or IP HELPER ?
Yes I have checked the logs on WDS, nothing strange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The only thing is I have gateway 0.0.0.0