Hi Jerry,
I'm still having problems allowing anyone from outside the local network access to my web site. I was not able to configure the linux box so it would use two NIC. When I put either card in and configured it, I was able to connect using https from outside the local network, if the NIC was connected directly to the cable modem. When both card were install at the same time, neither card would work. That is an idication of an IRQ conflict, but I was not able to trace it down, and I have the BIOS set for PNP. It seem like it should work, but it doesn't.
Also, I changed the forwarding on my Linksys router to point to my Windows NT Box. It is running Micorsofts IIS 4.0 web server. My Window NT computer is a 1.6 MZ with 512 meg of memory and two Western Digital 40 Gig hard drives with a pardise IDE/SCSI controller allowing UDMA 100/133. Guess what. I get the same message of "The connection was refused when trying to connect". This message is returned by Netscape 6.02. When I'm using IE I get the traditional IE message about contact the system administrator. I think I will take a look at the log files and see if they can provide additional clues.
I also downloaded apache 2.0.35-i686.RH7-2.tar.tar, or similar name, from the apache binary folder files. It comes with source code. My apache web server is a 586 and the apache2 is designed for a 686, so I had my doubt, but though I would give it a shot. The only parameter that it take is the fully qualified path of the root directory. If that is not supplied, it defaults to /usr/local/apache2 as the root. The modules are no longer compiled into the apache executable, but are supplied a seperate modules in the form of .so that live in a lib directory. The modules are loaded dynamically ar run time with statement like -IF OPENSLL-. If the functionality is present the httpd.conf will load the modules to work with it. The httpd.conf file is becoming more like a special program everyday. Anyway, I compiled Apache2 as follows:
# ./configur
# make test
# make
# install
It compiled without error, but when I attempted to start it, I received a page fault error, so I went back to the httpd/apache suppled with the RedHat 7.3 CDs.
Since the connection error occurs with both RedHat 7.3 and Windows 4.0 under both IIS and apache runing on two separate computers, the problem may be outside the boundaries of their control. It looking more and more like I may have to put everything back on Hostway. If I did this, I may no longer be able to use postgres as my web backend database. Hostway provides MySQL at an additional $5.00 per month, which I would probably need to use. I doubt I would be able to direct a Hostway web page request to my static IP here in Abilene so the Hostway web page could connected to my postgres here; and even if I could, the connection refused issue might through a monkey wrench into the plan.
To further complicate things Cox Communications is setting up DNS servers here in Abilene and Midland. Previously all DNS services were out of Oklahoma City and Dallas. When I was working with Cox Tech Support, they gave me the new IP address of the Abilene DNS, which I'm using. Also, I got a call from the tech support guy that installed my cable, and he gave me a new static IP address. It seem that some of Cox's IP address had been deleted during the transition to the new DNS. I made the necessary changes with my interNIC registrar through Hostway which charged me $9.95 to access my registrar and submit the change request. I still have my IP address with Hostway of 46.26.49.44 and it works fine, but it is not registered with the interNIC.
If you come across anything that might bear on my problem, let me know.
