Thanks very much will this be a solution for the exchange and iis?
Yes i am a newbie and i appreciate simplicity, learning the linux os is a
task in itself with out have the battle of disecting HOW-TOs
>
>Simply because sendmail and apache are already pre-configured. ipchains is
>pretty hard to setup for a beginner, and Linuxconf has the bad habit of
>resetting firewall/routing settings.
>
>ipfwadm/ipchains/whatnext change with kernel versions. It's really hard to
>keep up. Apache and Sendmail are more likely to be backward-compatible
>with most releases/distributions.
>
>But I agree that LRP rocks =) Send a floppy to your customer and you're
>set, on a 386sx/16, 1.44 and 8 megs ram!
>
>Jean-Michel Dault
>[EMAIL PROTECTED]
>
>On Thu, 30 Dec 1999, Jack Coates wrote:
>
>> Date: Thu, 30 Dec 1999 22:15:34 -0800
>> From: Jack Coates <[EMAIL PROTECTED]>
>> Reply-To: [EMAIL PROTECTED]
>> To: [EMAIL PROTECTED]
>> Subject: Re: [expert] Port Forwarding I guess
>>
>> Jean-Michel Dault wrote:
>> >
>> > If you want to enable IIS behind Linux, add this in
/etc/conf/httpd.conf,
>> > assuming your NT is 192.168.0.1. Don't forget the trailer slash,
otherwise
>> > it won't work.
>> >
>> > ProxyRequests On
>> > ProxyPass / http://192.168.0.1/
>> >
>> > Jean-Michel Dault
>> > [EMAIL PROTECTED]
>> >
>>
>> This assumes you've installed Apache on the Linux box, and the answer
>> for his Exchange assumes that Sendmail is running on the Linux box. If
>> he has IIS and Exchange behind the box, why go to the trouble of setting
>> up Apache and Sendmail to act purely as relays up in user space? Use
>> ipfwadm or ipchains to forward port 25 to the Exchange box and port 80
>> to the IIS box, then all the work is done in the kernel. This is a job
>> for lrp.c0wz.com!
>> Jack
>> --
>> Linux: because you can't do a sig like this in Windows.
>> 10:12pm up 13:18, 2 users, load average: 0.49, 0.82, 0.86
>>
>
