Linked server - from 2008 to a 2005 box.
in [Server Configuration]
|
From: Fsb on 20 Jan 2010 14:23 OK after much testing it looks like we fixed it? I created a TCP/IP Alias to the destination server with the non default port of 30001. BUT what I do not understand is that I can connect to the destination server from other servers without having to create an Alias. Is this something new in SQL 2008? "Fsb" <Fountainhead7(a)hotmail.com> wrote in message news:ezHdrVemKHA.2164(a)TK2MSFTNGP02.phx.gbl... > Just to clarify is it still possible that it could be a double hop issue > if I am using the destinations SA account when creating the linked server. > I'm not using impersonate. > > Also, difference between this SQL box from all others boxes that I don't > have an issue connecting to are; > > 1. It's a virtual machine on a dedicated blade. > > 2. Windows 2008 server. > > 3. SQL 2008 Server. > > 4. The destination server is not using the default port. > > Should these be areas that could cause an issue? If, so how do you suggest > going about excluding each as the cause? > > Do any of the points I mentioned in previous post already exclude one of > the points listed above as not being the issue? > > Do recap the facts: > > 1. When I login into the source SQL server box with my own login in, > start SSMS using my own login and connecting to the destination using the > SA account or (any SQL server account) for the destination it works. These > same steps do not work on my local machine. > > 2. I can connect to the destination server as described above from > any other server on my network from my computer. > > 3. I can connect to the source from the destination as described in > step 1 with no issues. > > "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message > news:Xns9D00EF2AC52A0Yazorman(a)127.0.0.1... >> Fsb (Fountainhead7(a)hotmail.com) writes: >>> Named Pipes Provider: Could not open a connection to SQL Server [5]. >>> OLE DB provider "SQLNCLI10" for linked server "SERVER NAME" returned >>> message "Login timeout expired". >>> OLE DB provider "SQLNCLI10" for linked server "SERVER NAME" returned >>> message "A network-related or instance-specific error has occurred while >>> establishing a connection to SQL Server. Server is not found or not >>> accessible. Check if instance name is correct and if SQL Server is >>> configured to allow remote connections. For more information see SQL >>> Server Books Online.". (Microsoft SQL Server, Error: 5) >> >> Error 5 is "Access is denied". >> >> It seems that your Windows user is not permitted to access that part of >> the network, so it does not make contact with the remote server at all. >> Really what this may be due to, I don't know, but so much is clear that >> this is a question about configuration of Windows networking and not >> primarily an SQL Server problem. It probably has something to do with >> double hops. >> >> -- >> Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se >> >> Links for SQL Server Books Online: >> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx >> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx >> SQL 2000: >> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx >> > >
From: Erland Sommarskog on 21 Jan 2010 18:03 Fsb (Fountainhead7(a)hotmail.com) writes: > OK after much testing it looks like we fixed it? > > I created a TCP/IP Alias to the destination server with the non default > port of 30001. > > BUT what I do not understand is that I can connect to the destination > server from other servers without having to create an Alias. Is this > something new in SQL 2008? There are still a number of things I don't know, but since you got an Access is Denied error, the problem may be with the SQL Browser Service. Which you circumvent by specifying the port number. -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
From: Fsb on 22 Jan 2010 08:29 so the fact that the server i'm trying to connect to is not using the default port and is using 30001 does not result in having to change anything in the source server to connect? "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message news:Xns9D0898BC80FYazorman(a)127.0.0.1... > Fsb (Fountainhead7(a)hotmail.com) writes: >> OK after much testing it looks like we fixed it? >> >> I created a TCP/IP Alias to the destination server with the non default >> port of 30001. >> >> BUT what I do not understand is that I can connect to the destination >> server from other servers without having to create an Alias. Is this >> something new in SQL 2008? > > There are still a number of things I don't know, but since you got an > Access is Denied error, the problem may be with the SQL Browser Service. > Which you circumvent by specifying the port number. > > -- > Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se > > Links for SQL Server Books Online: > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx > SQL 2000: > http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx >
From: Erland Sommarskog on 22 Jan 2010 17:46 Fsb (Fountainhead7(a)hotmail.com) writes: > so the fact that the server i'm trying to connect to is not using the > default port and is using 30001 does not result in having to change > anything in the source server to connect? Well, somehow you must of course specify it. Either by instance name (assuming it's a named instance), or by port number. The Browser service is supposed to resolve the instance name to a port number, but there are several instance I access by port number, for one reason or another. -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
From: Fsb on 22 Jan 2010 17:52
no instance on the server. "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message news:Xns9D08F1C958DE1Yazorman(a)127.0.0.1... > Fsb (Fountainhead7(a)hotmail.com) writes: >> so the fact that the server i'm trying to connect to is not using the >> default port and is using 30001 does not result in having to change >> anything in the source server to connect? > > Well, somehow you must of course specify it. Either by instance > name (assuming it's a named instance), or by port number. The Browser > service is supposed to resolve the instance name to a port number, > but there are several instance I access by port number, for one reason > or another. > > > -- > Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se > > Links for SQL Server Books Online: > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx > SQL 2000: > http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx > |