September 28, 2005 at 5:03 pm
Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on my laptop I opened up frontpage to create a page to view the db results. But, I get the this error when I select the "System Data Source on Web Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
I have been browsing through the web for some time now and can not seem to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows Authentication", I have added the IIS_WPG, created a new account named SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view data entered into a SQL db.
Any help will be very much appriciated
September 29, 2005 at 1:04 am
In order to use windows authentication, you need to put the servers in a domain.
If they can't be in one, you have to use sql-authentication.
September 29, 2005 at 11:51 am
I beleive that in older versions of Windows server systems, you could authenticate using the same-name user on two different servers as local users. (Definitely in NT4 and Windows 2000) Technically, they are two different user accounts (server1\name1 and server2\name1), but Windows Authentication worked and recognized name1 as the same on both servers.
But I do not think that works anymore on Windows 2003. That would be part of the security lockdown MS implemented on that version. I have not tried or tested it to be absolutely sure, but I would bet that it does not work anymore.
You will likely have to use SQL authentication, or add a domain controller.
Mark
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply