[ale] apache wierdness

[James P. Kinney III]

Scenario:

apache server behind nat firewall.
Network changes just occurred.
Nat reconfigured to accept new external IP and redirect to DMZ apache
server.

Situation:

_partial_ connections. If login to web script with bad user name or
password, system returns the correct "bad username or password. Login
failed" error message from the login script.

Using a good combination, I get no response. It looks like a server hung
on connect. wget eventually times out. BUT! The person who wrote the app
on the server connects just fine with the SAME LOGIN THAT FAILS WITH
ME?!?!?!

Both of us see the same IP address. No errors in the log files.

If I try and access a perl script in cgi-bin called printenv with the
perms set to no execute, I get an apache arror message telling me it
can't be execute. If the perms are fixed, the server just sits and does
NOTHING.

I have never seen something like this before and am comletely perplexed.

The firewall now has old and new connections on it (i.e. old IP and new
IP) We are in the process of migrating to a new ISP/data line provider. 

If everything failed to go through, I could understand it being the
network change. But some stuff comes through. Static pages don't happen.
Error messages happen.


-- 
James P. Kinney III          \Changing the mobile computing world/
CEO & Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part