March 28, 2008 at 4:42 am
I have the following environment setup:
Server A:
Win2K, SQL Server 2K SP3, Security Authontication Windows Only
Server B:
Win2003, SQL Server 2K SP3, Security Authontication Windows Only, Security Options tab in components services is set properly
Domain:
Windows 2K
I have used sp_addlinkedserver command on both servers
They see each other and can select from each other as well.
The problem I have is that when I try to open a query analyzer session on server B while I am physically on server A and try to access server A I get error "Login failed for user (null)"
Any idea why? Specially that this sometimes works and sometimes it simply doesn't for no known reason!!
March 28, 2008 at 5:06 am
Hi,
Please check for the @@servername for the server u are going to connect. Many times it is happeneing that the servername is null in the system but you anc login to that...
I hopt this would help..
March 28, 2008 at 8:43 am
Read my prior post: http://www.sqlservercentral.com/Forums/FindPost473248.aspx
In fact, I would recommend reading the whole thread as it has lots of good stuff from other posters.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
April 13, 2008 at 2:35 am
I'd like to thank everyone who tried to help but I fiannly solved the problem by upgrading the domain from Win2K to Win2003. I discovered that a lot of security and authentication issues are solved by using kerbos protocol and this protocol is embeded in Win2003.
April 13, 2008 at 1:08 pm
And does it work now?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
April 16, 2008 at 11:52 pm
Hi,
Can u tell us what security options you discovered after upgrading from 2k to 2003. Coz when u will be having a distributed transactions having sql2005 in the os. it will give an error 7391. For this issue we had face lot of problem with windows2003 and sql 2005.:)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply