There are a few possibilities:
1) Are you connecting to rr-n1-tor.opensrs.net while you're still in
testing? If you haven't passed the RITE test yet, then you won't be able to
connect to the production server, and you may get this error.
2) Are you connecting to the production server from an IP address other than
the one you gave to OpenSRS when you went live?
3) Check your OpenSRS.conf to make sure you've specified either
rr-n1-tor.opensrs.net or horizon.opensrs.net as the server name.
4) Finally, this can happen if the permissions to /etc/protocol do not allow
the anonymous user to read the file (I'm going from memory here on the exact
filename, so forgive me if it's wrong). On WINNT, the file in question is
something like c:\winnt\system32\drivers\etc\protocol.
Regards,
Eric Longman
Atl-Connect Internet Services
+-------------------------------------------------------+
| Atl-Connect Internet Services http://www.atlcon.net |
| 3600 Dallas Hwy Ste 230-288 770 590-0888 |
| Marietta, GA 30064-1685 [EMAIL PROTECTED] |
+-------------------------------------------------------+
----- Original Message -----
From: "Sandro Bradi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 11, 2000 9:23 AM
Subject: socket problems
When trying to use the OpenSRS script (reg_system or verify_install), it
tells us:
Logging in to OpenSRS server... ERROR: Unable to establish socket!
what's the reason? any idea?
thanks
marc
