Surface 3 - Unable to obtain DHCP
-
@dylan123 If you mentioned this already, I apologize. But, are you working with a Surface 3 or a Surface Pro 3? Everything in my environment is a Pro. I’m just wondering if we can take different hardware types out of the mix.
-
@Scott-Adams There are also sub-models of each series. Surface Pro 3 has different sub models.
-
@Scott-Adams Yeah Surface Pro 3.
Build version is 14393 for both the 3’s based on what it says in system information.
-
Just giving this a bump to see if anyone else has any other ideas of what I can try?
Ran the latest update again to get 1.4.3 but still no luck.
Using USB ethernet, I get to the stage of unplugging and replugging before getting the error message -
Unplug and replug although when I unplug it says "usb2-port1: cannot disable (err = -32)
Failed to get an IP via DHCP! Tried on interfaces(s):Using the dock with only ethernet connected it just fails to speak with the DHCP.
Both attempts have gone through a dumb switch as well just to ensure they don’t hang without connection to the network.
Maybe it just won’t work with the surface’s I’ve got, just thought I’d give this one final try.
-
@dylan123 Have you tried George’s suggestion about a powered usb 2.0 hub ? You should be able to get one for less than ten dollars online.
-
@Wayne-Workman said in Surface 3 - Unable to obtain DHCP:
@dylan123 Have you tried George’s suggestion about a powered usb 2.0 hub ? You should be able to get one for less than ten dollars online.
I haven’t yet Wayne mainly due to the fact Scott had success with the same adapter I’ve been attempting to use.
That said, I’m willing to buy one to test with as it would be great to be able to create images of our Surface 3/4s with FOG if possible
I imagine I should be able to buy any USB 2.0 to Ethernet adapter or is there a particular model/brand I should be looking at? I’ve been through some of the threads, particularly the one I linked earlier in this thread with Sarge and his Surface 4. He linked an Amazon 2.0 USB to Ethernet adapter but that’s currently no longer stocked so I can’t purchase that (probably take a while for it to be shipped to Aus anyways).
Think I’ll just go with this if I don’t need to be going for a particular brand/model - http://www.msy.com.au/peripherals/15841--edimax-eu-4208-usb20-10-100-ethernet-adapter.html
I could get one with USB ports as well but I’m thinking that might be a chance to cause another issue although it would be nice not having to swap from keyboard to Ethernet quickly!
-
Finally have some success!
I think it’s been a mixture of things that have made it work this time compared to other attempts. I just tried with ipxe7156.efi instead of ipxe.efi which is what I was trying the other day (I know I previously used ipxe7156.efi with no success) and I was able to quick register it and begin the capture process, rather interesting that it was able to do the quick register and create it’s own host kernel argument of the - has_usb_nic=1 without me having to put that in which is nice. Also had a dumb switch in the middle along with doing more updates so I’m not sure what part has fixed it for me but it appears to be working!
Process for mine which is basically very similar to Scott’s well written instructions but will add everything I’ve done in case it helps someone in the future:
DHCP Server Settings
067 - ipxe7156.efiFog Client Version
Upgraded to FOG 1.4.0-RC-4
Upgraded Kernel Versions so both bzImage and bzImage32 versions are 4.10.9Connection Setup
Network > dumb switch > Microsoft Surface Ethernet to USB Adapter (model:1663) > Surface 3/4 (4 I’ve got to the quick register page, haven’t tested further yet).
Left Surface keyboard plugged inSurface BIOS Settings
Turn Trusted Platform Module off
Turn Secure Boot off
Change boot so network is allowed rather than just SSD - Network > SSDChoose whether to quick register a client or capture/deploy an image.
Once all the above is set up then it’s basically how you do any other FOG image apart from having to disconnect and reconnect the USB network adapter.
Steps -
- Ensure setup is plugged in as mentioned in the connection setup above
- Hold volume down, press power on and hold volume down until red Surface screen appears then let go
- Surface should start booting into fog
- When prompted to unplug USB Nic, plug back in and hit the enter on Surface keyboard
- If you’re quick registering, you should be able to select that option. If you’re capturing/deploying, it should automatically begin that process as you’ve set in the task manager on your FOG system.
Thanks for your assistance @Scott-Adams @george1421 @Tom-Elliott @Wayne-Workman
Thinking aloud, I suppose there isn’t really a way to register all my Surface machines because since I’m using the USB adapters and they’re the device that contains the MAC address (as I found out when I tried register the Surface 4 only to find it was listed as the Surface 3 model I did the quick register for before). Not really the end of the world if that’s the case as I can still create the images required and then just deploy it to the Surface as I wish.
-
@dylan123 So if you added
has_usb_nic=1to the FOG_KERNEL_ARGS field in fog settings, this would be the reason you “didn’t have to add it back”. This “flag” doesn’t automatically set itself, so the only way to have it “preset” is if you entered this in FOG Configuration Page->FOG Settings->Expand All->FOG_KERNEL_ARGSI’m glad you got it working and documented what worked in specific sequence. Hopefully all continues to work as expected for you.
What I might recommend, is if you know the nics and which devices they’re going to be attached to, is to take the MAC’s and create a CSV with the MAC and Hostname to tie with it.
This way you can specify the hostnames and not worry about the registration process itself. (I know not optimal but you can ensure all hosts receive the has_usb_nic flag this way.
Your CSV for these systems might look like:
"00:01:02:03:04:05","FirstHost","","","","","","","","","","","","","","has_usb_nic=1" -
@dylan123 I added the link to your solution post in the wiki. One day I (or someone else) can go through it all and make a formal article.
-
@Wayne-Workman said in Surface 3 - Unable to obtain DHCP:
@dylan123 I added the link to your solution post in the wiki. One day I (or someone else) can go through it all and make a formal article.
Sounds great, happy to help if required in more detailed instructions if needed
@Tom-Elliott said in Surface 3 - Unable to obtain DHCP:
@dylan123 So if you added
has_usb_nic=1to the FOG_KERNEL_ARGS field in fog settings, this would be the reason you “didn’t have to add it back”. This “flag” doesn’t automatically set itself, so the only way to have it “preset” is if you entered this in FOG Configuration Page->FOG Settings->Expand All->FOG_KERNEL_ARGSThink I was half correct with what I said, I must have had the host with the mac still added. Interestingly though, I’ve found I don’t need that command for the surface 3s.
- So basically in the config > fog settings > fog_kernel_args section, that’s blank.
- In my host section, it only contains two laptops that are both the HP models I’ve been previously working with, no surfaces.
- I can then turn on any surface 3 and it will boot to the fog menu where I can either quick register it (not much point) or deploy the surface 3 image I took yesterday.
*I did a quick register of the surface 3 given I thought it automatically added the has_usb_nic=1 to the arg section however it didn’t. It still added the surface to my list of hosts though - I then tried with a surface 4, it booted to the fog section but when I selected ‘quick register’ I got then ‘unable to obtain DHCP address’ type error message which suggests for the surface 4, I need to have the has_usb_nic=1 argument.
Just thought it was interesting how that worked, probably come across that though with other people that have been trying to image surfaces.
