#21653 [Com]: Warning: fsockopen() [function.fsockopen]: php_hostconnect: connect failed

From: Date: Thu, 10 Jul 2003 19:53:50 +0000
Subject: #21653 [Com]: Warning: fsockopen() [function.fsockopen]: php_hostconnect: connect failed
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-43686@lists.php.net to get a copy of this message 
 ID:               21653
 Comment by:       laudanp at yahoo dot com
 Reported By:      support at hostcolor dot com
 Status:           Feedback
 Bug Type:         Sockets related
 Operating System: RedHat 7.2
 PHP Version:      4.3.3RC2-dev
 New Comment:

In addition, I'm not sure why the error would continue even after
wez...

"[22 Jun 5:11am CDT] wez@php.net 
When I visited your test page, it seemed to be working; the port-scans
triggered my port-sentry and that dropped the route to your machine.
So the only "problem" is that you see two separate error messages?
I've removed a redundant message from the stable branch.

"


Previous Comments:
------------------------------------------------------------------------

[2003-07-10 14:53:00] laudanp at yahoo dot com

In addition, the http://64.246.34.44/ address I listed just above
is no
longer in use.  You can refer back to the original
http://computercops.biz links way above.

Thanks

------------------------------------------------------------------------

[2003-07-10 14:51:31] laudanp at yahoo dot com

Each "ports are filtered or open" line is with respect to the client PC
(target PC), and not the server that PHP is installed.

Scenario A: 

- ports are filtered (closed or stealth)
- PHP 4.2.3 is installed

Scenario B:

- ports are open
- PHP 4.2.3 is installed

Scenario C:

- ports are filtered (closed or stealth)
- PHP 4.3.x is installed

Scenario D:

- ports are open
- PHP 4.3.x is installed

Ok, under both Scenario A and B, no "fsockopen()..." error is
generated.

Under both Scenario C and D, the "fsockopen()..." error is displayed.

Clearly what worked 100% of the time in 4.2.3, no longer functions in
4.3.x.  This has been an ongoing issue for several months now.

------------------------------------------------------------------------

[2003-07-10 11:41:03] sniper@php.net

This is propably stupid question..but why shouldn't fsockopen() give an
error when it fails to connect???
Obviously that's what is happening here? :)


------------------------------------------------------------------------

[2003-07-10 02:51:25] support at hostcolor dot com

I am not the original submitter of the bug but I was contacted by mr.
Paul Laudanski and also by seeing the number of comments it seems that
the problem is still there. We certainly found no solution as nothing
else but reverting to 4.2.3 helped.
best regards and good luck

------------------------------------------------------------------------

[2003-07-09 09:21:01] laudanp at yahoo dot com

HI folks, welcome back.  So, what is the status?  Those errors are
still there.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/21653

-- 
Edit this bug report at http://bugs.php.net/?id=21653&edit=1

Thread (57 messages)

« previous php.bugs (#43686) next »