I tried to change that and it did seem to limit the number of computers that can image at once. But it did still allowed 10 computers (I believe that was the amount) to be inprogress as snapins vs checked in or queued.

I have found where you can limit the max clients for imaging. Is there a way to limit how many snapins can be in progress at once? If I have 100 hosts check in, FOG seems to allow 10 at a time. I have a batch file that downloads a large amount of data from a server and would like to limit this to 2 clients at a time so I don’t overwhelm the network bandwidth.

@Sebastian-Roth Below is the configuration I am using. If I changes the storage node IP Address to the internet networks IP it will work but then replication does not work. ![0_1561473109851_Image Attempt.png]

@george1421

Here is my setup:

Master Server: 10.10.1.3
Node : 192.168.1.2(Local Network)
IP of node from Master Server Network: 10.10.1.4 (ports forwarded to 192.168.1.2)

I don’t actually have 2 network cards in the node. The servers are on two separate networks. I have opened ports to allow the replication and set the node ip to 10.10.1.4 but then when I go to image it tries to mount the image location on the node using the “public ip” (10.10.1.4) side of the gateway. This causes a connection refused message due to no loopback.

On the other hand. I can tell the Master server the node ip is 192.168.1.2.
This results in replication not working but imaging via the local node is successful.

Your example of 2 nics though would produce the same issue I believe.

OK so understood about configuring using Hairpin NAT. If some of my sites/labs do not have the ability to do the hairpin NAT, is there no way to have the Master use the WAN IP for replication and then have it pass the local LAN IP of the node during imaging to the client being imaged?

This would let me support the sites that cannot do the Hairpin Nat and also just in general stop me from altering the routers at 50+ sites.

I do have NFS open on the firewall with port forwarding to the local ip.

When trying to mount the imaging folder is shows the path as “[external IP]:/images/ on /images failed: Connection Refused”

If on the master node i change the IP of the node from it’s WAN address to it’s Local address. This breaks replication but fixes imaging.

I’m have a storage node that exists on a separate network. For replication I have to put the WAN side IP for the master node to push replication to the node on the sub network. For imaging though, if I do not have the LAN side IP set for the node it tries to contact the WAN IP and fails.

Is there a way for replication to use the WAN IP and for imaging on that node to use the local IP?

It is failing at the point where it tries to mount the images folder and is using the WAN IP.

@Sebastian-Roth Thanks for the quick reply! If that is the case, which ports need to be accessible between networks/vlans for the replication to occur? I have several networks onsite and would like to allow replication to a node on each network.

I was wondering which device initiates the pole to see if anything needs to be replicated. Does the node poll the master or does the master push changes to the nodes as they happen?