Snap 5 DHCP woes

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 2
Kommentare: 5

Hardware. Dell T1700 with Intel I217-LM Ethernet card.

So i'm having some serious issues getting Snap 5 to talk to our DHCP servers.
In windows i get DHCP right away, and i can run the /release /renew commands all day and they are finger snap fast.

However when i boot into Acronis i just get a 169 address. I was just using the standard boot media so i created WinPE media and i got the same thing. From PE i can run the ipconfig /renew and i get the error " unable to contact your DHCP server". I can run again and again and i keep getting the error. I also tried PXE booting, the computer gets an IP just fine in windows, so i can send it a reboot command, PXE runs, it connects and launches into Snap Deploy, but gets a 169 address.

This happens for everything, Master image creator, agent, single deploy. It doesn't seem to matter.
I actually care about PXE the least, it was just another thing to try.

Things i tried so far:
I tried using custom WinPE drivers and finding the exact drivers for my Ethernet, no change.
Booting linux media, PE media, and PXE, same problem in all three.
trying different net cables and switches
Trying legacy boot vs UEFI boot, no change
Configuring Bios for UEFI Network boot, which in the bios states "wakes up Ethernet card sooner"
Adding a 30 second delay when creating media. (but this only seems to work for the agent anyway)

Strange anomaly:
If i just keep rebooting into Snap over and over, i occasionally will get an IP. Sometimes it might take TEN reboots, sometimes i give up after a while and never get it working.

I should also note that we have about 80 of these stations, and i'm having problems with all of them.. It's very tough to image stations when i have to keep rebooting over and over just to get it to IP.

Also, if i manually enter in the IP info and servers, it still doesn't work. So it's almost like something isn't engaging properly.

Anyone have any other ideas?

Di, 09/08/2015 - 19:35
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 2
Kommentare: 5

Well i just wanted to follow up.
Maybe this is just some odd incompatibility with either Dell or this specific Ethernet port and Snap 5.
If we keep rebooting we can get essentially every station to IP maybe.. 1 out of 5.

I did find a solution though, Enabling UEFI Network Stack AND PXE boot in the bios.
Then booting from recovery using Legacy boot. Yes, i configured UEFI boot options, then booted legacy anyway. For whatever reason doing this in the bios of all our stations is now letting Acronis get an IP right off the bat. It does add a few seconds to our boot times, but that's a small price to pay to actually have this work.

Mi, 09/09/2015 - 15:14
  • Anmelden, um Kommentare verfassen zu können