October 20, 2006 at 11:16 am
Hi,
I have a Server 1 locally and Server2 and Server3 at another location. Server2 registers in Enterprise Manager on Server1, but when I try to add Server2 as a linked server using the same credentials it tells me "SQL Server does not exist, or access denied". Server 3 registers fine and was added as a linked server with no problems.
Server2 and Server3 are at different locations. All Sql Servers are SQL2000
What could be the deal? When adding as linked server, does it use a different port than 1433 (maybe they need to open that port if it's different?) I can't think of what the deal is.
Local Server -->Registers Server2 OK
Local Server -->Server2 as linked server connection prob.
Local Server -->Registers Server3 OK
Local Server -->Server3 as linked server OK
October 20, 2006 at 1:55 pm
Run a Profiler trace on the server being linked to. Make sure you add in Audit Login Failure as an event. Try to use the linked server connection. If you don't see the audit failure, there's a communications issue. If you do, perhaps the account you are using doesn't have the appropriate rights to login (whether you've mapped it or told it to use existing credentials).
K. Brian Kelley
@kbriankelley
October 20, 2006 at 2:06 pm
Well, I can register it, use query analyzer, and even connect via ODBC, but it won't add as a linked server, so it's not a connection issue (unless the port for linked servers is different than 1433 in which case I'll have to open it in the firewall). I even tried to connect linked server using several credentials including the sa account and it still doesn't work. If I can view the objects in EM, use Query Analyzer, and connect via ODBC, linked servers shouldn't be a problem, unless there's a different connection property that i'm not aware of. BTW, I have other servers registered as linked with no problem, so the issue appears to be with the remote server...?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply