user can't connect - driving me mad!
My background is very much in sql 2000 and am a bit raw with 2005.
I developed a database which is a backend for a local web app. All worked fine on the development server.
I have moved this over to a 2005 sql server in production and fired everything up. Out of approx 30 users tsted so far 2 of them cannot connect via the web app. They get login failed for nt authority/anonymous user
Anon access is not turned on in iis (Windows Auth is) None of these people that failed have permissions (windows/sql) above or below those that passed.
To get the db from 2000 to 2005 I created the new db in sql 2005 and then restored the backup from 2000.
To get the logins across I did a transfer logins task from 2005 to 2000
Both tasks went fine.
I have deleted 2 of the failed users, their logins/usernames/schemas and started them from scratch. Still no good.
What's happening with these few people?
I developed a database which is a backend for a local web app. All worked fine on the development server.
I have moved this over to a 2005 sql server in production and fired everything up. Out of approx 30 users tsted so far 2 of them cannot connect via the web app. They get login failed for nt authority/anonymous user
Anon access is not turned on in iis (Windows Auth is) None of these people that failed have permissions (windows/sql) above or below those that passed.
To get the db from 2000 to 2005 I created the new db in sql 2005 and then restored the backup from 2000.
To get the logins across I did a transfer logins task from 2005 to 2000
Both tasks went fine.
I have deleted 2 of the failed users, their logins/usernames/schemas and started them from scratch. Still no good.
What's happening with these few people?
ASKER
all different users all on the same domain - mixed results pass/fail
all users are "public"
all have logins created in 2005, usernames made in the appropriate DB. Schemas (which is an alien concept to me in SQL) created
login name = domain/username
mapped to username domain/username with a default schema named domain/username
This is the pattern for all users, ones who can connect and those who can't
My web.config has windows authentication and impersonation.
IIS has anon turned off so it must be the user connecting to the DB (via IIS)
all users are "public"
all have logins created in 2005, usernames made in the appropriate DB. Schemas (which is an alien concept to me in SQL) created
login name = domain/username
mapped to username domain/username with a default schema named domain/username
This is the pattern for all users, ones who can connect and those who can't
My web.config has windows authentication and impersonation.
IIS has anon turned off so it must be the user connecting to the DB (via IIS)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
great going !!!!
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
Vee_Mod
Community Support Moderator
are you trying thru something else ?