Showing posts with label establishing. Show all posts
Showing posts with label establishing. Show all posts

Tuesday, March 27, 2012

Establishing VPN Connection thru DTS package

Hi,
I have defined a DTS package which establishes VPN connection with my
client's server. When I execute this package thru SQL Enterprise
Manager (SEM) it works fine, but when I schedule it as a job or try to
execute thru SQL Query Analyzer using 'xp_cmdShell' stored proc, it
doesn't establish connection. NE ideas on what am I doing wrong?
Yr prompt response will be highly appreciated.
Thanks,
Um JunkWhen you execute it using xp_cmdshell the package is run under the context
of the SQL Server startup account (if the user connected via Query Analyzer
is a member of the sysadmin role) or the SQL Proxy account (if the user
connected via Query Analyzer is not a member of the sysadmin role).
Login to the machine using these accounts and see if you can run the
package from Enterprise Manager. This could give you some additional
information.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

Monday, March 26, 2012

Establishing VPN Connection thru DTS package

Hi,
I have defined a DTS package which establishes VPN connection with my
client's server. When I execute this package thru SQL Enterprise
Manager (SEM) it works fine, but when I schedule it as a job or try to
execute thru SQL Query Analyzer using 'xp_cmdShell' stored proc, it
doesn't establish connection. NE ideas on what am I doing wrong?
Yr prompt response will be highly appreciated.
Thanks,
Um Junk
When you execute it using xp_cmdshell the package is run under the context
of the SQL Server startup account (if the user connected via Query Analyzer
is a member of the sysadmin role) or the SQL Proxy account (if the user
connected via Query Analyzer is not a member of the sysadmin role).
Login to the machine using these accounts and see if you can run the
package from Enterprise Manager. This could give you some additional
information.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - 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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!
|||thanks for posting this! was having the same problems but now it worked in a few seconds!
|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.
|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - 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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!|||thanks for posting this! was having the same problems but now it worked in a few seconds!|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - 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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!
|||thanks for posting this! was having the same problems but now it worked in a few seconds!
|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.
|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

|||Scripting as new Table with insert data isn't supported in SQL Server. I found a C# program that does this; http://www.eggheadcafe.com/articles/20040913.asp

Just needed the server name. Worked beautifully.

Thank you Thank you.

Fred

sql

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - 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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!|||thanks for posting this! was having the same problems but now it worked in a few seconds!|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - 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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!
|||thanks for posting this! was having the same problems but now it worked in a few seconds!
|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.
|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Establishing connection from SQL MMC fails

Hi,
I have Win2003 and SQL server 2000 installed. I have restarted SQL services
and the services crashed and could not be killed. I have killed the
processes manually but when I open SQL Server Enterprise Manager, expand SQL
Server group and click on the desired SQL Server group it is failing and the
MMC becomes not responding.
It fails on 'Establing connection to SQL Server and checking Windows
security'
I have tried to telnet on the respective SQL Server port and the port
responds ok. I have also done a netstat and the server is listening on the
respective port.
From the sql error logs, the following information is being logged
2007-09-26 16:45:04.32 spid8 63 transactions rolled forward in database
'msdb' (4)
2007-09-26 16:45:34.04 spid5 Starting up database 'tempdb'
2007-09-26 16:50:33.06 spid8 Time out occurred while waiting for buffer
latch type 4,bp 0xf97e40, page 1:1508), stat 0x9, object ID 4:2073058421:0,
EC 0x42CAC3F0 : 0, waittime 3000. Continuing to wait.
2007-09-26 16:50:33.06 spid8 Waiting for type 0x4, current count
0x10000a, current owning EC 0x42CAC3F0.
Your suggetions will be highly appreciated.Dear Quintin,
Thank you for posting here.
From the problem description, I understand that the error message
"Establish connection to SQL Server and checking Windows security" is
encountered when trying to connect to the SQL Server 2000 via the
Enterprise Manage. If I have misunderstood about your concern, feel free to
let me know.
Before moving on, I suggest that you try the following method to check if
you could connect via osql.exe
1. Click Start, click Run, type cmd, and then click OK
2. At the command prompt, type the following command, and then press ENTER.
OSQL -E -S <server name>\<instance name>
OSQL -E -S tcp:<computer name>,<port number>
Also, you could try SQL authentication by using sa
OSQL -S <server name>\<instance name> -Usa -P<password>
3. Please check if we can successfully connect to the instance of SQL
Server 2000 by using osql.exe.
If any error message appears, please let me know the extract error message
we received.
Please also help me gather the following information for the further
research:
Information One: SQL MPS Report
=====================Please help create a MPSReport on the problematic machine, which will
collect ERRORLOG, Windows event log and other helpful information about the
SQL Server. To create a MPSReport, please visit the following web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en
And look for MPSRPT_SQL.EXE. Download it and run it on the machine. Dismiss
the prompted dialog boxes and the readme window (usually a Notepad) after
you read them. After the Command Prompt window closes itself, collect the
cab file the tool has generated and sent it to me.
Information Two: Screenshot
=====================Please also help me to capture a screenshot when the error message
"Establish connection to SQL Server and checking Windows security" appears.
1. When the error appears, please press the Print Screen key (PrtScn) on
your keyboard.
2. Click Start, click Run, type MSPAINT, and click OK.
3. In Paint, click Paste under the Edit Menu, click Save under the File
menu, type a file name for the snap shot, choose JPEG as "Save as type",
click "Desktop" on the left pane, and click Save.
Please send above files to me at v-adamqu@.microsoft.com
If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| From: "Quintin Zammit" <qztarantino@.newsgroup.nospam>
| Subject: Establishing connection from SQL MMC fails
| Date: Wed, 26 Sep 2007 19:27:40 +0200
| Lines: 30
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| Message-ID: <eNQDMKGAIHA.4880@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 80.85.100.38
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:26395
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hi,
|
| I have Win2003 and SQL server 2000 installed. I have restarted SQL
services
| and the services crashed and could not be killed. I have killed the
| processes manually but when I open SQL Server Enterprise Manager, expand
SQL
| Server group and click on the desired SQL Server group it is failing and
the
| MMC becomes not responding.
|
| It fails on 'Establing connection to SQL Server and checking Windows
| security'
|
| I have tried to telnet on the respective SQL Server port and the port
| responds ok. I have also done a netstat and the server is listening on
the
| respective port.
|
| From the sql error logs, the following information is being logged
|
| 2007-09-26 16:45:04.32 spid8 63 transactions rolled forward in
database
| 'msdb' (4)
| 2007-09-26 16:45:34.04 spid5 Starting up database 'tempdb'
| 2007-09-26 16:50:33.06 spid8 Time out occurred while waiting for
buffer
| latch type 4,bp 0xf97e40, page 1:1508), stat 0x9, object ID
4:2073058421:0,
| EC 0x42CAC3F0 : 0, waittime 3000. Continuing to wait.
| 2007-09-26 16:50:33.06 spid8 Waiting for type 0x4, current count
| 0x10000a, current owning EC 0x42CAC3F0.
|
| Your suggetions will be highly appreciated.
|
|
|
||||Dear Quintin,
I am just writing to see if you have had the opportunity to try the
troubleshooting steps or collect the requested information. If you have any
questions with the previous information I've provided, please don't
hesitate to let me know.
I appreciate your time and look forward to hearing from you.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 141089102
| References: <eNQDMKGAIHA.4880@.TK2MSFTNGP03.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Thu, 27 Sep 2007 09:48:43 GMT
| Subject: RE: Establishing connection from SQL MMC fails
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <TcGwYuOAIHA.5204@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 126
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:26437
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Quintin,
|
| Thank you for posting here.
|
| From the problem description, I understand that the error message
| "Establish connection to SQL Server and checking Windows security" is
| encountered when trying to connect to the SQL Server 2000 via the
| Enterprise Manage. If I have misunderstood about your concern, feel free
to
| let me know.
|
| Before moving on, I suggest that you try the following method to check if
| you could connect via osql.exe
|
| 1. Click Start, click Run, type cmd, and then click OK
| 2. At the command prompt, type the following command, and then press
ENTER.
|
|
| OSQL -E -S <server name>\<instance name>
| OSQL -E -S tcp:<computer name>,<port number>
|
| Also, you could try SQL authentication by using sa
|
| OSQL -S <server name>\<instance name> -Usa -P<password>
|
| 3. Please check if we can successfully connect to the instance of SQL
| Server 2000 by using osql.exe.
|
| If any error message appears, please let me know the extract error
message
| we received.
|
| Please also help me gather the following information for the further
| research:
|
| Information One: SQL MPS Report
| =====================| Please help create a MPSReport on the problematic machine, which will
| collect ERRORLOG, Windows event log and other helpful information about
the
| SQL Server. To create a MPSReport, please visit the following web site:
|
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
| 88B7-F9C79B7306C0&displaylang=en
|
| And look for MPSRPT_SQL.EXE. Download it and run it on the machine.
Dismiss
| the prompted dialog boxes and the readme window (usually a Notepad) after
| you read them. After the Command Prompt window closes itself, collect the
| cab file the tool has generated and sent it to me.
|
| Information Two: Screenshot
| =====================| Please also help me to capture a screenshot when the error message
| "Establish connection to SQL Server and checking Windows security"
appears.
|
| 1. When the error appears, please press the Print Screen key (PrtScn) on
| your keyboard.
| 2. Click Start, click Run, type MSPAINT, and click OK.
| 3. In Paint, click Paste under the Edit Menu, click Save under the File
| menu, type a file name for the snap shot, choose JPEG as "Save as type",
| click "Desktop" on the left pane, and click Save.
|
| Please send above files to me at v-adamqu@.microsoft.com
|
| If anything is unclear in my post, please don't hesitate to let me know
and
| I will be glad to help. Thank you for your efforts and time.
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu
| MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| =====================================================| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| =====================================================| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
| --
| | From: "Quintin Zammit" <qztarantino@.newsgroup.nospam>
| | Subject: Establishing connection from SQL MMC fails
| | Date: Wed, 26 Sep 2007 19:27:40 +0200
| | Lines: 30
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| | X-RFC2646: Format=Flowed; Original
| | Message-ID: <eNQDMKGAIHA.4880@.TK2MSFTNGP03.phx.gbl>
| | Newsgroups: microsoft.public.sqlserver.server
| | NNTP-Posting-Host: 80.85.100.38
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:26395
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Hi,
| |
| | I have Win2003 and SQL server 2000 installed. I have restarted SQL
| services
| | and the services crashed and could not be killed. I have killed the
| | processes manually but when I open SQL Server Enterprise Manager,
expand
| SQL
| | Server group and click on the desired SQL Server group it is failing
and
| the
| | MMC becomes not responding.
| |
| | It fails on 'Establing connection to SQL Server and checking Windows
| | security'
| |
| | I have tried to telnet on the respective SQL Server port and the port
| | responds ok. I have also done a netstat and the server is listening on
| the
| | respective port.
| |
| | From the sql error logs, the following information is being logged
| |
| | 2007-09-26 16:45:04.32 spid8 63 transactions rolled forward in
| database
| | 'msdb' (4)
| | 2007-09-26 16:45:34.04 spid5 Starting up database 'tempdb'
| | 2007-09-26 16:50:33.06 spid8 Time out occurred while waiting for
| buffer
| | latch type 4,bp 0xf97e40, page 1:1508), stat 0x9, object ID
| 4:2073058421:0,
| | EC 0x42CAC3F0 : 0, waittime 3000. Continuing to wait.
| | 2007-09-26 16:50:33.06 spid8 Waiting for type 0x4, current count
| | 0x10000a, current owning EC 0x42CAC3F0.
| |
| | Your suggetions will be highly appreciated.
| |
| |
| |
| |
|
|

Establishing a remote connection..! (Again)

Hi,

I am trying to connect via the Management Studio Express. I share a LAN with the server. In Netowrk connections I can see the server and I can even access the "Shared" folders. However,when I try to connect I get an error that says the error may be caused by the server not allowing remote connections. I have already done the following:

With the Surface Area Configuration facility I have set the server to allow remote connections I have selected TCP/IP as the preferred mode of connection. I have selected Windows authentification as mode of authorisation

What else can I do?

Please help.

Derekprinsloo

Verify that there is no local firewall blocking.

These resources should help you.

Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

Configuration -Connect to SQL Express and ‘Stay Connected’
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html

Establishing a remote connection..!

How can I establish a remote connection for using remote database in SQL Server 2K5?

Thanks.

Take a look at this link:

http://msdn2.microsoft.com/en-us/library(d=robot)/ms188721.aspx

Is this what you are looking for? If not, please provide additional information on the scenario you want to enable.

Thanks
Laurentiu

|||

my scenario :

my computer is into a LAN. I want to connect from my PC to a database on another computer in this LAN. I have username and password for logging in to the another computer in SQL Server Authentication mode.

please help me!

|||

How did you try to connect so far?

Normally, you would need to specify the server name, and the user name and password. But you should check that the server accepts remote connections and that you're not blocked by a firewall. Also check to see that the type of connection that you make is enabled on the server (if you use TCP, check that TCP is enabled).

Thanks
Laurentiu

sql