Home/ Questions/Q 871047
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T10:34:48+00:00

First off, I can connect to both databases with SQL Server Enterprise Manager, so

  • 0

First off, I can connect to both databases with SQL Server Enterprise Manager, so I know the servers are up and available. One of them is SQL1, the other is SQLTEST.

In my program when I use the following connection string, it work connects just fine:

conn = New DBConnect("Data Source=SQL1;Initial Catalog=SignInspection;Integrated Security=SSPI")

However, if I change SQL1 to SQLTEST the connection times out I don’t get any errors other than the timeout error.

I can run the profiler on SQLTest and see that it is most definitely NOT even attempting to connect. Nothing happens at all, not a peep, nor hellow.

Any ideas? Thanks

EDIT:

Well, it’s a moot point now because I got authentication working properly on our SQL1 server.

I’ll post the configuration here so perhaps someone else can benefit.

First off, the web server is running IIS and .NET. Users are logged in to the intranet using Active Directory, and the .NET page needs to retrieve their log-in credentials (username most notably). The database is SQL Server 2005, running on a different machine. But the .NET app needs to impersonate as another user to connect to the database.

To successfully do both of these things go to Windows > Run, enter inetmgr and hit run. Navigate to the site and right click > properties, then click on the tab titled Directory Security, click Edit.., make sure only Integrated Windows Authentication and Digest authentication are enabled. Enter your proper AD realm and click OK. Apply the settings/hit OK.

In web.config you need the following lines

<authentication mode="Windows" />
<identity impersonate="true" username="myDomain\MyUserName" password="123mypasswordgoeshere">

replacing, of course, myDomain\MyUserName and 123mypasswordgoeshere with the username and password that has login rights on both your domain and your sql server. The connection string can probably be modified, but this is mine and it works:

Server=SQL1;Database=SignInspection;Trusted_connection=True;

These are the steps that worked for me and hopefully they’ll be of use to someone else.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When you connected with the enterprise manager, was that from the same machine as you’re running the VB.Net code on?

    Otherwise, it can be quite a few things, ranging from firewall or DNS as mdma mentions to being setup with the wrong network protocol or maybe not accepting remote connections.

    This article contains a list of things to look at (it’s for SQL 2000 but it’s something to get you started at least).

    • 0