By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,632 Members | 1,906 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,632 IT Pros & Developers. It's quick & easy.

Problems with Windows Authentication

P: n/a
Hi,
We're currently planning to migrate from SQL Auth to Windows Auth.
Personally, I do not have too much experience with Windows
authentication but have heard that there are some problems when working
with it.
The problems I've already ran into were:
"Cannot Generate SSPI Context" (which I've already resolved), and a
more serious problem which prevents me from connecting to a linked
server. (double hop, see http://support.microsoft.com/?id=238477)

Anything else I should expect?

Thanks!

Jul 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"Adi Sapir" <ad******@gmail.com> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...
Hi,
We're currently planning to migrate from SQL Auth to Windows Auth.
Personally, I do not have too much experience with Windows
authentication but have heard that there are some problems when working
with it.
The problems I've already ran into were:
"Cannot Generate SSPI Context" (which I've already resolved), and a
more serious problem which prevents me from connecting to a linked
server. (double hop, see http://support.microsoft.com/?id=238477)

Anything else I should expect?

Thanks!


In general, MS recommends Windows authentication over SQL authentication -
if you have Windows client connecting directly to the server then things
should be quite straightfoward. If not (for example, if you're using JDBC),
then you might have some issues, but as with any major change, you should
try it out first in a test environment - if you do have any problems, then
you can post more details here or in microsoft.public.sqlserver.security.

Simon
Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.