Posts made by JTech

@george1421 lol Well thank you for the Laugh but I will try that and see if that resolves it.

@george1421 but why would it work correctly before and suddenly change

@george1421 nope it looks the same way 0.0.0.0.0.0.:51667 0.0.0.0:*

@george1421 it says ok in Green

@george1421

@george1421

@george1421 do you know and easy command to tell if the service is running

@george1421

When I set the Ubuntu up it asked if I wanted to use there DCHP server so I would say the Ubuntu DCHP service

sorry I geuss the other pic was to large in size but this is what I get when trying to boot PXE

Fog server
Ubuntu 16.04
Tue Nov 01, 2016 14:44 pm
Running Version 1.3.0-RC-14
SVN Revision: 5974

Client

• Service Version: N/A
• OS: Windows 7

Description

Ok so this is a simple network a Fog server set up with a switch one client PC and one other PC to get to the GUI.
For the actual problem now it seems that when I initially set up the server it will work until I reboot it or shut it off then the clients PCs/hosts can not get a PXE Request from the Fog. But (please note it was working with no problem before the restart.)
Please assist

you guys can mark this as solved I posted how I resolved this issue above

@JTech said in HP ProBook 650G2 (2016 model ):

OK so first off a little about are FOG set up

1. Fog 1.2.0
   2.Its SVN Trunk version, simply the latest stable version
   3.FOG was installed on Ubuntu 14.04.3 LTS

Ok now to for the issue I am trying to register a New HP ProBook 650G2 to are fog system so that I can upload and download images. however when I attempt to register the HP it gives me the fallowing error

tsc: Fast TSC calibration failed

Then it acts like it is going to register then it says the fallowing

Unable to register host for the following reason: (blank dose not give any reason)

then is goes a little further and try to send inventory…

Any help on this would help me out greatly we really like the FOG Project and would really like this to work on these new computers. We are going to be buying a lot of these units so again it would be awesome if you could you guys could shed some light on this.

Ok I resolved this and here is what it did
I ran a capability test on the computer it self and found this to be a network issue as we already knew this. However I notice that the Kernel hasn’t been updated in a while so I went to the fog management counsel under configuration tab I went to kernel updater and up dated the kernel. there are many to chose from in you can research what you need for your environment but I choose the most recent 86_64bit version (4.1.2.64 ) this instantly allowed the computer to register and take the download / and upload of the image.

Hopefully this help other people with this issue and I want to thank everyone that helped with this

@Sebastian-Roth said in HP ProBook 650G2 (2016 model ):

@JTech said:

it is running from a windows computer if you still need hardware ID vend and dev please advise on where and how to obtain this information

Device manager -> Network card -> find the corrrect one and right click -> Properties -> Hardware … (see I am a linux guy so I am not exactly sure if this is absolutely correct. I am sure you’ll find it or try google on how to find the IDs of your NIC in windows).

I am wondering if this is another one of these awkward NICs. Can you please connect the client to your main network using a small dumb mini switch? See if the issues goes away then.

ok the NIC is an Intel Ethernet Connection 1219-V

The hardware IDs are as fallows
PCI\VEN_8086&DEV_1570&SUBSYS_80FD103C&REV_21
PCI\VEN_8086&DEV_1570&SUBSYS_80FD103C
PCI\VEN_8086&DEV_1570&CC_020000
PCI\VEN_8086&DEV_1570&CC_0200

@Tom-Elliott said in HP ProBook 650G2 (2016 model ):

No dice as in?

You updated the boot file to use the proper items?

yes that is correct I updated the boot file to use the proper items

@george1421 said in HP ProBook 650G2 (2016 model ):

So let me understand (for both of you), you can get into the iPXE menu OK? You can pick register, the FOS client engine gets downloaded and starts running but it can’t communicate on the network.

What happens if you manually register that target computer then schedule a debug (capture/deploy the case doesn’t matter) to that computer. Press enter a few times at the wall of text and it should drop you at a command prompt.

Then key in ip addr show Does it pick up an ip address?

If not, from a running windows computer, can you get the hardware ID vend and dev?

1. As you said above it appears that there is a lost of communication however I am able to get through the process with other model computers that we have here.

2. When I go about registering manually it will come up so the FOG is seeing the PC however the PC runs through its process then when I try to hit enter it goes straight to the bottom and say tsc: Fast TSC calibration failed it will not let me go to the command prompt part

3 it is running from a windows computer if you still need hardware ID vend and dev please advise on where and how to obtain this information.

Also is there a way to attaché screen shot to this forum I could give you images that show you exactly what I am talking about.

OK so first off a little about are FOG set up

1. Fog 1.2.0
   2.Its SVN Trunk version, simply the latest stable version
   3.FOG was installed on Ubuntu 14.04.3 LTS

Ok now to for the issue I am trying to register a New HP ProBook 650G2 to are fog system so that I can upload and download images. however when I attempt to register the HP it gives me the fallowing error

tsc: Fast TSC calibration failed

Then it acts like it is going to register then it says the fallowing

Unable to register host for the following reason: (blank dose not give any reason)

then is goes a little further and try to send inventory…

Any help on this would help me out greatly we really like the FOG Project and would really like this to work on these new computers. We are going to be buying a lot of these units so again it would be awesome if you could you guys could shed some light on this.

we are still working on this and have made progress but it is still happening

Kelly m post with the picture is doing exactly what my system is doing. hope fully this clear some stuff up there are no error code in this process.

@george1421

it reads 1.2.0

1 fog is 1.2.0
#2 im not sure how would I verify that
3. The image was a uefi (we upload this image from pxe via Ethernet)
4 I m running the fog on a Ubuntu