This is new information (not in original post) - Are you saying that after a reboot, you get a single response with the first hit but after that a timeout?
Precisely. I'm experiencing this behaviour not only with Apache. It seems that if I run a generic sever program listening for incoming connections I'm able to connect to it only at the first hit.
Other things to check out: - try using IP address in browser to eliminate DNS issues
Already done. No result.
- what is on the homepage? I hope it's a plain HTML page... If it's some clever dynamic content, are you sure it works with an external request? (eg, if it does something clever with the client-IP, like a reverse DNS lookup... you might have problems).
The page is the default plain HTML apache homepage.
what browser are you using? Get Firefox with the LiveHTTPheaders extension and look at the request-response headers for more clues.
I tried Firefox 2, Internet Explorer 7, Opera 9 and Konqueror. I always get the same behaviour. I'm going to get LiveHTTPheaders and let you know if I made some progress. Are you interested in a packet sniffing capture too?
The point about quadruple-checking the FW is that, for security reasons, a FW usually *drops* disallowed packets (as opposed to refusing the connection). So timeout problems are often due to FWs (if you hear hoof-beats, think horses, not zebras). Are you sure you only have one FW? Check the process table...
Completely sure. Maybe this problem is related to Windows Xp inbound connection limit? See http://support.microsoft.com/?scid=kb%3Ben-us%3B314882&x=10&y=11 for details.
I really appreciate your help. Thank you.
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|