Troubleshoot TFTP - Revision history

Wayne-workman.28155: /* Please enter TFTP server */

2016-10-12T16:05:54Z

‎Please enter TFTP server

2016-10-12T16:05:33Z

‎Common problems and fixes

2016-05-08T00:42:04Z

‎Ubuntu:

2016-05-08T00:35:16Z

‎Fedora 20/21

2016-03-26T18:46:53Z

‎Testing TFTP

2016-03-24T18:56:17Z

‎Testing TFTP

2016-01-19T05:07:25Z

‎Common problems and fixes

2015-10-04T17:21:01Z

‎Ubuntu:

2015-10-04T17:20:42Z

‎Fedora:

2015-10-04T17:20:15Z

‎Fedora:

@@ Line 243: / Line 243: @@
 {{:My problem isn't in the WiKi!}}
-=== Please enter TFTP server ===
+=== Please enter tftp server: ===
 ==== Description ====
@@ Line 256: / Line 256: @@
 Another cause of this problem, although less common, is that Option 066/next-server is not configured on the only DHCP server in the environment. Find instructions on correcting this here: [[Modifying existing DHCP server to work with FOG]]
 === Failed to load libcom32.c32  /  Failed to load COM32 file vesamenu.c32 ===

← Older revision		Revision as of 16:05, 12 October 2016
Line 242:		Line 242:

	{{:My problem isn't in the WiKi!}}		{{:My problem isn't in the WiKi!}}
		+
		+	=== Please enter TFTP server ===
		+
		+	==== Description ====
		+
		+	When trying to network boot to FOG, you are presented with a prompt similar to the below picture:
		+
		+	[[File:Please enter tftp server.png]]
		+
		+	==== Solution ====
		+
		+	Typically this is caused by two or more DHCP services running on one network, and one or more of them being incorrectly configured for FOG. The administrator may or may not know of these DHCP services, one or more of them could be a rogue DHCP service. You can find a rogue DHCP service by running Wireshark on a computer and applying the filter <font color="red">bootp</font> to only see DHCP traffic, and then doing several IP releases and renews. Any rogue DHCP service should show up in the replies.
		+
		+	Another cause of this problem, although less common, is that Option 066/next-server is not configured on the only DHCP server in the environment. Find instructions on correcting this here: [[Modifying existing DHCP server to work with FOG]]

@@ Line 127: / Line 127: @@
 # Note: TFTP_ADDRESS=":69" is also valid.
 # "0.0.0.0:69" means to use any interface while ":69" means to use anything.
+#
 </pre>

@@ Line 46: / Line 46: @@
 == TFTP Service ==
-=== Fedora 20/21 ===
+=== Fedora 20/21/22/23 ===
 status/enable/restart

@@ Line 16: / Line 16: @@
 Normally, you can use your Linux installation medium to live boot on another computer.
-<pre>tftp -v x.x.x.x -c get undionly.kpxe
+<pre>tftp -v x.x.x.x -m binary -c get undionly.kpxe
 Connected to x.x.x.x (x.x.x.x), port 69
-getting from x.x.x.x:undionly.kpxe to undionly.kpxe [netascii]
+getting from x.x.x.x:undionly.kpxe to undionly.kpxe [octet]
 Received 89509 bytes in 0.0 seconds [84047115 bit/s]
 </pre>
@@ Line 24: / Line 24: @@
 === Try to get a file with Windows ===
-<pre>tftp –i x.x.x.x get undionly.kpxe</pre>
+<pre>tftp -i x.x.x.x get undionly.kpxe</pre>
 ==== Testing using Windows ====

@@ Line 10: / Line 10: @@
-=== Try to get a file with Linux: ===
+=== Try to get a file with Linux ===
 This is ran from a separate Linux machine, NOT your FOG server.
@@ Line 22: / Line 22: @@
 </pre>
-=== Try to get a file with Windows: ===
+=== Try to get a file with Windows ===
 <pre>tftp –i x.x.x.x get undionly.kpxe</pre>

← Older revision		Revision as of 05:07, 19 January 2016
Line 270:		Line 270:

	Please see this article for more details about the various boot files available in fog: [[Filename Information]]		Please see this article for more details about the various boot files available in fog: [[Filename Information]]
		+
		+	=== Could not boot: Connection timed out (http://ipxe.org/4c0a6035) ===
		+
		+	==== Description ====
		+
		+	You get a timeout error, either after installing or updating the FOG server, or after changing the FOG server's IP address.
		+
		+	The error is similar to the picture below:
		+
		+	[[File:WrongIP for iPXE.png]]
		+
		+	==== Solution ====
		+
		+	Edit the file <font color="red">/tftpboot/default.ipxe</font> (it's a text file)
		+
		+	Somewhere around the bottom of the file, you will see a line that looks like below, where x.x.x.x should be your FOG Server's current IP address. If the IP is wrong, fix it and save the file.
		+
		+	<pre>chain http://x.x.x.x/fog/service/ipxe/boot.php##params</pre>
		+
		+	Also edit the <font color="red">/opt/fog/.fogsettings</font> file to make sure you have the correct IP address assigned in there, so that when you update in the future, this doesn't happen again.
		+

	=== Unable to connect to tftp server ===		=== Unable to connect to tftp server ===

@@ Line 132: / Line 132: @@
 To edit /etc/default/tftpd-hpa:
 <pre>sudo vi /etc/default/tftpd-hpa</pre>
 Explanation of settings for /etc/default/tftpd-hpa:
 <pre>man tftpd-hpa</pre>
 == FOG Configuration (web interface) ==

@@ Line 103: / Line 103: @@
 <pre>sudo vi /etc/xinetd.d/tftp</pre>
 Explanation of settings for /etc/xinetd.d/tftp:
 <pre>man xinetd.conf</pre>
 === Ubuntu: ===