Problem solved.

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options

Was the part I needed. Thanks!

@george1421 Perfect, thanks. All working now.

@sebastian-roth I see, also i am now able to manually enter clients. This thread is solved. Though i hope the next update fixes this issue.

Sorry for the delayed response! We were very swamped with semester start at the middle of August, in addition to just opening a new Center for Science and Health Professionals with tons of new hardware. I didn’t get a chance to test out the new DLL but I was planning on it… until a hurricane hit us and we’ve been closed for over a week and won’t reopen until after Labor Day (I’m located in Houston).

I will at some point test it out and let you know how it goes. Until then I will say that FOG has been an absolute champ and has made my life so much easier for this semester start. I have no clue what I would do without it.

@mikec96 said in Isolated Network Connection Issues:

Even though I entered 192.168.1.1 into the Server IP address setting, FOG was actually using its previous IP when it was connected to the internet (which was 192.168.1.35).

Did you manually change the server IP after/while running the setup? FOG does not change it for you! FOG uses the IP address in several places internally but it wouldn’t change the actual IP configured on the interface.

Possibly you will run into one or the other issue with the changed IP. So please take a read through this as well: https://wiki.fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address

You’re right we implemented a new FireWall and this IP was being blocked. Thanks!

I worked with the OP via IM for a bit and we have things working for dhcp. The root cause is the dhcp config file had a wrong subnet scope defined (10.x.x.x) where the fog server was on the 192.168.1.x subnet. Once we got the configuration file fixed the target computers pxe booted without issue. At this point the OP can pxe boot the computers. He has an issue with imported images from FOG 1.2.0, but that is a story for a new thread.

@msi Yep looks good now.

This is solved from a FOG point of view.

The problem was that a user replicated several large images overnight and Hyper-V expanded the VM, choking the main servers.

Thank you for all of your help @Sebastian-Roth!

@wayne-workman

Agreed on all counts, plus I don’t have images that need deleting at present to test, nor time to create images just to test deletion (at this point). I’ll check this as the opportunity presents itself.

thanks to all.

Jim

@J-Fog Any news on this? Please post the full fog.log as requested by Wayne.

@thebrennan47 Any news on this? The wrong IP is probably set for the Storage Node in the web UI. Go to “Storage Management” and edit the Storage Node (usually called “DefaultMember”).

@jglessner So is this save to be marked as solved or do you still have that issue? Feel free to open a new thread in case you run into a new issue. Better to open a new one and not mix up things in one case.

This seemed to work! Thanks!

@wayne-workman

Hi,

Finally I was able to install the Fog on Centos7 with little tweaks. Because of Proxy server remiphp56 was not installed so after the fog installation I have to uninstall Php5.4.6 and Install PhP 5.6 for fog 1.4.4 to work.

Thanks
Sudheer

@richard-wise Right that is usually the case when windows is involved. There are a couple of ways to side step the issue.

Not use windows at all. Use Notepad++ on windows Once the file gets to linux unaltered, use the linux command dos2unix to scrub out any remaining Windows bits left behind.

With that said, well done on the debugging!!.

With help From Geroge1421 we discovered that there was a rouge DHCP server connected to the network. It was running from a VM on a regular PC. Network admins were able to locate the port relates to the MAC address of the rouge server.

Now PXE is booting to FOG smoothly

That did it! Thank you guys!

@Brian-Hoehn From the postings of the other users it seems like the new init files Tom provided did help. So I suppose you see a different issue here. Please open a new thread and post all your details there - FOG version, OS version, picture of the error on screen, …