/build/static/layout/Breadcrumb_cap_w.png
01/01/2019 144 views

Main site external Firewall IP =  1.1.1.1 (This is where the SDA is located)
Remote site external Firewall IP = 2.2.2.2 (and RSA is at this site)
RSA internal IP = 192.168.1.50
DHCP at the remote site has the boot server setup as the IP address of the RSA = 192.168.1.50

Since my SDA and RSA for this site are not able to be connected via a WAN at time, I have the firewalls setup at each site to forward ports from the external IPs to the internal devices.  The sync works fine, but when I try to image a client at the remote site I can see that after the initial boot to 192.168.1.50 the client is referenceing the external IP address 2.2.2.2 of the SDA in its downloads.  I can see that it is referencing http://2.2.2.2/....... instead of http://192.168.1.50 after I select my boot option.

The client still images, but I can tell from the speed that the path it is taking by hair-pinning out the firewall and back in is slowing down the process.  The internal switches run at 1GB and the external port on the FW is only at 100Mb.

0 Comments   [ + ] Show comments

Comments


There are no answers at this time