October 13, 2008 at 12:55 am
Hi,
I have windows 2003 server (enterprise edition - 32 bit & SP2) with MS Sql 2000 server installed. I wanted to establish ODBC connectivity from windows XP machine to this server but could not succeed. I get some error saying can't connect to this server, permission denied. I checked with netstat -a and sql listens on default port. The software guy told me that windows server should be a domain and client machines should be a member of this domain. Is it true ? Do I need to have AD installed for ODBC connectivity ?
Please help me out. I searched on net for a week but could not find any solution.
I checked with cliconf and TCP/IP and named pipes are enabled. From 2003 server I can establish ODBC without any problem.
Awaiting your solution.
October 13, 2008 at 1:15 am
provide Windows 2003 IP Address in ODBC Configuration (instead of SQL Server name).
Note: Also check whether Windows 2003 server is accessable from Win XP command prompt.
October 13, 2008 at 3:59 am
Hi
Thanks for your prompt reply.
I checked with IP address also but no luck. And windows 2003 server is accessible from client XP machines.
October 13, 2008 at 4:30 am
Check the local area network DNS (i.e. TCP/IP) properties and other settings.
October 13, 2008 at 11:56 pm
Hi
What exactly in TCP/IP and DNS? I can access windows 2003 server from any XP machine.
Is it necessary to have AD installed to get this thing to work?
October 14, 2008 at 5:04 am
"I have windows 2003 server (enterprise edition - 32 bit & SP2) with MS Sql 2000 server installed. I wanted to establish ODBC connectivity from windows XP machine to this server but could not succeed. I get some error saying can't connect to this server, permission denied."
What kind of error message do you get." Connection failed etc:
Like "SQL server does not exist or access denied." or ?. Or "Login failed for etc".
To be short
Your description of the problem is not sufficient to guide you to a "complete" solution but:
On the XP machine you will via the control panel ODBC administrator create a ODBC data source
to the 2003 server with the MS sql server. ODBC driver for SQL-server (MDAC) is probably already
installed on the XP-machine. Lets create a system DSN (Add driver SQL server). You sholud be able to see the server name in "Which SQL Server etc" selection box. If not write the name of it and continue. Have you established a SQL Server user? If not do that and use "With SQL Server authentication etc as log in . The network log in ID will probably not work.
If you still have problems please report back.
Personally I do not use ODBC on a remote PC to get/insert data in a SQL-server as yuou have to
create the ODBC connection on each PC. I use remote oledb.
Like:
To connect to SQL Server running on a remote computer (via an IP address):
strConnect = _T("Provider=sqloledb;Network Library=DBMSSOCN;"
"Data Source=130.120.110.001,1433;"
"Initial Catalog=MyDatabaseName;User ID=MyUsername;"
"Password=MyPassword;");
An old article:
http://www.codeproject.com/KB/database/connectionstrings.aspx#OLE%20DB%20SqlServer
October 14, 2008 at 11:01 am
Maybe this link will help ...
http://www.connectionstrings.com/
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
October 15, 2008 at 12:26 am
Hi
I already tried establishing ODBC from xp machine. But getting error 'Server does not exist or access denied'.
The software is developed by other guy and he wants us to install Active Directory in Windows Server 2003 and all xp machine member of that domain, then ODBC will work.
Still confused whether AD is required for ODBC to happen or not?
Thanks for your reply.
October 15, 2008 at 12:55 am
Use the following string:
Driver={SQL Server};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
If still have problem to connect, try the following way:
* Install SQL 2000 client tools in any one of Windows XP machine and then try to connect.
* Possible install latest security patches or Serive packs in your windows 2003 server.
* Install MDAC 2.5/2.6 in XP machines.
Let me know:
What about your front-end application ?
October 16, 2008 at 10:59 am
What is the service pack level of your SQL Server? If it less than SP3a, there is a known bug where port 1433 is blocked as a listener even though it says it is enabled as the default on the server config. Run the following SQL on the server to see what is being used to listen on.
USE master
GO
EXECUTE xp_readerrorlog
The server not listening on port 1433 will block most client attempts to connect to the server which will will get the response "server does not exist or access denied".
It is recommended to upgrade to the latest SQL SP4 service pack also.
Is there any local or server firewall blocking traffic possibly?
maddog
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply