Hi NGs,
I've a very strange behavior of an IIS.
Situation:
We have a Windows 2000 Server with IIS5 and SQL 2000 SP3 installed
(call it oldserver). it's located in the domain [oldRD]
next we have a Windows 2003 server running IIS6 and SQL2000 SP3
[newserver]. this one is located in domain [newRD]
[oldrd] and [newrd] have a oneway trust: [oldrd] trusts [newrd].
now we have a Domain User located in [newRD] let's call him [myuser].
[myuser] is logged on to a workstation located in [newrd] -Windows XP
Sp1.
he is member of local administrators on all relevant machines.
There are two databases, one located on [newserver] the other on
[oldserver] -lets name them [oldDB] and [newDB] ;-)
On both server is the same website installed. The site contains
ASP-scripts.
On [oldserver] there is a SystemDSN pointing to [oldDB].
On [newserver] there are two SystemDSNs one pointing to [oldDB] on
[oldserver] and the other pointing to [newdb] on [newserver].
All DSNs are tested successfully on the server using WinAuth.
Now if [myuser] opens the web on [oldserver] accessing [olddb]
everything works.
If [myuser] opens the web on [newserver] accessing [newdb] everything
works fine.
But if [myuser] opens the web on [newserver] accessing [olddb] the
odbc sends back an error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Error authenticating
user 'NT AUTHORITY\ANONYMOUS LOGON'
/serverdata/sharedfiles/dbconnect.asp, line 3.
DBCONNECT.ASP looks like this:
<%
Set conn = Server.CreateObject("ADODB.Connection")
conn.Open "DSN=serverdata;USR=_runtimeusername;PWD=_runtimepassword"
%>
The IIS-logs on [newserver] show the [newrd]\[myuser] loading the web.
If the user connects to the [newserver] using RDP and loads the web
localy, it works.
What is it, that IIS6 prevents sending the runtimeuser to DSN if this
web is loaded remotly?
thanks ind advance
Carsten Lahme