PXE Boot Problem
-
I setup a brand new FOG server. I’m using version 1.5.2. When I attempt to upload a new image from a Windows 7 laptop, it times out (for lack of a better term) at the point where it’s looking for DHCP. My FOG server is not on my network. I have the FOG server setup to manage DHCP. I used this setup in the past and it worked, so I’m sure I’m just missing something obvious. The FOG management console PC is able to see the FOG server, and I’m able to ping the FOG server from the laptop I’m trying to upload. Any ideas would be appreciated. Thank you.
-
@digital-dog You have a conflicting description in your OP.
When I attempt to upload a new image from a Windows 7 laptop, it times out (for lack of a better term) at the point where it’s looking for DHCP.
My FOG server is not on my network.
Just so I understand you have fog configured on a dedicated imaging network and not connected into your business network. Do I understand that correctly?
FOG is your dhcp server for your dedicated imaging network
If the client isn’t able to pick up a dhcp address how can your laptop ping the fog server?
Does your fog server have more than 1 network adapter installed?
A screen shot of the actual error would help with the context of the error.
-
@george1421 When I setup FOG, I gave it a IP address of 10.1.10.13, a router address for the DHCP server of 10.1.10.1. I’m reviewing the procedure I’ve used in the past and realized I was never asked during the FOG installation to provide a DNS address on the DHCP server and client boot image. Is that possibly the issue
Sorry, I misspoke when I said the laptop could ping the FOG server.
Yes, my FOG server has 2 network cards installed
I tried to upload a screen shot several times, but it wont let me. The error reads…
No DHCP or proxyDHCP offers were received.
Thanks.
-
@george1421 I’ve attached a screen shot of the error message. When I setup my FOG server in the past, I was able to setup and IP address for the FOG server, a router IP address for the DHCP server, and an IP address to be used for DNS on the DHCP server and client boot image. With the newest installation of FOG, I was prompted for everything except the IP address for DNS on the DHCP server and client boot image. I’m guessing this is the problem. Does anyone know how to set this up with the new version of FOG? Am I missing something obvious? Thanks.
-
@george1421 sorry, correct image attached here0_1525264255931_IMG_1227.pdf
-
I’ve abandoned my plans to try to setup the server as a standalone. I’m now getting the IP addresses from my DHCP server. When I attempt to boot a laptop to upload and image, I receive the attached TFTP error message. I’ve combed though the forums looking for a solution, but had no luck. Any suggestions anyone can provide would be greatly appreciated. Thank you.
0_1525291384570_IMG_1230.pdf -
@Digital-Dog I guess you need to tell us more about your network setup for us to be able to help you. In the latest picture I see two completely different IP addresses. Why is this. What is your FOG server IP? Which one is your DHCP server?
-
@sebastian-roth The majority of my servers are hosted off-site and have the 10.4.58 IP range. Any devices located in my office, such as my FOG server, have the 192.168.30 IP range.
FOG server - 192.168.30.16
DHCP server - 10.4.58.10My original plan was to upgrade my current FOG server and keep it as a standalone server. However, when I couldn’t get that to work I decided to go this route. Any assistance you can provide would be greatly appreciated. Thanks.
-
@sebastian-roth it’s working now. I had the wrong bootfile Name in option 67 on my DHCP server.
