can only connect one way - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

can only connect one way

Author

Topic

evidica
Starting Member

17 Posts

Posted - 2007-01-16 : 16:31:45

I have tried everything I can think of to no avail. I have two SQL 2000 servers running in the same workgroup. Server 1 has been around for a long time and Server 2 is new. I can connect to Server1 from Server2 but the the other way around. Any ideas?

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-16 : 16:40:47

Try adding an alias using Client Network Utility to the server where you receive the error.

Tara Kizer

evidica
Starting Member

17 Posts

Posted - 2007-01-16 : 16:49:55

Did that already, nothing changed.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-16 : 16:57:27

Please post the alias' definition.

Also please post the error.

Tara Kizer

evidica
Starting Member

17 Posts

Posted - 2007-01-16 : 17:02:22

Server Alias: DLSQL
Network Library: TCP/IP
Connection Paramerters: DLSQL

Error when trying to connect in Query Analyzer:

Unable to connect to server DLSQL:

Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-16 : 17:13:12

I'd suggest providing the port number in the alias.

Also, try connecting with this in Query Analyzer:

tcp:TheServerName,ThePortNumber

Tara Kizer

evidica
Starting Member

17 Posts

Posted - 2007-01-16 : 17:17:41

did both to no avail.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-16 : 17:25:20

Can you ping the server?

Tara Kizer

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-01-16 : 17:27:32

can any other system connect to the database on Server2?

-ec

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-16 : 17:32:02

For the server that you can't connect to, is it running Windows XP sp2?

Tara Kizer

evidica
Starting Member

17 Posts

Posted - 2007-01-16 : 17:34:43

I can ping, no other computers can connect to it and it is running Windows Server 2003 SP 1

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-01-16 : 20:01:19

quote:
Originally posted by evidica

I can ping, no other computers can connect to it and it is running Windows Server 2003 SP 1

it doesn't sound like the TCP/IP protocol is enabled. Or, you are running a SQL Server service pack older than SP3a.

Run the following command on the Server you are having problems with:

SELECT @@VERSION

paste the results here for us.

-ec

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-16 : 20:18:05

To verify if TCP/IP protocol is enabled for the SQL Server, go to the problematic SQL Server, open up Server Network Utility and check to see if TCP/IP is listed in the enabled protocols on the first tab.

Tara Kizer

monty
Posting Yak Master

130 Posts

Posted - 2007-01-17 : 01:17:42

one of the reason for sql server driver Failing to Connect over TCP/IP is because if it uses three Parameters in Address Keyword

plz read this link:
http://support.microsoft.com/kb/311836

and upgrade the MDAC to the latest version to see if it works.

its me monty

evidica
Starting Member

17 Posts

Posted - 2007-01-17 : 10:03:45

Version info:

Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Personal Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

I have TCP/IP enabled

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-01-17 : 11:07:51

quote:
Originally posted by evidica

Version info:

Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Personal Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

I have TCP/IP enabled

You need to apply the latest (at least SP3a) to SQL Server. If you check the application event log on this machine you will see that TCP/IP protocol for SQL Server is disabled by the Operating System since you are running a database that is susceptible to the SQL Slammer worm (among other things). This is actually a feature of Win2k3 SP1.

-ec

evidica
Starting Member

17 Posts

Posted - 2007-01-17 : 12:49:59

ahh, ok, thank god Microsoft covered my backside there. I applied SP4 and it is functioning properly. Thanks all for the help.

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-01-17 : 13:36:19

quote:
Originally posted by evidica

ahh, ok, thank god Microsoft covered my backside there. I applied SP4 and it is functioning properly. Thanks all for the help.

Glad to hear you got things working properly.

but just to clarify things, the 8.00.194 version indicated to me that you were running the initial release of SQL 2000 (no service packs applied). Everyone should be running a minimum release of .818. .818 is SP3a + MS03-31 hotfix. btw, version .760 is the minimum required by win2k3 SP1 so tcp/ip protocol doesn't get disabled.

-ec

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources