@george1421 Thanks for the guide. I’ll work through this and get back to you if things go well or if i run into any problems. I should of followed the set up like this when i started because the current fog .32 i’m using is set up like that. The management side has a 192.x.x.x and the fog deployment has something like 10.x.x.x
Again I really appreciate the help. Thanks!
@george1421 UPDATE: I followed your instructions and I got my system to work exactly how I wanted it too. I really appreciate the help. Thanks again.
Unfortunately I ran into a small hiccup during the deployment process. You’ll see the post soon once I get the photo uploaded haha.
@Sebastian-Roth I really appreciate the help. Let me know if you need any other pieces of information. And also as an update, I updated to git 7799 to see if that fixed the problem, however the issue still remains. Thanks.
Alright so I started from scratch. I took this image from my old FOG 0.32 Server and deployed this image onto a client. I watched it image and noticed that all the partition sizes appeared correct. When I was able to get to the client machines desktop, I looked at the disk management and also noticed all the partitions were the correct size.
Unfortunately I can’t test what happens when I try to capture this same image to the new FOG Trunk Server. My capture is failing on the 3rd partition everytime. I get a “extfsclone.c : bitmap free count err, partclone get free:655082 but extfs get 2418133”. I’m trying to fix this now.
But here’s the output you requested. I don’t know if this effects the fact I can’t actually upload the image in the first place. This was ran from the client machine running the debug mode from the new FOG Trunk server.
Yeah…umm, I said screw it and did a wipe and fresh install on the entire thing. I can pxe boot fine now. I am however run into an image capturing issue but i’ll save that for another day or post if I can’t figure it out.
I appreciate the the help.
My fog server does have to 2 nics. I’m pretty sure I configured those right. I had a separate post and another fog project moderator helped me through the process and got it working perfectly.
I really think something in that software update I did messed something up. Thats literally the only change I made in that 3 week period between it working and not working.
So i unplugged the fog server from my local network and rebooted the client machine. When it started it back up again, it still had the same IP address and pointed back to the fog server as its DHCP server.
@ITSolutions I unplugged my fog server from the network and on my client machine it shows the DHCP server to be the fog server.
@Quazz I have one router but my fog server doesn’t need internet access. I use it just for imaging. The fog server does get Internet through one of its NICs but thats just for browsing/convenience. I had set up the fog server to be separate from my local network to be used just for imaging.
@Wayne Workman You wanted a picture of it or the actual file? I just ran a cat /etc/dhcp/dhcpd.conf and snapped a photo.
Worst comes to worst, I’ll just have to do a fresh wipe and reinstall everything.
@Quazz To my knowledge, there is no other dhcp server.
And that link should just be a picture of whats in my dhcp config file.
@Wayne-Workman @ITSolutions @Quazz
I think I just installed the ISC-DHCP and start/enabled it. I didn’t need to configure it at all because at the time everything was working fine.
I’ve also tried restarting the both the isc-dhcp and tftp-hpa service multiple times.
The only major change I can think of that might have messed something up is when I did an update (not a manual apt-get update in the terminal, but when I turned on the machine and a window popped up telling me there are updates available for install).
And i don’t think it’s the switch. Because if i connect a client machine directly from the fog server machine, I get the same issue.
Here’s the output of the dhcp config file.
0_1466602264751_pic1
I’m running Ubuntu Server 14.04. Three weeks ago it was running fine. I could connect any client machine, it was able to get an ip address, and pxe boot. I literally just stopped and stepped away from it for three weeks. I came back because I had to image something, I figured hey this new fog server is faster than my old one, let me use this one. And thats when I came across the tftp error. I was running git version 79** something, I can’t recall.
My fog server is isolated on its own separate network. This is being used only for imaging purposes but i have the isc-dhcp server running on it to hand out IP addresses.
I’m running into this “PXE: TFTP open timeout” error when I try to pxe boot a client machine.
My DHCP server is working because every client machine I try is getting its own IP address. I’ve restarted my TFTP server, gave everything in the /tftpboot directory 777 permissions, and disabled the firewall. The TFTP password/user name is set correctly also.
I can ping the fog server from the client machine but I can’t ping from the server to the client. I even tried updating to the latest git version (8203). The current version I had wasn’t working either so I thought maybe an update would fix it. I was running 79** something.
I don’t know what’s wrong. It worked fine 3 weeks ago. I stepped away from it to do something else and when I got back, I get this error on every machine I try to pxe boot into.
I’m going through the wiki troubleshooting guide for TFTP but I can’t find the fix.
@Sebastian-Roth I apologize for the long delay. I had to step away from this for another project.
And yes you have the set up correct. I deployed the image from my old FOG 0.32 to a client machine. Then using the new FOG I uploaded the image from that same client. During the deployment while using the FOG 0.32, all three partitions are the correct size. But when I upload it to the new FOG, I can see the second partition shrinking. I tried repeating this process with other images (7 in total) and only one other images has this issue. The others are all correct.
And yes the d1.partitions picture I uploaded is from the new FOG trunk server. The image directory from my old FOG 0.32 does not have a d1.partition file. In each image it only contains a d1.mbr, d1p1.img, and d1p2.img
I’ll upload the photo of the output you’re requesting however something has gone wrong and now I can’t even pxe boot any client machines. I’m getting the TFTP open timeout error. I gotta figure this issue out first before I can run the debug mode on the new server.
@Sebastian-Roth I’ll get you all the info and pics whenever I have a chance to sit down and thoroughly record/repeat the process that lead to this hiccup. Just give me a bit of time, thanks.