John A. Sullivan III wrote: > Ah, OK - between this reply and your replay to Aleksander, it's starting > to become a bit more clear. The router is a corporate router to the > outside world over which you have no control. This internal 10 network > where the Linux box and 2nd Webserver sit IS the entire internal network > with a 22 bit mask and housing all users who directly access the 2nd > WebServer on the LAN. You want the WebServer accessible to the world > but, because of politics, bureaucracy, etc., you only have control over > the Linux box. Do I understand it thus far? Exactly :) > > Do you have the freedom to insert a second NIC into the 2nd WebServer? > If so, you can insert a second NIC into both devices, set the default > gateway for the 2nd WebServer to the Linux Box and allow world access > through this second network. No, I don't but, I'm just going to have to go through all the steps in this company to get it in order to do what they require. > One way or another, you are going to have to touch the 2nd WebServer > even if just to change its default gateway to the LinuxBox so that its > reply packets to the world pass through the Linux Box. If you cannot > get it on a separate network by hook or by crook, you'll have to > investigate bridging. I think there is something at > http://ebtables.sourceforge.net/ but I have never played with it. Good > luck - John To make matters worse, the second webserver is IIS and I have no idea how to use IP Multiplexing on Win2k, I could do it in linux but Windows systems are not my expertise. What I'm going to do -if I get the permission- is this: Install a 2nd nic on the 2nd webserver so the IP address that is being used doesn't get affected and I will configure it's router to the linux box so it can redirect packets where they should go... Thanx a lot for this great help, I really mean it... this mailing list is simply great Juan
