Could someone please tell me what I need to do to be able to connect a user, who is on a Novell Network to a SQL Server using tcp/ip.
Do I need to make the user a member of the NT Domain or have a local user account on the NT box, where the SQL Server is installed.
We have installed a SQL 2000 server on a windows xp-pro machine and succesfully installed DotNetNuke. Now is the problem that there is no way we can manage to get a client connected. We have tried everything, changing tcp port, setting permissions, changing registry according to document 307197 in the microsoft database and nothing helps. The only thing we can see is that in the serverlog we get a message stating that "SuperSocket Info : Bind failed on TCP port 1433". Can anyone help?Regards Ulla & Tom
I'm brand new to SQL server and all that and am having a little bit of hassles getting up and running.
I have a server 2003 computer running on my lan that I installed SQL server 205 express onto. I have attatched a database that I got with a C# book..
When I go into visual studio 2005 on the client to try and connect to te server vs cannot see the server at all.. the only server that displays is the client computer(which isn't a server??) I know there is a valid connection between the two computers because I login to the server using remote access..
Also, I have enabled TCP in the SQL server configuration program..
I wonder is there any beginnger guides on how to get the whole show up and running??
I have a Visual C# WinForms app which I am accessing a SQL Server 2005 database with. On the Server, I have allowed remote connections (TCP and named pipes) and enable SQL Browser as per instructions on MSDN. The app works fine on the development machine.
Server name is <machine name>SQLEXPRESS, connecting with Windows Authentication. Server log states that it is listening on [ 'any' <ipv4> 3153]. Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
On the client (local network), when trying to open the database I get this error still:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Also on the client, I can go into the ODBC Data Source Administation, and connect to the SQL Server Database that way successfully.
What further steps can I take to allow the client to access the SQL Server?
I m a new member to this forum. Im a hardware engineer who rectify aome software related issues. Now our employees having problem with connecting their XP prof based clients to 2003 server from SQL query analyzer. I tried refresh sql server manager in server and tried restarting the server machine many times. sometimes it the client machine connects and disconnects immediately. i aslo tried changing the poll interval , but no use.
waiting for a speedy solutin... i know this is as easy query.
When you connect to SQL Server using SQLConnection, how to set client machine name(or IP address) so that you can monitor the process on Server side using Enterprise Manager?
I have a Visual C# WinForms app which I am accessing a SQL Server 2005 database with. On the Server, I have allowed remote connections (TCP and named pipes) and enable SQL Browser as per instructions on MSDN. The app works fine on the development machine.
Server name is <machine name>SQLEXPRESS, connecting with Windows Authentication. Server log states that it is listening on [ 'any' <ipv4> 3153]. Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
On the client (local network), when trying to open the database I get this error still:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Also on the client, I can go into the ODBC Data Source Administation, and connect to the SQL Server Database that way successfully.
What further steps can I take to allow the client to access the SQL Server?
I have a Visual C# WinForms app which I am accessing a SQL Server 2005 database with.
On the Server, I have allowed remote connections (TCP and named pipes) and enable SQL Browser as per instructions on MSDN. The app works fine on the development machine.
Server name is SQLEXPRESS, connecting with Windows Authentication. Server log states that it is listening on [ 'any' 3153]. Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
On the client (local network), when trying to open the database I get this error still:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Also on the client, I can go into the ODBC Data Source Administation, and connect to the SQL Server Database that way successfully.
What further steps can I take to allow the client to access the SQL Server?
I am trying to link tables from an access 2003 frontend to sql server 2005 backend.
I am doing this in a vmware test environment. I am using vmware server and running sbs 2003 and xp sp2 client. Both virtaul machine can talk to each other(using local host connection).
I have tried to create a dsn to the sql server but i cannot connect. I can ping the sbs server through the command interface but the error i get when i try to connect is :
Connection failed: Sql state: hyt00 sqlserver error: 0 microsoft odbc sql server driver timeout expired.
spent a day trying various combinations - still no joy.
We are unable to connect with Client SQL database server using VPN connection, even we are able connect with their intranet site.
We tried to connect using IP address, but no success. After that tried to ping that server with server name and IP address using command prompt, but got request time out error.
Help Me In This : My Client Applicaion Can't Connect To Sql Server 2005 Express
Story :
I have Application Coded by C# To Connect To Sql Express Data Base , And I have Form In This Application To Configure The Connection String .
This Application Is Tested Local Ok (MY Server Name :- .SqlExpress ) When i User This Application In Client In Same Network And Try To Connect To The Data Base In Server (My Server Name :- ServerNameSqlExpress ) This Error Appeared "Server Does Not Exist Or Access Denied"
Note : I Configure My Server Configuration And Enabled The Tcp/ip .
Questions : How Can I Connect To Data Base From Client To Server Through NetWork Connection Using ServerNameInstance ?
How Can I Connect To Data Base From Client To Server Through NetWork Connection Using IpInstance ?
How Can I Connect To Data Base From Client To Server Through InterNe ?
All This Questions Using Sql Server 2005 Express .
I need to setup a server on a network where Novell is the NOS.
question : how can I configure the server (NT4 sp4 / SqlServer 7.0 ), so that the "Novell User/PW" will authenticate for my database on the NT/SqlServer server. What I am trying to avoid is the duplication of user maintenance on the system.
Windows 2003 Server and all client PCs are all on the same network. I installed SQL 2005 std version on windows server 2003 and created a database and tables in it.
I have two users, who want to connect to SQL server 2005 from their PCs (they have windows XP):
These are two things that I need to facilitate:
1) They want to be able to write queries using Query Designer and run from their PCs.
2) I created an MS Access database on my PC, I want to use Access database as a front end to the SQL server database. I will create queries, forms in Access DB, and I want to be able to get the data from SQL server Database to do this. I guess I can use ODBC to connect to tables in SQL server database.
3) I want to connect SQL server to Oracle database, and run oracle stored procedures. I want to load the results of oracle stored procedures into SQL server database tables. I guess I will use IIS for this.
Any suggestions are appreciated, especially with item number 1.
Someone please help me before I loose all of my hair :mad: !!!
I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).
I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.
Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.
So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!
Anyone support a config where you have an unix/linux (AIX here) ODBCclient connection to SQL Server database? I am looking for a simple,supportable configuration that does not require me to learn perl orinstal a bunch of crap gnu shareware on enterprise class machines.Please help!
We use Novell NDS security to access applications on NT servers. I have an application on an NT server that will connect to an other NT server that is running SQL Server 7.0. Is there any way to have/use the Novell login/password passed to SQL Server 7.0 once logged on to the NT application server?
Either passing as a login/password or converted to a group for SQL Server use. I would like to limit the number of times a business user needs to type a login/password. Hopefuly this would work like "trusted connections".
I am running SQL Server 6.5 on a Windows NT 4.0 Server. File and printer services etc. are handled by Novell. This server is the only NT box in the shop. All workstations are running Windows 95. My problem is that response from the SQL server is extremely slow. When I make a request to the server from a workstation my Novell server utilization peaks for several seconds.I dont know why the Novell server should have any involvment? What Net libraries and protocols should I be using?
I am trying to setup a client alias to connect to a named instance on another server.
TITLE: Connect to Server ------------------------------ Cannot connect to fred. ------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
[URL]
The network path was not found
------------------------------ BUTTONS: OK ------------------------------
I have set up the alias on the server and as expected it works. On the client side I have used the SQL Server Client Network Utility to configure the client side alias but no luck
I am using TCP/IP with a specific port ..
By the way the SQL is SQL Server 2012 Ent and the O/S is Windows 2012 R2 minshell
When I'm using SQL server 2005, and ODBC drive €œSQL Native Client€? I get an error when executing the below given code. Error Message: €œTransaction cannot start because more than one ODBC connection is in use.€?
But this works well with SQL Server 2000 with ODBC drive "SQL Native Client" and in SQL server 2005 also when I used ODBC drive €œSQL Server€?.
I used aTrgConn.Execute(€œBegin Transaction€?) and it's working properly. But unfortunately I cannot use this method, because I want to run the same code with Oracle ODBC as well. Is this a known issue in SQL Native client drive with SQL server 2005? Do you know a solution for this?
Please Help..............
Thanks in advance.
Code:
Dim aTrgConn As New ADODB.connection Dim aCmdIns As New ADODB.Command Dim aCmdUpd As New ADODB.Command
aTrgConn.Open sConnStr
Set aCmdIns.ActiveConnection = aTrgConn Set aCmdUpd.ActiveConnection = aTrgConn
after installing SQL Server 2008 R2 and the Reporting Services, I've managed to access the Report Manager URL....Reports through the web browser on the machine itself. But if i am trying to connect to on my client browser it does not find the Report Server.Do I need to configure the server in any way? Do I need to configure the firewall?
Upgraded Enterprise Mgr. from SQL7 to SQL 20000. When trying to connect to SQl 2000 server using Enterprise mgr using TCP/IP am getting Invalid attribute/option identifier any suggestions???
i am using sql2005 on win2k3(sbs) platform(domain concept).my client is winxp.when i am tring to connect from client pc i am getting following error message.
connection failed sql state 01000 sql server error 233 microsoft odbc sql server driver(dbnetlib) connection open (connect) connection failed sql state 08001 sql server error 17 microsoft odbc sql server driver(dbnetlib)sql server does not exist or access denied
Here is my problem: I have SQLEXPRESS running with Windows Authentication on a "server" PC named "ASUS1", and I need to connect from a "client" PC named "Presario1", user "Mauro", connected through a peer network (I use a cross-over cable); both PCs belongs to the same workgroup named "RMT-WORK", and they can see each others shared folders without problems.
I have installed the connectivity components + Management Studio Express on Presario1, and enabled named pipes and TCP/IP protocols; then I've got SQL Browser running. I have also added the Login "Guest" on ASUS1SQLEXPRESS.
When I start Management Studio Express on Presario1 and browse for servers I can select "ASUS1" as database engine but when I try to connect I receive "Error 40: could not open a connection to SQL Server" (same result using SQLCMD); I have tried to add on ASUS1SQLEXPRESS a user "Presario1Mauro" with "CREATE LOGIN [Presario1Mauro] FROM WINDOWS" but I receive a "Windows user not found" error...
i have a small problem to connect SQL Native ODBC Client to a mirrored Database. The connection goes without any problem when I connect to a primary Database, but when i give this connect string to an ODBC Client ""Server=Partner_A; Failover Partner=Partner_B; Database=XXX; Network=dbmssocn"", then i get an connect fail. There are no firewalls and other things on the network. I am also able to connect to a mirror database during failover, but I'm not able to set both servers on the ODBC Connection.