Re: Informix, NT4 and IIS

In <6ng132$2eb@ns.dvz-mv.de> "Bernd Heuer" <icafedt@mvnet.de> writes: >Hi there, >we have a similar problem: we try to use ASP pages with an IIS on a NT4.0-PC >and Intersolv-ODBC-Driver 3.10 to connect to an Informix-DB on a >UNIX-mashine. >But we can't manage to even establish the connection. It seems that it is >also >an authentication problem. >Any advice for me ?! >Thanks. >Wayne Chiasson wrote... >>Hi all, >>Has anyone been able to use ASP pages running IIS4 on an NT4 machine to >>query an informix database? We are able to connect when no security is >>being used but as soon as we try and force authentication, the site crashes >>after the second person logs on. The first person seems to be able to >>logon >>without problems. >>Forgot to mention that the database is on another server, and we are using >>Intersolv drivers 3.x to connect. Hello, I had quite a time getting IIS to work with Intersolv 3.x drivers for Informix on NT, but after some detective work I found that IIS doesn't authenticate via the domain unless it is a PDC or BDC. You need to do the following things: ** Beware! These involve using the registry editor program! ** These are from Microsoft's so-called knowledge base: Good Luck, Joe #include <MS_bs.h> =========================================================================== How to Authenticate a User Against All Trusted Domains Last reviewed: June 29, 1998 Article ID: Q168908 The information in this article applies to: * Microsoft Internet Information Server versions 2.0 and 3.0 { Note that in IIS4 you can just go to server properties -> Directory security -> Anonymous Access and Authentication Control -> EDIT - Be sure Basic Authentication is checked - Then Click on EDIT to enter the domain to be authenticated against. } SYMPTOMS By default, Microsoft Internet Information Server will validate an unqualified user logon ID against either the local computer's user database or the domain which the server is a member of. By changing an entry in the registry, you can force Microsoft Internet Information Server to validate the user against one domain of your choice. { This is misleading - on each of our installs, IIS tried to authenticate via the local server! JC } This information is contained in the online product documentation as follows: DefaultLogonDomain REG_SZ Range: string Default: domainname Specifies the default logon domain that validates a clear-text logon when no domain is specified in the user name field. The default value is the domain name for servers that are domain controllers or the name of the local computer (if stand-alone). WORKAROUND WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. To validate the unqualified user logon against all trusted domains and the local user accounts database do the following: 1. Run Registry Editor (Regedt32.exe). 2. Go to the following key in the registry: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\ <ServiceName>\\Parameters NOTE: where <ServiceName> is: MSFTPSVC FTP Service GOPHERSVC Gopher Service W3SVC WWW Service * On the Edit menu, click Add Value, and use the following entry: Value Name: DefaultLogonDomain Data Type: REG_SZ Value: \\\\Computername * Exit the Registry Editor and restart the computer for the change to take effect. STATUS Microsoft has confirmed this to be a problem in Microsoft Internet Information Server versions 2.0 and 3.0. - All praise the mighty Bill! --------------------------------------------------------------------- Additional query words: howto validate authenticate domain trust Keywords : prodiis3 prodiis2 Version : WINNT:2.0,3.0 Platform : WINDOWS Issue type : kbprb THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Last reviewed: June 29, 1998 (c) 1998 Microsoft Corporation. All rights reserved. Terms of Use. =========================================================================== HOWTO: Getting IIS to work with Informix ODBC Last reviewed: April 28, 1997 Article ID: Q166441 The information in this article applies to: * Microsoft Internet Information Server 3.0 { It also is needed for IIS4 - JC } SUMMARY This article describes some registry changes that need to be made to get Informix CLI 32 ODBC drivers to work with Windows NT 4.0 and Internet Information Server (IIS). MORE INFORMATION WARNING: Using the Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. The Informix drivers install only under the current user name of the person that is logged on to the system. In order to get general access to the drivers for all users, the registry entries that Informix installed under the logged on user's account must be copied to the generic users area. Here's how to do this: 1. Using Regedit, search the registry for the word "INFORMIXSERVER" (without the quotes). 1. This value and several others resides in a key called "ENVIRONMENT," which is a subkey of "INFORMIX." 1. Make a note of all of the values in the key and what they are equal to. 2. Go to HKEY_USERS\\DEFAULT\\Software and create a new k