@george1421 Thanks very much for the information. I’ve set up the A records on both DNS servers and everything seems to be working okay in that I can ping ‘fogserver’ from both networks.

I started capturing an image from the Student network but got an error that seems to suggest that a password is wrong somewhere (ftp_login():Login incorrect) so I need to fault find this one. I’ve found a fair bit of info on it so I just need to find the time to sort it out.

Thanks again to every one for the help, it’s much appreciated. I’ll report back once I have a chance to get back to it.

@george1421 Hi George. Yes, each network has it’s own DNS server. There’s no routing between the staff and student networks (that I’m aware of).

Server

• FOG Version: 1.44, 6077
• OS: CentOS7

Client

• Service Version: Smart Installer, 0.11.12
• OS: Windows 10

Description

Hi all,

I have set up our FOG server across two separate networks, one for Staff (10.0.0.X) and one for Students (192.168.102.X) using a CentOS Virtual Machine. I set it up first on the Staff network and have successfully been able to do everything I would be able to do with FOG (it’s great!).

I then added a network card to the FOG server VM and configured it for the Student network. I installed the FOG client on one of the Student PCs, rebooted and set the PC to PXE boot. However, when booting, the Student PC starts the PXE boot and successfully completes the ‘tftp://192.168.102.50/default.ipxe… ok’ step but in the next step it looks for the FOG server IP that’s on the other network ‘http://10.0.0.15/fog/service/ipxe/boot.php....Connection timed out’ and thus fails.

The clients can see the FOG server on the Student network but not the Staff network. Is there any setting to make the Student PCs look on the Student network or make FOG listen on the Student network rather than the Staff network for the http process?

Thanks in advance.