Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2000 > SQL Server 2000
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old November 29th, 2004, 04:28 PM
Registered User
 
Join Date: Nov 2004
Location: , , .
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default CAN NOT CONNECT TO SQL SERVER 2000 REMOTELY

HI Everyone,

I am having trouble with connecting to the sql server 2000 database located on the network.

I installed win2000 server and sql server 2000 database to the server machine ( new PC). Using an available network cable and plugged it to that PC. Then I did the upsizing an access database to the sql server database by moving all tables to that sql server. I can open the forms/tables of the access database that are linked to the sql server's ones locally. But it does not work when open them from a client machine, such as my machine.

For ex: I created a shared drive on the server PC and put the front-end access database in it. Go to my PC and map a network drive to that PC. Double click that access database on the mapped drive and would see all tables including the mapped ones. Then, I tried to open one of the mapped table and see a dialog :SQL Server Login. I put the server name ( used the same as the server PC's name) in the SERVER box, put a check for Using Trusted Conneciton and click OK. It seems to hang up for awhile and the error message is:

==================
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied
==================

But it is OK when I use the front-end access database on the server PC.

What I can find out for now is the name of the server PC ("PC_NAME") is different from the network name ("NETWORK_NAME") that associated with the IP ("xxx.yyy.zz.vv") that the server PC is using through the network cable.

When I ping -a IP, I can see the name as NETWORK_NAME or ping NETWORK_NAME it will display the IP. But when I ping the PC_NAME, then it says not found.

when I do telnet NETWORKNAME/PC_NAME 1433, then It says:

X:\>telnet warehouse 1433
Connecting To warehouse...Could not open a connection to host on port 1433 : Con
nect failed

Does anyone know this can help me out? I will way thanks in advance.

Again, thank you for your reading it.

Charlie Tran

Reply With Quote
  #2 (permalink)  
Old November 29th, 2004, 05:14 PM
Friend of Wrox
 
Join Date: Nov 2003
Location: Lehigh Acres, FL, USA.
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to jemacc
Default

Can you connect to your database using Query Analyzer? Make sure your account has permission to the newly created database.

1. Do you have SQL SP3a installed.? If no, install sp3a
2. Make sure to check clients connectivity and use TCP/IP
3. Test connection using SQL Authentication.



Jaime E. Maccou
Applications Analyst
Reply With Quote
  #3 (permalink)  
Old November 29th, 2004, 06:26 PM
Registered User
 
Join Date: Nov 2004
Location: , , .
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi jemacc,

Here is my response:

 Can you connect to your database using Query Analyzer?
=> YES. I open the Query Analyzer from sql server successfully with username = "sa" and pwd = "".

Make sure your account has permission to the newly created database.
=> What is it? Please be more specifying...?

1. Do you have SQL SP3a installed.? If no, install sp3a
=> YES
2. Make sure to check clients connectivity and use TCP/IP
=> How can I check it?
3. Test connection using SQL Authentication.
=> How can I do this?

thank you and I am waiting for your response.

Charlie Tran




Reply With Quote
  #4 (permalink)  
Old November 29th, 2004, 08:51 PM
Friend of Wrox
 
Join Date: Nov 2003
Location: Lehigh Acres, FL, USA.
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to jemacc
Default

Here is my response:

 Can you connect to your database using Query Analyzer?
=> YES. I open the Query Analyzer from sql server successfully with username = "sa" and pwd = "".

Make sure your account has permission to the newly created database.
=> What is it? Please be more specifying...?

1. Do you have SQL SP3a installed.? If no, install sp3a
=> YES
2. Make sure to check clients connectivity and use TCP/IP
=> How can I check it?

If you are using ODBC on the client front end (Check DSN connection)
If using access ADP Click File then connection.

3. Test connection using SQL Authentication.
=> How can I do this?
You have done this when you connect using the sa account in Query Analyzer.
If you are using Windows Authentication, you must use a domain account to connect to the database

Jaime E. Maccou
Applications Analyst
Reply With Quote
  #5 (permalink)  
Old July 13th, 2005, 05:08 PM
Registered User
 
Join Date: Jul 2005
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I have a VB 6.0 application which has commands to access a SQL Server 2000 database. When I ran and tested this application, it was doing okay. However, I got an error message when I made a standalone exe. The error message is "[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied."

I do check TCP/IP and port is 1433. In addition, I update the DBNETLIB.DLL by using critical update (SQLHotfix_ENU.exe).

Can anyone tell what the solution for this error is? Thanks.

Reply With Quote
  #6 (permalink)  
Old July 14th, 2005, 06:03 AM
Friend of Wrox
 
Join Date: Nov 2003
Location: Lehigh Acres, FL, USA.
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to jemacc
Default

Check and make sure you are using the same MDAC version on the client and on the server.

Jaime E. Maccou
Reply With Quote
  #7 (permalink)  
Old December 14th, 2005, 02:36 AM
Registered User
 
Join Date: Dec 2005
Location: , , .
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to nellaikumar
Default

Hi,

 I am trying to connect with SQL Server, but i got the following error.

Database server failed![DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

I tried with your previous post mail info. but I couldn't fix the problem.

Kindly help me.

With thanks in advance,

P.Nellaikumar.
Reply With Quote
  #8 (permalink)  
Old December 14th, 2005, 02:37 AM
Registered User
 
Join Date: Dec 2005
Location: , , .
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to nellaikumar
Default

Hi,

 I am trying to connect with SQL Server, but i got the following error.

Database server failed![DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

I tried with your previous post mail info. but I couldn't fix the problem.

Kindly help me.

With thanks in advance,

P.Nellaikumar.
nellaikumar2002@rediffmail.com
Reply With Quote
  #9 (permalink)  
Old December 21st, 2006, 10:34 AM
Registered User
 
Join Date: Dec 2006
Location: London, , United Kingdom.
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

It seems that this error will display for many different reasons. The reason I received it was that the Port number specified in the DSN differed from that in Enterprise Manager. To check this:

[u]In Enterprise Manager:</u>
Right-click on the appropriate Server Group
Select Properties
On the General tab, click the 'Network Configuration..' button
Select 'TCP/IP' in the 'Enabled protocols:' list box
Click Properties
Take a note of the 'Default port' number. (This number defaults to 1433. If it has been changed, it is likely that this is the source of the problem).

[u]In ODBC Data Source Administrator:</u>
Select the appropriate dsn and click 'configure'
Click 'Next'
Click 'Client Configuration..'
Check that the entry in 'Port number' matches that in Enterprise Manager. If there is no entry, try unchecking 'Dynamically determine port' and enter the port number.

This worked for me but there appear to be many reasons you could get this error.

Good luck.
Reply With Quote
  #10 (permalink)  
Old December 22nd, 2006, 04:14 PM
Friend of Wrox
 
Join Date: Aug 2004
Location: Orange County, CA, USA.
Posts: 385
Thanks: 0
Thanked 0 Times in 0 Posts
Default

troubleshooting is best done a piece at a time. I suggest the following.

1) goto the actual sql server and connect using the userid/password that you plan to use.

2) on a different box (that does not go through a firewall) try to connect using the same userid/password.

3) On the box your trying to connect from ping the server.

4) on the box your trying to connect with use the MS-SQL tools and connect with the userid/password your using.

5) setup an odbc connection using the same userid/password.

Don't proceed to the next step until the previous results in a connection. You may have firewall issues, wrong userid/password, you can't ping the server, etc. Take it a step at a time to find the problem.

Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Connect to SQL server 2000 from home! Jane SQL Server 2000 5 June 7th, 2006 03:42 PM
Connect SQL Server 2000 with VB6 sanjna000 SQL Server 2000 1 May 8th, 2006 02:01 PM
Connect remotely to SQL server rylemer .NET Framework 2.0 1 December 6th, 2005 03:16 AM
Connect to remote SQL Server 2000 using servlets Vinay Bansal Servlets 1 August 5th, 2005 12:22 AM
Access 2000 "Connect to SQL Server" cjdphlx Access VBA 1 July 17th, 2005 02:09 AM



All times are GMT -4. The time now is 03:59 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.