| Author |
Topic |
|
aclarke
Posting Yak Master
133 Posts |
 Posted - 2003-10-21 : 19:14:01
|
| Hi. I'm trying to connect to a SQL Server 7.0 server with v.2000 client tools. I've enabled multiprotocol on both ends, along with Named Pipes and TCP/IP. I ultimately want to use encryption, but I've tried with the "enable multiprotocol encryption" both checked and unchecked and I get the same error.Then I went into the SQL 2000 client utilities and created an alias to my server, using multiprotocol.When I try to connect via Enterprise Manager to the alias, I get this error:A connection could not be established to TEST_ALIAS.Reason: SQL Server does not exist or access denied.ConnectionOpen (Connect())..Please verify SQL Server is running and check SQL Server registration properties (by right-clicking the TEST_ALIAS node) and try again.I tried this alias using TCP/IP and it works. So there's a problem with named pipes. Maybe I'm not able to authenticate with the server for some reason?Thanks for any thoughts and help,- Andrew. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-21 : 20:01:33
|
| Try an alias just on named pipes. Named pipes rides on TCP/IP, so I don't think that anything needs to be enabled on the network.What is your named pipe set to?Tara |
 |
|
|
aclarke
Posting Yak Master
133 Posts |
Posted - 2003-10-21 : 20:12:00
|
| Hello Tara. I set up an alias called TEST_ALIAS and used my server's IP address as the Server Name. I left the "Additional Parameters" field blank, and tried to connect to TEST_ALIAS in Enterprise Manager using Windows Authentication. That's how I got the error.Then I went back into the Client Network Utility and changed my alias to using TCP/IP and it worked fine.- Andrew. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-21 : 20:17:06
|
| I do not have an "Additional Parameters" field in my Client Network Utility. Could you check out the setting in your registry, which is what Client Network Utility writes the information to?HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectToDouble click on your alias to get the data needed. Post it in this thread.Tara |
|
|
|
aclarke
Posting Yak Master
133 Posts |
Posted - 2003-10-21 : 20:23:42
|
| Value name: TEST_ALIASValue data: DBMSRPCN,222.222.2.22Actually it's the server's IP instead of 222.222.2.22 but you get the point. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-21 : 20:31:23
|
| What does the value data look like when it is named pipes? For me, I have:DBNMPNTW,\\tduggan\pipe\sql\queryWhere tduggan is the name of the server, but it could also be IP address. The named pipe works for me, so I'm guessing that your problem could be network related. Try creating an alias on the server. Then try connecting with named pipes and multiprotocol using the alias. If you get the error there, then there is a configuration problem on the server although I'm not sure what it would be. If you don't get the error, then the problem is either with the client machine or with the network.Tara |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-10-21 : 22:44:59
|
quote:
Named pipes rides on TCP/IP
No it does not. I've been able to use named pipes successfully when I had no TCP/IP access whatsoever. They are completely independent protocols. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-22 : 12:02:14
|
| Hmmm, that's what a network administrator had told me a couple of years ago. He explained that named pipes wasn't really a protocol, that it rides with another protocol and most commonly rides with IP. He was the lead network admin on that contract, but he could have been wrong.The discussion had come up due to client machines failing to connect to a server over named pipes.Tara |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-10-23 : 00:29:43
|
| "Protocol" might be the wrong term, "library" is definitely correct. There's a nice section in [b]Inside SQL Server[b] (6.5) where Ron Soukup described the impetus for creating named pipes. At the time TCP/IP was not as widely used as it is today. Named pipes was the fastest protocol for SQL Server then, but once TCP/IP became omnipresent Microsoft has focused on it instead and it is now the fastest.The client machines might have been failing if they were not running on a Windows NT-level OS (like Win95, 98 or ME). These OS's don't work with named pipes, which to me indicates that named pipes doesn't use TCP/IP at all. Otherwise it would be a simple matter to layer it on top so that they could work with it. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-23 : 12:12:37
|
| Thanks for the clarification. And yes the machines were non NT-level, I believe they were 95 or 98. But they were able to use named pipes to connect to the server. It was just that a couple of times, they would lose connectivity for quite a few hours and nothing appeared wrong on the network. Suddenly it would start working again for an entire office building without making any changes. It always worked on the machines at our office building during this problem. So if named pipes doesn't ride on TCP/IP, then why can you put the IP address in the pipe:DBNMPNTW, \\111.11.111.11\sql\pipe (or whatever it is)Just curious.Tara |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-10-23 : 14:54:32
|
| Don't know. Maybe it does overlay named pipes on TCP/IP, but it isn't required for it to work. |
|
|
|
aclarke
Posting Yak Master
133 Posts |
Posted - 2003-10-23 : 18:59:49
|
quote:
Originally posted by tduggan
What does the value data look like when it is named pipes? For me, I have:DBNMPNTW,\\tduggan\pipe\sql\queryWhere tduggan is the name of the server, but it could also be IP address. The named pipe works for me, so I'm guessing that your problem could be network related. Try creating an alias on the server. Then try connecting with named pipes and multiprotocol using the alias. If you get the error there, then there is a configuration problem on the server although I'm not sure what it would be. If you don't get the error, then the problem is either with the client machine or with the network.Tara
|
|
|
|
|
How can I get multiprotocol working?