Created on 06-21-2004 09:46 PM
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
ORIGINAL: Adrian Lewis Unfortunately, I have no fix for the fg' s behaviour but: If you were to multihome and add both internal 192 net and 69 net VIP addresses to your DNS servers' interfaces with no default route on the 69 net, when the secondary tries to contact the primary, it should (I think) do the following:You are nothing short of brilliant. It works like a charm, everything propagates between the two servers fine as soon as I put in the external DNS IP into the IP list in TCP/IP properties. Case closed this is now fixed!!!! Just out of curiosity though... are there any security or other implications to having an external IP assigned to the machine along with internal addresses? Just wondering. Thanks again for all your help everybody! I' m so happy right now!
ORIGINAL: MeritWell I found out a pretty good reason to not have an external IP assigned on a an internal server with NAT IP' s.... my server couldn' t communicate with another server (owned by another hosting company on the other side of Canada) that had an IP on the same subnet. Pretty nasty side effect. Anyways, I have re-opened my support ticket as this issue perists and I found another problem it causes.... When one of my mail servers sends out e-mail for a newsletter from a website it sends some e-mails to users on my primary mail server (communicating on the external IP). However, the primary mailserver sees the incoming connection as 192.168.1.1 NOT the proper external IP and marks the message as spam because it fails an SPF check. Yet another side effect of this persisting problem.ORIGINAL: Adrian Lewis Unfortunately, I have no fix for the fg' s behaviour but: If you were to multihome and add both internal 192 net and 69 net VIP addresses to your DNS servers' interfaces with no default route on the 69 net, when the secondary tries to contact the primary, it should (I think) do the following:You are nothing short of brilliant. It works like a charm, everything propagates between the two servers fine as soon as I put in the external DNS IP into the IP list in TCP/IP properties. Case closed this is now fixed!!!! Just out of curiosity though... are there any security or other implications to having an external IP assigned to the machine along with internal addresses? Just wondering. Thanks again for all your help everybody! I' m so happy right now!
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1517 | |
1013 | |
749 | |
443 | |
209 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.