Hi Jerry,

Even though I did a custom install with the specific intent of excluding OpenSSL, it none the less was included. I decided to try again an see if I could run my web site under windows NT 4.0, so I started the apache2 services on my Windows NT Server, pointed my router to forward everything over port 80 to the window NT apache2 server. I turned my linux box off to take it out of the equation. I was able to bring the web page up locally by entering either the local IP address or the NetBIOS name. Then I connected to netzero and tried to access the site remotely with the registerred ULR and it didn't work. Next I stop the NT apache2 services and started Microsoft's IIS 4.0 services. I performed the same test with identical results. Everything is fine locally, but nothing doing form outside the local network. I'm beginning to think that anything coming into the local network over the WAN static IP is encrypted with SSL. Unless I have SSL installed, no connection can be made, because of the language barrier. I know some of the more expensive network cards have encrption built right into a chip on the NIC. I called Cox Tech Support and they do not use encryption in any of thier hardware or software. Well I'm back to square one. What are my options:

1. Set up my linux server with SSL and have everyone access it using https. I have not been able yet to determine if this problem exist over other ports like 5432 which postgres uses or port 1033, I think, which MySQL uses. If this is the case then setting up my web site as a secure SSL would only be a partial fix. Also, this requires a special network configuration, and my require the purchase of another router.

2. Move everything back to Hostway in Chicago, ILL and let them worry about connection problems. Also, I would have to move all my web postgres tables to a dedicated MySQL server hosted by hostway.com.

3. Search for a new site that support postgres, cancel my Hostway account, and then transfer my domain registration. Hostway will not act as a registrar unless you maintain an account with them.

4. Find some other way to distribute my FoxPro App that doesn't require a web site. I really don't like this idea.

There doesn't seem to be an easy and satisfactory solution. Very aggravating. I believe this one has me beat.

Any ideas on how to proceed from here?