StevieM Posted September 3, 2020 Posted September 3, 2020 Hi all Over the summer, I re-imaged one of our IT suites using MDT and WDS. Every machine imaged successfully apart from 2, which reported a DHCP lease issue. This is what happens: PXE Boot over IP4 - WDS Boot Manager shows correct Client/Server IP addresses Download NBP Select operating system - Loads WIM from MDT\WDS server Processing Bootstrap Settings - Gathering Complete It then presents a Wizard Error - A connection to the deployment share could not be made. DHCP Lease was not obtained for any networking device! Possible cause: Check physical connection. If I click cancel, it presents a command prompt. Running ipconfig shows a valid IP address, which is visible in both DHCP and DNS. If I release the IP address, and try again, a correct IP address is picked up on the next try, but the same error occurs. If I renew the IP address, it picks up a correct address. I've tried deleting the IP address from DHCP and DNS - same error. I've even set up a reservation in DHCP, which the machine picks up and uses. Surely this shows that it has obtained a DHCP lease, doesn't it? All the other PCs are identical, have the same BIOS settings, and have had no problems. Any suggestions, anyone?
StevieM Posted September 3, 2020 Author Posted September 3, 2020 Would you believe that something as simple as plugging the PC into a different network socket did the trick? It's using the same IP address as before, only now it works! 1
ricki Posted September 3, 2020 Posted September 3, 2020 I know this will be a silly question have you tried stopping the DHCP service and starting it or restarting the DHCP server but check it's not run out of space on the c drive before you restart it
Katy Posted September 3, 2020 Posted September 3, 2020 Would you believe that something as simple as plugging the PC into a different network socket did the trick? It's using the same IP address as before, only now it works! I’ve had this (not DHCP but similar network weirdness) and swapping ports fixed it, but also plugging a working PC into the “dodgy” port and it carried on working instead of breaking. Makes no sense!
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