Re: Bind failure

[Graham B. <gb...@po...>]

On Tue, Jun 27, 2000 at 11:45:02AM +0200, Klunder, JAA (Hans) wrote:
> I tried 2 things:
> 
> I tried perl 5.005_03 (activestate 522) with a small test script, the script
> runs fine from a dos box, the entries are found and dumped there (so the kit
> is correct), but when I run it from IIS (either as CGI or as ISAPI) it
> returns:
> 
> -----
> Content-type: text/html 
> Software error:
> create failed: IO::Socket::INET: Cannot determine protocol at
> C:\Inetpub\wwwroot\ldaptest.pl line 9. 

This is running perl5.6.0 as this is a known bug. Your system does not know
how to map the protocol name "ldap" to port 389.

This should be fixed in 5.6.1, but until then you just have to tell your system
about the ldap protocol. As I am not a windows user I cannot help with how to do
that.

> -----
> 
> I also tried perl 5.004_2. However I can't get either the ASN1 module or the
> perl-ldap module to install on that system:
> 
> ---------
> C:\temp\Convert-ASN1-0.07>perl makefile.pl
> Writing Makefile for Convert::ASN1
> 
> C:\temp\Convert-ASN1-0.07>d:\temp\nmake
> 
> Microsoft (R) Program Maintenance Utility   Version 1.50
> Copyright (c) Microsoft Corp 1988-94. All rights reserved.
> 
> makefile(641) : fatal error U1001: syntax error : illegal character ',' in
> macro

This is another common Win32 problem. Due to the many flavors of make on such
systems, MakeMAker will write the makefile in the format for the make app
that was used to compile perl itself. Unless you are using the same app
you will see these errors.

You need to either

1) Install manually

2) Get a copy of the same make app that was used to compile perl

3) modify the Config.pm in your perl installation so makemaker will
   write the makefile in the correct format

perl -V:make

will tell you what your config currently says.

Graham.