Showing posts with label remotely. Show all posts
Showing posts with label remotely. Show all posts

Wednesday, March 21, 2012

problems connecting remotely to sql server 2005

hi. im still a bit new in handling SQL and im having problems connecting to a remote sql server 2005. i have already configured the surface area to accept remote connections and am using the connection string:

SqlConnection lasConnection = new SqlConnection("user id = sa;" +

"password = 12345; server = Naomi;" +

"Trusted_Connection = yes;" +

"database = LAS;" +

"connection timeout=30");

and it returns an error of "System.Data.SqlClient.SqlException: Login failed for user 'NAOMI\Guest' "

however, when i use the application on the same computer as the server, it has no problems connecting at all. could please point me to the right direction on how i should face this problem?

thanks in advance

hi. im still a bit new in handling SQL and im having problems connecting to a remote sql server 2005. i have already configured the surface area to accept remote connections and am using the connection string:

SqlConnection lasConnection = new SqlConnection("user id = sa;" +

"password = 12345; server = Naomi;" +

"Trusted_Connection = yes;" +

"database = LAS;" +

"connection timeout=30");

and it returns an error of "System.Data.SqlClient.SqlException: Login failed for user 'NAOMI\Guest' "

however, when i use the application on the same computer as the server, it has no problems connecting at all. could please point me to the right direction on how i should face this problem?

thanks in advance

|||

I merged these threads as they appear to be duplicates.

Are you using SSIS? If not, you might want to post in the SQL Server Data Access forum.

As a quick thought, you have the security set to a trusted connection, which means you don't have to specify a user id and password. You might want to take a look at http://www.connectionstrings.com/.

|||that was weird... when i tried a different connection string without the trusted connection then configured the surface area of the sql server for remote access it just connected like magic. hehe. sorry for being so bad at this btw. i already figured out how to connect to the server using the add data connection wizard in VS2K5 but i was wondering how do i access the data using this connection? how do i open it? coz in the old style we still need a manually configure a connection string, connect it and then do the queries.|||Still not clear on whether this is SSIS - in SSIS, you'd add a new connection manager (in the lower pane in the designer) to use a connection.

Problems Connecting Remotely - Integration Services

All,
We have a new install of SQL 2005 SP1 configured with a Navision
database restored and all client tests show no issues at moment. I am
able to connect remotely via SSMS (Management Studio) from my
workstation via TCP/IP. Also installed is Integration Services. I am
able connect to the service remotely to view the Stored Packages in the
File System but unable to view the MSDB contents. The error is below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
TCP Provider: No connection could be made because the target machine
actively refused it. (Microsoft SQL Native Client)
No firewall exists on this server. Does anyone have insight to this
issue?
Thanks,
IanUpdate: Reviewing the Surface Area Configuration shows that Local and
remote connections are enabled for both TCP/IP and Named Pipes.
Connection via Named Pipes produced the similar error below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
Named Pipes Provider: Could not open a connection to SQL Server [2].
(Microsoft SQL Native Client)
Regards,
Ian

Problems Connecting Remotely - Integration Services

All,
We have a new install of SQL 2005 SP1 configured with a Navision
database restored and all client tests show no issues at moment. I am
able to connect remotely via SSMS (Management Studio) from my
workstation via TCP/IP. Also installed is Integration Services. I am
able connect to the service remotely to view the Stored Packages in the
File System but unable to view the MSDB contents. The error is below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
TCP Provider: No connection could be made because the target machine
actively refused it. (Microsoft SQL Native Client)
No firewall exists on this server. Does anyone have insight to this
issue?
Thanks,
IanUpdate: Reviewing the Surface Area Configuration shows that Local and
remote connections are enabled for both TCP/IP and Named Pipes.
Connection via Named Pipes produced the similar error below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
Named Pipes Provider: Could not open a connection to SQL Server [2].
(Microsoft SQL Native Client)
Regards,
Iansql

Problems Connecting Remotely - Integration Services

All,
We have a new install of SQL 2005 SP1 configured with a Navision
database restored and all client tests show no issues at moment. I am
able to connect remotely via SSMS (Management Studio) from my
workstation via TCP/IP. Also installed is Integration Services. I am
able connect to the service remotely to view the Stored Packages in the
File System but unable to view the MSDB contents. The error is below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
TCP Provider: No connection could be made because the target machine
actively refused it. (Microsoft SQL Native Client)
No firewall exists on this server. Does anyone have insight to this
issue?
Thanks,
Ian
Update: Reviewing the Surface Area Configuration shows that Local and
remote connections are enabled for both TCP/IP and Named Pipes.
Connection via Named Pipes produced the similar error below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
Named Pipes Provider: Could not open a connection to SQL Server [2].
(Microsoft SQL Native Client)
Regards,
Ian