Comments on: Can’t register remote SQL 2000 server

By: findit

findit — Mon, 03 Jan 2005 10:15:42 +0000

I’ve found the difference which PC’s have. When I click on Component services ==> Computers ==> My Computer ==> Default Protocols ==> Connection-oriented TCP/IP ==> Properties, successfull computers have nothing in the Port Range area and Port range assignment set to Internet range. However, unsuccessfull PC’s have the Port range assignment set to Intranet range. What’s strange is that I can’t simply change the settings type without a manual addition of ports, like 111-40000.

By: 0ct0pus

0ct0pus — Mon, 03 Jan 2005 04:09:29 +0000

The fact that on some machines port 1433 appears as LISTENING and to some appears FILTERED might indicate that the firewall only allows the connection from certain IP range.

You might wanna check the firewall rule to allow the connection from all IP in the subnet since all clients are in one subnet.

We try to sort this out from network layer first.

By: mraslan

mraslan — Thu, 30 Dec 2004 21:02:49 +0000

No problem, just try the things i mentioned in my previous post and tell me about them

By: findit

findit — Thu, 30 Dec 2004 12:23:08 +0000

I’m sorry, I’ve checked again and want to correct my statement: telnet fails only on workstation which can’t register remote SQL server. There are no problems registering any local SQL on this WS.

By: mraslan

mraslan — Thu, 30 Dec 2004 11:30:38 +0000

i just want to confirm the following with you.
You *can* ping the SQL server from all workstations
You *can not* telnet to port 1433 from all workstations

i have some questions, do you have machines that sometimes connect and other times unable to connect to the SQL server?

on the SQL server, open start menu > programs > SQL server > Server Network Utility, in there do you have the following checkbox checked? “Force protocol encryption” and “Enable Winsock proxy”

open Enterprise Manager, right click on the server name node and get its properties, click on the connections tab, and check “Max concurrent user connections” make sure its set to “0″

try this, try to install a test sql server on the same subnet as the clients and another one in the remote site, and try to telnet to them from the clients, and tell me the results.

By: findit

findit — Wed, 29 Dec 2004 13:20:27 +0000

Hi, all!
We use only TCPIP everywhere. We can ping the server from any workstations and we can’t telnet the server from all workstations. However, it doesn’t prevent me from successfully registering the server from some of them.
There is no record for this server in the registry on WS, which are failing and its quite natural, because the name of the key is LastConnect.
Thanks

By: BeerMaker

BeerMaker — Wed, 29 Dec 2004 11:26:48 +0000

Are you using named pipes or tcp/ip as the network protocol? If its IP, can you ping the machine. If so, and you cant connect its a blocked port.

On one of the working machines with SQL Enterprise manager, look at the registry key: [HKLMSoftwareMicrosoftMSSQLServerClientSupersocketnetlib] and find the server name entry. Your entries will look like this:

-134086648:tcp:Server1,2510
-33423352:np:Server2pipesqlquery

Server1 uses tcp, Server 2 is using named pipes.

Try to map a drive to the server and see if you can connect. Id recommed using TCP and making sure the client computers use TCP as the client network protocol for sending SQL requests.

Please, post a reply when you fix the problem.

HTH