At 09:11 AM 5/27/00 -0400, Brian Chabot wrote:
>Other than allocating a special port for the new server, is there any
>way we can have 2 local (192.168.x.x) web servers talking to the outside
>world on port 80? Our ISP is VERY against issuing a second IP, so that
>route is (for the moment) out of the picture.
Nope.... If you're doing what I think you're doing, which would be having
the NAT box redirect port 80 to the inside web server, then you're done.
When traffic hits port 80 on the NAT box, it get's redirected to the inside
box. There is only one port 80, so when you tell it to redirect that port,
you can only tell it go to one place.
>Basically, I am trying to move one of our domains to it's own
>box. Email is easy enough to relay, and I have no problems assigning a
>special port for the few ssh clients we'll have... but http is still an
>issue.
There is one way around this, albeit not that helpful. Assign one of the
domains to an SSL server. Then, redirect port 80 to one system and port 443
to another.
Kenny
>**********************************************************
>To unsubscribe from this list, send mail to
>[EMAIL PROTECTED] with the following text in the
>*body* (*not* the subject line) of the letter:
>unsubscribe gnhlug
>**********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
