Is this your problem? The AS/400 on the outside of your fire wall has a public IP address. And when it needs to get to the AS/400 behind the fire wall it points to your fire wall's IP address which sees it on port 80 and forwards it to your AS/400 behind the fire wall. And when they hit a part that is behind the fire wall the URL is changing to your fire walls IP address or name. And the fire wall has two ports one for your lan and one for the Internet. And how this traffic is handles depends on what connection it comes in on. Now if it was all on one AS/400 I would say set up two domain names one for external users and one for internal users. Such as www.company.com and www.company.net but you are starting off on one AS/400 and letting it transfer traffic when it hits a certain section or CGI program. I am not sure how you can handle this short of having something (Java script or CGI) on the web server check what IP address the client connected on and then format the URL based on that. Or you could do something I really do not recommend is to have an internal DNS that points to a different IP address then the external DNS points to for the URL passed back by the first AS/400. John Ross At 03:34 PM 12/9/2002 -0700, you wrote:
We have a windows 2000 web server outside our firewall hosting our external web sites but we have web servers that run cgi programs and other portions of the web sites on AS/400's behind the firewall essentially spreading our web sites over multiple machines one outside and one inside our firewall. The problem we have is that we don't know how to assign DNS exactly the same to internal and external users. Has someone done this and can you tell me how.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.