How to make an internal website on Lan to be seen on the internet
Hi EE,
I have a home page running that can be seen on the internet. This was set up on a linux box by another admin.
I have another site that is running on a server 2003 serving active pages. This site is running well internally. A link to this site is on my home page but it is not accessed outside of my network. I want it accessible outside.
The site is running iis 6.0 but I dont want it to be accessed directly from the server 2003 but to use the link on the linux box to work.
Can someone direct me to some hints or documents to set this up so that I can access this page outside on the internet.
Thanks in advance.
I have a home page running that can be seen on the internet. This was set up on a linux box by another admin.
I have another site that is running on a server 2003 serving active pages. This site is running well internally. A link to this site is on my home page but it is not accessed outside of my network. I want it accessible outside.
The site is running iis 6.0 but I dont want it to be accessed directly from the server 2003 but to use the link on the linux box to work.
Can someone direct me to some hints or documents to set this up so that I can access this page outside on the internet.
Thanks in advance.
c1nmo
You'll need to configure your routers/firewalls to allow external access, what do you have in place?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can apparently map files on another server into the Apache web server. http://httpd.apache.org/docs/2.0/mod/core.html#directory Permissions have to be set on both servers to allow this to happen. Something like this:
<Directory "REMOTESRVR/VOL1:/data/wp">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
I think what he might be saying is he wants links from the Linix box to be able to hit the Windows box. If that's the case it should be possible using the referrer to block any hits that don't come from the LInux box. Without an example it's hard to tell.
Mapping via Apache is pretty cool though. Good to know.
Mapping via Apache is pretty cool though. Good to know.
ASKER
Thanks, here are some more information.
My LAN network address is 10.1.1.0/24
The address of my 2003 server is 10.1.1.5
The linux box is my default gateway and serves as my firewall which has the external interface to my ISP
I can access my internal website via "10.1.1.5/link_to_inetpub/
On the linux box is a static html page that has links to 10.1.1.5/link2MyActivePage
On the server 2003 is also a dns server that does my name resolutions for me.
I can understand the logic behind the first two comments and they make perfect sense.
Its just how to go about it as I havent done this before and a bit lost.
Do i have to do something in iis or is it a dns thing where I have to have a FQDN to mapped to 10.1.1.5 as this is not recognised on the internet? Any more thoughts most welcomed.
My LAN network address is 10.1.1.0/24
The address of my 2003 server is 10.1.1.5
The linux box is my default gateway and serves as my firewall which has the external interface to my ISP
I can access my internal website via "10.1.1.5/link_to_inetpub/
On the linux box is a static html page that has links to 10.1.1.5/link2MyActivePage
On the server 2003 is also a dns server that does my name resolutions for me.
I can understand the logic behind the first two comments and they make perfect sense.
Its just how to go about it as I havent done this before and a bit lost.
Do i have to do something in iis or is it a dns thing where I have to have a FQDN to mapped to 10.1.1.5 as this is not recognised on the internet? Any more thoughts most welcomed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If your ASP pages connect to Access or SQL Server, Apache on Linux won't be able to help you. There are no acceptable drivers for either one on Linux. You have to have direct access to the Windows server to use those.
That's not what a proxy does. It simply rewrites URLs and serves as a HTTP proxy for the website.
IT Routes requests based on host headers and you don't need SQL drivers. It's just HTTP :)
IT Routes requests based on host headers and you don't need SQL drivers. It's just HTTP :)
Yes, but one of my suggestions was to make the files on Windows be a remote directory for Apache on Linux. If they are ASP and / or access the databases, then they would not work as a remote directory under Apache on Linux.
To use a proxy, the question becomes how do you expose a LAN site to the internet when it does not have an Internet domain name.
To use a proxy, the question becomes how do you expose a LAN site to the internet when it does not have an Internet domain name.
ASKER
Thanks for directions simonlimon and DaveBaldwin.
Issues been resolved now by making an A record with FQDN that is acceptable on the internet. ie www.activepage.website.com with external ip address on the linux box. An rproxy is then used to point back to the servers ip address.
Issues been resolved now by making an A record with FQDN that is acceptable on the internet. ie www.activepage.website.com with external ip address on the linux box. An rproxy is then used to point back to the servers ip address.
ASKER
Points allocated to WiReDWolf, simonlimon and DaveBaldwin. Thanks for the leads;)