I've been playing around with MDT deployments to my ESXi Host, and I got the vmx3net driver injected into the image, windows 2019 is using the correct driver, and I know that it worked at least once to complete the deploy. However, now that I'm booting to the OS, I cant get on the network, I've got everything set as far as I can tell. Its loading the vmx3net driver and says everything is fine. It just wont pull from DHCP. or even if I static it, fails also.
And now, my second VM is failing to even pxe boot, even though its configured exactly the same as the one that worked earlier! My guess is that I've got something wrong in the vsphere networking, but I dont know what. I've verified the VM is showing up in DNS and has a reserved IP in our DHCP network with the correct MAC address.
Can you post a screen shot of your networking config so we can look at it?
Below are all the screen shots I could take
One thing I did notice is that the VMnic0 shows a subnet range thats only 1 address long. seems weird, but I cant see where to change that. Any other oddities? Thanks @BigMike23
guest config
vm config
VM network
vswitch
vmNIC0
vmkNIC
Figured it out. I tagged the port group as being part of our VLAN -- it just didnt like that. I set it back to 0, and its working fine. (even though I had the vlan correct.)
That is great that you figured it out and also thank you for posting the same so we didn't dig further into the problem.
