Jump to content


PVS 7.2 Target Device Unable to Connect to DHCP

Started by chris minchinton , 10 February 2017 - 04:37 PM
4 replies to this topic

chris minchinton Members

chris minchinton
  • 9 posts

Posted 10 February 2017 - 04:37 PM

hi all,


I wonder if someone has seen this issue or one similar?


We have a 2 PVS servers with 3 different NICS each on a different VLAN:


NIC 1 - is on 2214 (production)

NIC 2 - is on 2255 (streaming 1)

NIC 3 - is on 2257 (streaming 2)


The PVS servers have the DHCP role installed and has 2 scopes for streaming 1 and streaming 2.


streaming 1 is on x.x.12.x

streaming 2 is on x.x.21.x


We host our target devices on Hyper-v (with SCVMM) and when the legacy NIC is on the 2255 VLAN the system will boot and when set on 2257 on boot the device will sit waiting for DHCP and eventually will error with no boot device found. We also use reservations for each of the machines NICs so no un-authorized machines cannot 


We have created a normal windows machine and attached its NIC to 2257 and it is able to get a DHCP address (this was using the non legacy hyper-v NIC).


In the boot server host name we have one IP address that is the IP address of the one PVS server.


So looks like our DHCP seems to be working but during boot our one VLAN is having issues.


Hopefully someone will be able to help.


Many thanks.


George Spiers Members

George Spiers
  • 215 posts

Posted 11 February 2017 - 11:03 AM

What happens if you attach the "normal windows machine" with a legacy NIC, can it PXE boot from VLAN 2257?

Is the normal windows machine on the same hypervisor hosts/datacenter as the PVS Target Devices?

Benjamin Crill Members

Benjamin Crill
  • 209 posts

Posted 10 April 2017 - 03:45 PM

Sounds like you need a DHCP helper address added to the VLAN configuration on your switch

Carl Fallis Citrix Employees

Carl Fallis
  • 984 posts

Posted 12 April 2017 - 11:04 AM

You should try the Citrix PXEChecker tool for PVS, it helps diagnose PXe and DHCP issues it is located at http://support.citrix.com/article/ctx217122

chris minchinton Members

chris minchinton
  • 9 posts

Posted 04 May 2017 - 12:27 PM

Thank you we had tried that and it came up with an error, still awaiting our networks team and our virtualization team to look at the VLAN configurations.


Fingers crossed they will get back to me one day.