I'll do my best to explain this. We (CompanyA) have a site to site VPN tunnel with CompanyB. Because CompanyB is a large, public company, there are lots of policies and red tape to deal with. For instance, even though we have a VPN configured, they require that each of CompanyA's resources be NAT'd on CompanyA's firewall and that all traffic that comes from CompanyA's resources appear to come from this public IP address, NOT the internal LAN address. I got over that one...It was a pain, but easy enough. The problem that has me banging my head against the wall is this:
- CompanyA provides an internal webpage that hosts all our content on a SQL back end.
- CompanyB can access this resource as requested, by using the public IP I used in the
NAT policy for this resource.
- The webpage has thousands of links to other documents hosted in the database.
These links all point to http://internal_server_name_/blah/blah/blah.pdf
- Because they require the public address, they cannot resolve "internal_server_name" to
anything, therefore cannot open the links. The same applies when CompanyA
employees want to send links to the webpage via email.
Anytime a link is sent to CompanyB, the employees at CompanyA must manually change the link to read: http://servers_public_ip_address/blah/blah/blah.pdf
. Like I said, there are thousands of links, which all point to the servers internal name, so changing everyone of those is out of the question.
If anyone can help me figure this one out, I'll owe you big time.
We are at a stalemate at this point. They refuse (or are just too large a company) to agree to just be done with the public IP and use the internal IP, which would solve all the problems. I've exahusted all my resources trying to come up with a resolution for this, but I'm just banging my head against the wall.