fog unable to register host for the following reasons
-
Try to pull the power on that computer (cord or battery) then hit the power button a few times, then hook it back up and try again… Just a shot in the dark.
-
Tried that first time it happened it was at a school campus we have since brought it back to my office for trouble shooting.
-
Most commonly, when I see “Unable to register for the following reasons: (((((BLANK)))))” it’s because the system failed to pickup IP.
-
What is the computer that is failing to register? Such as Make/Model/NIC?
-
HP prodesk 400 G1 MT with a realtek PCIe GBE NIC identical PC’s register fine it seems to be an issue with this one only.
-
@Joseph-Hales What happens if you try to do a manual web-interface registration?
-
It registers but does not image as described in the first post.
-
Oh duh… sorry… RTFM.
Is it a desktop? Do you have an ethernet card you can put in just to get imaging done?
Maybe try a Firmware update??
-
Ok traced it to a switch or cable issue something about fog won’t successfully image on a port that for all appearances is fine network boot works but when it reinitializes the connection to image it fails is the best guess but even a fluke netscanner cant find any issues with the connection.
-
I have seen this at the campus level but switching ports or cable fixed it and I chalked it up to a bad cable but when it happened today I tested the cable every way I can think of and find no issues with it.
-
It sounds, to me, more likely then it’s an issue with the NIC on the system, not a switch or cable problem.
I too have seen these issues before, and normally changing out the patch and/or port as needed, all works fine. I have, too, seen that it was the NIC and had to process the system under warranty. It’s rare, but it can happen. Based on your findings and description I’m going to side more specifically an issue with the onboard nic.
-
So now - try that port with a different system and see what happens.
-
I’m solving this thread. The reason your systems were failing to register wasn’t, specifically, a problem with FOG directly, but seemingly specific to this one system. Does this sound correct?
