Posts made by cnkpadobi

this is the last screen before rebooting… this is after I manually register the the host on the fog server

Running Version 1.3.4-RC-2
SVN Revision: 6063

Client

• Service Version:
• OS: Windows 7
  When pxe booting a Lenovo M90p | 5498WDH and Intel DQ57TM. All other machines work fine.![alt text](![image url](!

When we pxe boot machine we reached the registration screen. We select quick or full registration it acts like it going to register but the screen just reboots. if you pxe boot again it says host not register and nothing took affect.

Then we try to manual register it and it registers fine but when we assign a task and deploy image it just reboot see image.

Any help is appreciated thanks

Hello

Ok I will try to upgrade… Should I upgrade also the latest Ubutu 16.04 is there any issues with Ubutu and FOG

I uploaded an image to the server from one of my Lenovo machines. It was done successfully… Then I tried to deploy the image to a different Lenovo computer. The computer registered. It goes through the motions as if it will image the machine but then stops. I have included pics for more understanding what is happening. Deploy image just keeps restarting and will not complete successful

.

Can’t seem to get my machines to deploy image just keep rebooting… Not sure what i am doing wrong     

Thanks for the help…

I have another question, I have one machine is that is on a continuous loop.
Seen pic for the last screen before it loop. This was a machine that I tested and took  image on before.

And will not get to the quick registration screen. Lastly is there a way to set the fog registration screen with the options to stay a bit longer?

So DHCP is done is on each subnet.

The Main one we been working on is 192.168.0.x
One of the sub sites 10.10.1.x

However the subnet and the main site is connect by MPLS Network

no not all we have 15 different location as well.

How do I setup for my network to received computers from the different subnet.

question was looking at the wireshark file. Since it has so many ip address in it… was thinking it may be picking up my voip phones as well… Is that possible?

ok got it to pxe boot… seems to work somewhat.

Was able to take image but still having issues deploying0_1478830627175_output.pcap

hmmm… ok why would the other machines not boot? will try to get another log file

Ok follow the steps.

1. Turn off the watchguard DHCP options.
2. enable dnsmasq on server
3. Got the first machine to pxe boot and was able to take snapshot of the machine.

While taking a snapshot of the machine, I decided to see if I can pxe boot and register another machine.

HOwever, I got the origal mesage again… HOwever the other machine is still working.

Here is a capture of my log files 0_1478826719275_output.pcap

ok thanks

Here is the file…0_1478723712526_output.pcap

I am not sure if I am doing it right. However when I ran the tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011 it did not report anything back after pxe booting the machine.

yes I setup dhcp options already

@george1421

DHCP is done by my firewall… Its a watchguard firewall.

My DNS is on a windows Server
Yes, all targeting the same network

I am actually getting a different message.

So I tried to pxe boot two different type of machine

1. Hyper V machine I got the above PXE-E51 error
2. Stand alone box I get the follow error : PXE-E32 TFTP Open timeout

Also when this is fixed I wanted to make sure that my remote sites that are on the 10.10.x.x networks to be able to reach the imaging machine for imaging as well.

Yes, that is the Fog Server Ip

Yes dns is being handed out in the 192.168.0 range.

I am using version 1.2.0

I am running
ubuntu 14.04.5 LTS
No firewall enable and Does Selinux need to be enforced?

Hello, When I try to take an image of a machine, I keep getting this message.

PXE-E51: No DHCP or proxyDHCP offers were received.

NOt sure what I am doing wrong

I have an inhouse DNS and DHCP server already setup.

Please help

here is my /etc/dnsmasq.d/ltps.conf file.

# Sample configuration for dnsmasq to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCP
# server is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename.
dhcp-boot=undionly.kpxe,192.168.0.253,192.168.0.253

# rootpath option, for NFS
dhcp-option=17,/images

# kill multicast
dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 0

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from network", undionly.kpxe

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.0.253,proxy

# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h

# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

Tom Elliott – Edited to wrap the code in triple backticks so we can actually read the config more properly.