ID: 21653 Updated by: [EMAIL PROTECTED] Reported By: support at hostcolor dot com -Status: Open +Status: Feedback Bug Type: Sockets related Operating System: RedHat 7.2 PHP Version: 4.3.3RC2-dev New Comment:
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? :) Previous Comments: ------------------------------------------------------------------------ [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. ------------------------------------------------------------------------ [2003-07-01 06:38:08] laudanp at yahoo dot com Ok, I disabled any port blocking on my end this morning, and as it turns out I get the same messages as when port blocking was on: Warning: fsockopen(): unable to connect to xxx.xxx.xxx.xxx:21 in /var/www/html/testpaul.php on line 134 Connection Refused: Port 21 used by Nerte 7.8.1. This is odd indeed. ------------------------------------------------------------------------ [2003-06-30 08:27:35] laudanp at yahoo dot com CORRECTION TO THIS: So something is different between the TCP and UDP connections. Now, I'm running these scans from a box that is dropping the probes. Hence, since UDP is connectionless and TCP is connection oriented, the bug may have something to do with this? I haven't tested it on a system that is not running a firewall recently. What do your tests show now with the current snapshot? ------------ CORRECTED VERSION: *... Now, I'm running these scans from the server against a system that is dropping the probes via a firewall. ... I haven't tested it on a system that is not protected by a firewall (or disabled it). What do your tests show now with the current snapshot? ...* ----- Thanks ------------------------------------------------------------------------ [2003-06-30 08:24:33] laudanp at yahoo dot com Download: .bz2 (3.5M) .gz (4.3M) Built On: Jun 30, 2003 11:30 GMT php4-STABLE-200306301130 http://64.246.34.44/phpinfo.php http://64.246.34.44/testpaul.php Hi, I grabbed the latest stable cvs snapshot and it appears the problem persists. Its the same code, no change, since I started using it prior to PHP 4.2.3. For some reason, it doesn't work with 4.3.x. Now, for my UDP scanner (http://www.computercops.biz/modules.php?name=UDP_Scanner) on PHP 4.3.x I use the following code which works well with either 4.2.3 or 4.3.x: $handle = fsockopen($this-> targetIP, $portNumber, &$errno, &$errstr, 2); For the TCP Scanner (http://www.computercops.biz/modules.php?name=TCP_Scanner), I have this line: $handle = fsockopen($this-> targetIP, $index, $errno, $errstr, $this-> timeout); So something is different between the TCP and UDP connections. Now, I'm running these scans from a box that is dropping the probes. Hence, since UDP is connectionless and TCP is connection oriented, the bug may have something to do with this? I haven't tested it on a system that is not running a firewall recently. What do your tests show now with the current snapshot? Thanks (Phew, this is one elusive bug). P.S. Here is my configure statement: ./configure --with-mysql --with-apxs --with-gd --with-jpeg-dir=../jpeg-6b/ --with-zlib ------------------------------------------------------------------------ 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
