Fagyal, Csongor ([EMAIL PROTECTED]) wrote:
[snip]
> >PING rr-n1-tor.opensrs.net (216.40.33.39): 56 data bytes
> >64 bytes from 216.40.33.39: icmp_seq=0 ttl=236 time=287.759 ms
> >
> >Never knew it was that far away though ;-(
> >
> >
> Hmmm.... thank you for your reply, Andy.
>
> However, I don't know what the problem is, then. Now I can traceroute up to
>
> 129.33.183.72
>
> but still I'm getting "Unable to establish socket" messages. Verify simply
> says (after some waiting):
>
> _________OpenSRS Client Debugger__________
>
> Operating System : Linux xxxxxxx 2.4.18-14 #1 Wed Sep 4
> 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux
> Perl compiled for : linux (i386-linux-thread-multi)
> Client Version : XML:2.2.3b
> Server Hostname : rr-n1-tor.opensrs.net
> Server Port : 55000
> Reseller Username : xxxxxxx
> Private Key Length : 111
> Encryption method : Blowfish
> Checking for Digest::MD5 : OK (version 2.20)
> Checking for Crypt::DES : OK
> Checking for Crypt::Blowfish : OK (version 2.09)
> Prototype mismatch: sub Crypt::CBC::new vs ($$;$) at CBC.pm line 44, <DATA>
> line 241.
> Checking for Crypt::CBC : OK (version 1.25)
> Checking for XML::Parser : OK (version 2.31)
> Checking for Unicode::String : OK (version 2.06)
> Checking for Storable : OK (version 2.04)
> Logging in to OpenSRS server : ERROR: Unable to establish socket!
I don't have the client debugger handy, but I can definitely establish
a socket:
> telnet rr-n1-tor.opensrs.net 55000
Trying 216.40.33.39...
Connected to rr-n1-tor.opensrs.net.
Escape character is '^]'.
Content-Length: 559
<?xml version='1.0' encoding="UTF-8" standalone="no" ?>
<!DOCTYPE OPS_envelope SYSTEM "ops.dtd">
<OPS_envelope>
<header>
<version>0.9</version>
</header>
<body>
<data_block>
<dt_assoc>
<item key="object">VERSION</item>
<item key="attributes">
<dt_assoc>
<item key="state">ready</item>
<item key="version">XML:0.1</item>
<item key="sender">OpenSRS SERVER</item>
</dt_assoc>
</item>
<item key="protocol">XCP</item>
<item key="action">CHECK</item>
</dt_assoc>
</data_block>
</body>
</OPS_envelope>
Can't think what the error could be - if it was an invalid IP the XML
would actually tell you.
If its timing out, maybe there is a routing problem (which is why it
can't establish a connection). Can you ping the server?
Andy.
