December 4, 2013 at 10:38 am
Lynn Pettis (12/4/2013)
HowardW (12/4/2013)
Lynn Pettis (12/4/2013)
Just a quick question, does anyone know what port(s) SQL Server uses for its Linked Servers?Whichever port the remote instance is listening on, it's just an outgoing connection to a data source, like any application OLE DB/ODBC connection. The direction of a linked server is one way, so it doesn't create a local listener or anything like that...
So if it is the default instance the linked servers use port 1433?
This works the same way as clients.
the linked server connects to 1433 on the default instance, but the source port is chosen the same way it is for your client.
Not to be pedantic, but I wasn't sure if you were asking for the source or destination side of the linked server.
December 4, 2013 at 10:58 am
Steve Jones - SSC Editor (12/4/2013)
Lynn Pettis (12/4/2013)
HowardW (12/4/2013)
Lynn Pettis (12/4/2013)
Just a quick question, does anyone know what port(s) SQL Server uses for its Linked Servers?Whichever port the remote instance is listening on, it's just an outgoing connection to a data source, like any application OLE DB/ODBC connection. The direction of a linked server is one way, so it doesn't create a local listener or anything like that...
So if it is the default instance the linked servers use port 1433?
This works the same way as clients.
the linked server connects to 1433 on the default instance, but the source port is chosen the same way it is for your client.
Not to be pedantic, but I wasn't sure if you were asking for the source or destination side of the linked server.
Without getting specific we have one site where we aren't able to configure and use linked servers either from that site or to that site.
We get the following:
OLE DB provider "SQLNCLI" for linked server "nnn.nnn.nnn.nnn" returned message "Unable to open logical session".
Msg 65535, Level 16, State 1, Line 0
SMux Provider: Physical connection is not usable [xFFFFFFFF].
OLE DB provider "SQLNCLI" for linked server "nnn.nnn.nnn.nnn" returned message "Unable to open logical session".
Msg 65535, Level 16, State 1, Line 0
SMux Provider: Physical connection is not usable [xFFFFFFFF].
We have no issues using Linked Server to or from other sites.
December 4, 2013 at 11:40 am
Steve Jones - SSC Editor (12/4/2013)
Check. Removed.Thanks. Feel free to PM me in the future.
Sorry, yes, I meant to. I forgot :blush:
December 4, 2013 at 11:53 am
Lynn Pettis (12/4/2013)
Steve Jones - SSC Editor (12/4/2013)
Lynn Pettis (12/4/2013)
HowardW (12/4/2013)
Lynn Pettis (12/4/2013)
Just a quick question, does anyone know what port(s) SQL Server uses for its Linked Servers?Whichever port the remote instance is listening on, it's just an outgoing connection to a data source, like any application OLE DB/ODBC connection. The direction of a linked server is one way, so it doesn't create a local listener or anything like that...
So if it is the default instance the linked servers use port 1433?
This works the same way as clients.
the linked server connects to 1433 on the default instance, but the source port is chosen the same way it is for your client.
Not to be pedantic, but I wasn't sure if you were asking for the source or destination side of the linked server.
Without getting specific we have one site where we aren't able to configure and use linked servers either from that site or to that site.
We get the following:
OLE DB provider "SQLNCLI" for linked server "nnn.nnn.nnn.nnn" returned message "Unable to open logical session".
Msg 65535, Level 16, State 1, Line 0
SMux Provider: Physical connection is not usable [xFFFFFFFF].
OLE DB provider "SQLNCLI" for linked server "nnn.nnn.nnn.nnn" returned message "Unable to open logical session".
Msg 65535, Level 16, State 1, Line 0
SMux Provider: Physical connection is not usable [xFFFFFFFF].
We have no issues using Linked Server to or from other sites.
Just curious, have you checked the Windows Firewall rules for TCP 1433 and 1434 as well as UDP 1434? Does telnet or SSMS work to the remote location (from the source server) ?
Any routers or firewall configured between source and destination that might have a misconfigured rule?
And it is a default instance, right? Has somebody changed the port for SQL in Server Configuration?
Is any server able to create a linked server to the server in question?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 4, 2013 at 11:55 am
WayneS (12/4/2013)
Paul White (12/3/2013)
dwain.c (12/3/2013)
Steve,I thought you might want to see this:
http://www.sqlservercentral.com/Forums/FindPost1519227.aspx
By alerting you, I am not vouching for its veracity.
I have a copy of Itzik's book, and I can vouch for this "article" being very substantially word-for-word extracts and code samples from Chapter 1.
What's worse is the very prominent links to http://www.learn-with-video-tutorials.com/window-functions-tutorial offer to sell you the same material for USD 29. The free sample shows the video is simply Itzik's text being read by a software voice. Yes, seriously.
Sigh. The only think this person changed was the table name of some of the code. Everything else that is the text of the article is, word-for-word, a direct copy/paste from Itzik's book.
Ugh. Unfortunate really.
I need to read that book still.
I noticed that the sample code was still available on the article. Not sure if that is something that should be removed or not. Just bringing it up for consideration.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 4, 2013 at 1:09 pm
SQLRNNR (12/4/2013)
Lynn Pettis (12/4/2013)
Steve Jones - SSC Editor (12/4/2013)
Lynn Pettis (12/4/2013)
HowardW (12/4/2013)
Lynn Pettis (12/4/2013)
Just a quick question, does anyone know what port(s) SQL Server uses for its Linked Servers?Whichever port the remote instance is listening on, it's just an outgoing connection to a data source, like any application OLE DB/ODBC connection. The direction of a linked server is one way, so it doesn't create a local listener or anything like that...
So if it is the default instance the linked servers use port 1433?
This works the same way as clients.
the linked server connects to 1433 on the default instance, but the source port is chosen the same way it is for your client.
Not to be pedantic, but I wasn't sure if you were asking for the source or destination side of the linked server.
Without getting specific we have one site where we aren't able to configure and use linked servers either from that site or to that site.
We get the following:
OLE DB provider "SQLNCLI" for linked server "nnn.nnn.nnn.nnn" returned message "Unable to open logical session".
Msg 65535, Level 16, State 1, Line 0
SMux Provider: Physical connection is not usable [xFFFFFFFF].
OLE DB provider "SQLNCLI" for linked server "nnn.nnn.nnn.nnn" returned message "Unable to open logical session".
Msg 65535, Level 16, State 1, Line 0
SMux Provider: Physical connection is not usable [xFFFFFFFF].
We have no issues using Linked Server to or from other sites.
Just curious, have you checked the Windows Firewall rules for TCP 1433 and 1434 as well as UDP 1434? Does telnet or SSMS work to the remote location (from the source server) ?
Any routers or firewall configured between source and destination that might have a misconfigured rule?
And it is a default instance, right? Has somebody changed the port for SQL in Server Configuration?
Is any server able to create a linked server to the server in question?
There could easily be routers and firewalls configured that are preventing us from using Linked Servers. Lets just say this site is extremely tied down. I can connect to the server using SSMS from outside, but can't get a linked server to work. Not sure what else we can request from the those responsible for the network to get linked servers to work. Most places I have been they just work, and they work here to other sites, just not this one.
We can't even get xp_cmdshell to run on this site. When upgrading we use Redgate Multi Script to run SQL that uses xp_cmdshell to run a command line command to shutdown DataXtend replication. This site we have to RDP into the server and do that manually from a command prompt.
Edit: And no, I have tried to create a linked server on other sites with no luck.
December 4, 2013 at 1:15 pm
Lynn Pettis (12/4/2013)
There could easily be routers and firewalls configured that are preventing us from using Linked Servers. Lets just say this site is extremely tied down. I can connect to the server using SSMS from outside, but can't get a linked server to work. Not sure what else we can request from the those responsible for the network to get linked servers to work. Most places I have been they just work, and they work here to other sites, just not this one.
You're connecting from SSMS on your workstation, right? Do you have a local instance you can create a linked server from on your laptop to this server? It should be the same connection as from SSMS. don't delegate or use impersonation, specify your credentials.
December 4, 2013 at 1:28 pm
Steve Jones - SSC Editor (12/4/2013)
Lynn Pettis (12/4/2013)
There could easily be routers and firewalls configured that are preventing us from using Linked Servers. Lets just say this site is extremely tied down. I can connect to the server using SSMS from outside, but can't get a linked server to work. Not sure what else we can request from the those responsible for the network to get linked servers to work. Most places I have been they just work, and they work here to other sites, just not this one.You're connecting from SSMS on your workstation, right? Do you have a local instance you can create a linked server from on your laptop to this server? It should be the same connection as from SSMS. don't delegate or use impersonation, specify your credentials.
Nope, connecting from SSMS on the server where I am trying to create the linked server. Currently our workstations do not have the client tools installed. We actually have to RDP to servers to do our work.
December 4, 2013 at 2:58 pm
Lynn Pettis (12/4/2013)
Steve Jones - SSC Editor (12/4/2013)
Lynn Pettis (12/4/2013)
There could easily be routers and firewalls configured that are preventing us from using Linked Servers. Lets just say this site is extremely tied down. I can connect to the server using SSMS from outside, but can't get a linked server to work. Not sure what else we can request from the those responsible for the network to get linked servers to work. Most places I have been they just work, and they work here to other sites, just not this one.You're connecting from SSMS on your workstation, right? Do you have a local instance you can create a linked server from on your laptop to this server? It should be the same connection as from SSMS. don't delegate or use impersonation, specify your credentials.
Nope, connecting from SSMS on the server where I am trying to create the linked server. Currently our workstations do not have the client tools installed. We actually have to RDP to servers to do our work.
Is the remote server physical or virtual?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 4, 2013 at 3:00 pm
SQLRNNR (12/4/2013)
Lynn Pettis (12/4/2013)
Steve Jones - SSC Editor (12/4/2013)
Lynn Pettis (12/4/2013)
There could easily be routers and firewalls configured that are preventing us from using Linked Servers. Lets just say this site is extremely tied down. I can connect to the server using SSMS from outside, but can't get a linked server to work. Not sure what else we can request from the those responsible for the network to get linked servers to work. Most places I have been they just work, and they work here to other sites, just not this one.You're connecting from SSMS on your workstation, right? Do you have a local instance you can create a linked server from on your laptop to this server? It should be the same connection as from SSMS. don't delegate or use impersonation, specify your credentials.
Nope, connecting from SSMS on the server where I am trying to create the linked server. Currently our workstations do not have the client tools installed. We actually have to RDP to servers to do our work.
Is the remote server physical or virtual?
And the reason I ask is that I see plenty of articles related to SQL server and VMWare vms with various nic configurations that throw your errors.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 4, 2013 at 3:27 pm
SQLRNNR (12/4/2013)
SQLRNNR (12/4/2013)
Lynn Pettis (12/4/2013)
Steve Jones - SSC Editor (12/4/2013)
Lynn Pettis (12/4/2013)
There could easily be routers and firewalls configured that are preventing us from using Linked Servers. Lets just say this site is extremely tied down. I can connect to the server using SSMS from outside, but can't get a linked server to work. Not sure what else we can request from the those responsible for the network to get linked servers to work. Most places I have been they just work, and they work here to other sites, just not this one.You're connecting from SSMS on your workstation, right? Do you have a local instance you can create a linked server from on your laptop to this server? It should be the same connection as from SSMS. don't delegate or use impersonation, specify your credentials.
Nope, connecting from SSMS on the server where I am trying to create the linked server. Currently our workstations do not have the client tools installed. We actually have to RDP to servers to do our work.
Is the remote server physical or virtual?
And the reason I ask is that I see plenty of articles related to SQL server and VMWare vms with various nic configurations that throw your errors.
All production servers are physical servers.
December 4, 2013 at 3:46 pm
Lynn Pettis (12/4/2013)
SQLRNNR (12/4/2013)
Is the remote server physical or virtual?
And the reason I ask is that I see plenty of articles related to SQL server and VMWare vms with various nic configurations that throw your errors.
All production servers are physical servers.
Based on the error
SMux Provider: Physical connection is not usable [xFFFFFFFF]
I would still look at the NIC for configuration errors or outdated drivers.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 4, 2013 at 10:36 pm
In unrelated news, slightly belated drum rolls please..
<---------
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2013 at 11:05 pm
GilaMonster (12/4/2013)
In unrelated news, slightly belated drum rolls please..<---------
Congrats
Is the next level SSC-Eternal?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 5, 2013 at 5:31 am
GilaMonster (12/4/2013)
In unrelated news, slightly belated drum rolls please..<---------
Congratulations, Gail. I remember reading a post once where you said that you crossed the 2,000 point boundary. It doesn't seem that long ago. 😉 Well done.
Viewing 15 posts - 42,286 through 42,300 (of 66,738 total)
You must be logged in to reply to this topic. Login to reply