Connecting to my SQLServer installation from elsewhere

[Warlocks]

I am running SQLServer 2000 on XP and trying to connect from similar setups to my machine but getting not found message.
My Setup is Windows and SQLServer auth. and also set to allow remote connections...
However, I can seemingly connect to every installation in our building but no-one can connect to mine.
I have also Completely switched off the firewall on my machine to ensure it isn't this...

Does anyone have any reasons why people can't connect to my SQLServer but I can connect to everyone else's?

Cheers,

Woody.

 

[SQLBill]

Do they have logins on yours?

-SQLBill

Posting advice: FAQ481-4875

 

[Warlocks]

Logins have been created both for Windows Authentication and also SQLServer Authentication and tested but failed.
As mentioned, I can get on to theirs but they can't get on to mine.
I have also set any logins tried with System Administrator priv. so should be able to do anything on my machine...

 

[SQLBill]

I can get on to theirs but they can't get on to mine.

This doesn't really make a difference. You might have a login on theirs, but if they don't have a login on yours they won't connect. But you say there are logins...

What errors are you getting (In SQL Server Error Logs and look also in the Windows Event Viewer logs)?

What port is your SQL Server instance using? Maybe, the other instances are using the default port and you are using something else.

-SQLBill


Posting advice: FAQ481-4875

 

[mrdenny]

The first thing to do is to check for basic connectivity.

From someone elses machine from to a command prompt and telnet to your machine on port 1433. If it connects then the network connection is working, if it doesn't then there is something blocking the connection. A router ACL, a firewall, etc.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(Not quite so old any more.)

 

[Warlocks]

OK.
Denny, I tried your theory and you are correct with the fact that the telnet attempt fails on my port 1433.
I was then advised by our network person to go into properties and choose the Network Configuration button and found that there were no enabled protocols. He then advised on putting across the TCPIP protocol and checked properties and found the port number 1433 (which would seemingly answer the question).
However, now my installation is screwed as it won't start my local installation even on my machine anymore. The message in the Event Log is something to do with encryption... I have copied the messages below in the order they will have been logged:

1 - Encryption requested but no valid certificate was found. SQL Server terminating.

2 - 19015 :
Encryption requested but no valid certificate was found. SQL Server terminating.

3 - Error: 17826, Severity: 18, State: 1
Could not set up Net-Library 'SSNETLIB'.

4 - 17120 :
SQL Server could not spawn FRunCM thread.

Note that I then checked an installation that was working (and was able to be connected to) and they also had Named Pipes enabled.
However, I have tried to start SQLServer from command line with minimum config (using -c -f) but still the same error message appears so I am now unable to change the Enabled Protocols and can't find any reference to doing it manually in Books Online.

How can I now either get rid of the TCPIP or add the Named Pipes so that I can start the instance again?

Cheers,

Woody.

 

[Warlocks]

An update from previous.
Found the problem with loss of connection and sorted that.
However, I still have the same issues as before whereby I can't connect through port 1433 to my machine (even FROM my machine!?!).
Firewall is switched off and I don't think there are any routers that would affect the connection. Anyway, that wouldn't explain the fact that I can connect to a colleagues machine but he cannot connect to mine!!!

 

[Catadmin]

Have you verified that your SQL Server actually uses port 1433 instead of another port? The server properties should tell you that.

Also, what OS is your friend using and are you using? Windows XP Service Pack 2 automatically puts up a PC Firewall which has to be disabled or have Port 1433 drilled through it.

Firewalls hide in the most innocuous places these days. @=)



Catadmin - MCDBA, MCSA
"If a person is Microsoft Certified, does that mean that Microsoft pays the bills for the funny white jackets that tie in the back???

 

[mrdenny]

You have to have TCP enabled to be able to connect on port 1433. When you enable it do not check the require encryption option. That will requre a certificate to encrypt the data over an ssl connection.

In order to connect to the SQL Service, you've got to have at least one network protocol.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(Not quite so old any more.)

 

[logicalunatic]

Also...

Make absolutely sure that you have upgraded to the latest service pack...

http://www.microsoft.com/sql/downloads/default.asp

It appears SQL Server likes to shut itself down if it's out of date. Just spent a few hours figuring that one out

 

[Warlocks]

Guys,

Thanks for all your assistance.
I finally have it that other users can now see my database installation...
To be honest, not sure which fixed it as I went through and did the suggestions all at once so thanks to all for your effort.

Woody.