Tech Support > Computers & Technology > testing for fsockopen
testing for fsockopen
Posted by Lincoln Geo on November 18th, 2006


Hello. Before going to our host administrators I'm trying to do a little
research. When I attempt to run a PHP server-side RSS aggegator program (to
bring in some feeds headlines to a web page) I receive this error, for
example, in its error log:

fsockopen(): unable to connect to www.nytimes.com:80

I am told that fsockopen is typically enabled by default but I don't know if
such is the case on this server, or, if perchance there is something else
preventing the outside connections.

My question is, is there a way for me to do a test that will tell me that
fsockopen is disabled? And if it is disabled, what does it entail to enable
it?

Thanks.


Posted by why? on November 18th, 2006



On Fri, 17 Nov 2006 18:42:48 -0800, Lincoln Geo wrote:

x-post snipped to 24hshd from
alt.www.webmaster,24hoursupport.helpdesk
oddly enough there was no need to snip any php newsgroup, the OP missed
them.

What little research you did do, resulted in this answer -

Contact the "host administrators"

So you think that 1 persons default open is not another default closed?

Like a firewall, you mean?

Well 1 test would be trying to create a connection using fsockopen() and
trying to connect to a site, for example www.nytimes.com:80 and see what
happens.

Use a different method to connect to the site.

Contact the "host administrators"


Posted by Lincoln Geo on November 19th, 2006


Your comments are about as helpful as a candle in a forest fire.
Nevertheless thank you for taking the time to not reply to my question.


"why?" <fgrirp*sgc@VAINY!Qznq.fpvragvfg.pbz> wrote in message
news:7cjul2lc3o4dbrriibe4il5pt8k65urh3d@4ax.com...


Posted by why? on November 19th, 2006



On Sun, 19 Nov 2006 01:30:53 -0800, Lincoln Geo wrote:

Well it's you that said you can't be bothered to ask the system admin
first. That is only your fault, no one else can get that wrong for you.

I doubt there is an admin for you system (which you didn't specify who /
what / where anyway) in the 24hshd ng. Thus it is impossible to answer
any query about what is /isn't enabled or blocked by a FW.

Sadly you didn't even say if you tested the supplied URL on a browser
from that system to see if the target itsef is reachable. Nor did you
say if a proxy is involved. You didn't say if it's simply a failed DNS
lookup.


Me

Posted by Charles Sweeney on November 20th, 2006


Lincoln Geo wrote

I would just ask the host.

--
Charles Sweeney
http://CharlesSweeney.com


Similar Posts