Hi All,
This message is more to get a solution into the mail list archives than
anything else, but if you happen to be plagued by this problem maybe this'll
help...(comments or corrections -- especially for the *nix parts -- are
welcomed and appreciated).
PROBLEM DESCRIPTION
===================
When you run verify_install.cgi everything looks fine but the "Logging in to
server" step reports "ERROR: Unable to establish socket".
SYSTEMS AFFECTED
================
Windows NT,
Windows 2000,
possibly *nix variants (this is possible but unlikely)
SOLUTION
========
On Win32 platforms, this happens when the permissions on
C:\WINNT\System32\drivers\etc are set too tightly. In order to establish
the socket, the program must be able to read the PROTOCOL file in this
directory. The following command issued from a command prompt will grant
READ privilege to EVERYBODY on this directory:
C:\>cacls c:\winnt\system32\drivers\etc /t /e /g Everyone:r
*NOTE: You may need to adjust the path if you've installed Windows NT to a
path other than the default.
ADDITIONAL STEPS TO DETECT THIS CONDITION
=========================================
You can confirm that this is the problem like this:
1) Log in to the server interactively with an
account that has elevated permissions (like
the Administrator account)
2) Open a command window and change to the cgi
directory where verify_install.cgi is installed.
3) Run verify_install.cgi from the command prompt,
like this:
c:\>perl verify_install.cgi
4) If the script is able to successfully log into
the server from the command line, but *NOT* from
a browser session, then this indicates that the
c:\winnt\system32\drivers\etc directory is
inaccessible to the IUSR_machinename user that
the web server runs under.
NOTES FOR *NIX
==============
On *nix platforms, if the permissions on /etc/PROTOCOL are set such that the
anonymous user can't read it, then you will get this error. This would be
very unusual on a *nix system though, because they tend to be configured for
network connections by default.
If you encounter this on *nix, I believe the proper command would be
$chmod 744 PROTOCOL
to grant read privilege to the PROTOCOL file for world.
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] |
+-------------------------------------------------------+
