Connecting To SQL Server 2000 Via VB6 Program On Vista
Jul 18, 2007
I am having difficulty connecting to SQL Server 2000 on one of our
servers via a VB6 program on Vista. I can connect fine to a different
server, but it gives me the following error with the server in
question:
"Unable to connect to database. Please check your internet connection
Error# -2147467259
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied"
Using the program, I am able to access the database just fine while
running on Windows XP, but when I run the program on Vista, it gives
me that error message for that server. If I change the connection
string to a different server address, it works fine on Vista. What
differences in the servers might cause this?
Here is my connection string:
"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"
View 7 Replies
ADVERTISEMENT
Nov 26, 2006
hi there - I'm praying someone here can shed some light on this - after many google and web searches, I have found users with similar issues, but have yet to find a solution.
Problem: I have recently upgraded my desktop from Windows XP to Windows Vista Ultimate (clean install) and have migrated my local machine to SQL Server 2005. However I have a number of .Net projects that access databased on another server running SQL Server 2000 - prior to my upgrade to Vista, I was running SQL Server 2000 on my desktop as well. During the install, everything seemed to go well, and I also installed the SQL Server 2005 Service pack as instructed via the MSDN site. However, when attempting to test my .net projects on my desktop pc (ie visit http://localhost), I encounter the error:
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
note that the server I am attempting to connect TO is the old SQL 2000 server - NOT 2005. I specify my connection info in the web.config - and it points to an external ip address on the web.
Can anyone shed some light on this? I've tried enabling remote access on my local SQL 2005 install, but I'm fairly sure thats for servers that want to connect to my desktop, rather than my desktop attempting to connect to external servers. Any help is greatly appreciated - I'm pulling my hair out over trying to figure this out! :)
To summarize my setup (if it helps)
Desktop PC:Windows Vista (Ultimate)SQL Server 2005Visual Studio 2005II 7.0.Net 2.0 (ASP.Net Application)
External Server (co-located at a datacenter)Windows Server 2003SQL Server 2000IIS 6.0.Net 2.0 (ASP.Net Application)
Much appreciated,
Ted
View 5 Replies
View Related
Sep 25, 2007
Hi,
I've written a piece of database software in Visual Basic (Visual Studio 2005) to use in my office. My office has networked computers all connected to a server (windows server 2003). I have an old-ish version of SQL server on the server computer (version 7). The software works perfectly within the office environment - each computer on the network connects to the SQL server on the server computer and works very efficiently.
I now want to be able to access the database from home by running the software on my home PC. I want the software to somehow connect to SQL server in the office over the internet. Having read many of the threads about remote SQL server connections, I feel totally out of my depth. I vaguely understand that SQL server needs to be somehow configured to receive connections from the 'outside world'. I don't know how to do this. I also don't know what I need to do on the Windows server to allow this to work. I thought I might be able to use the computer's IP address in the connection string, but using IPconfig on the server I only get network IP addresses - the server may be behind a router... How do I get the proper internet address? Once I've set up the server side to work with remote connections, how do I get my software to communicate with that server? Do I just need to change the connection string and that's it? What would the format of the connection string be?
I'm very sorry for asking so many questions in one go! I have ended up a bit frustrated after reading many threads and articles about SQL remote connections - it's all rather advanced and don't understand most of it!
Thank you very much in advance for any help you can provide.
Sam
View 1 Replies
View Related
Dec 19, 2007
I have two computers each with SQL Server Developer edition on them. Each is set up identically with remote connections enabled. Once machine is running Vista Business the other is running XP Pro SP2. From the Vista machine I can connect to the instance on the XP machine but I cannot connect to the Vista instance through the XP machine. I keep getting the error that indicates SQL Server isn€™t set up for remote connections even though it is. There is obviously some access problem that is due to Vista but I have no idea what it might be.
Thanks for any help you might provide.
Dane R. Vinson
PS I wasn't totally sure of the correct forum to post this but it seems like it might be a setup issue.
View 3 Replies
View Related
Jul 13, 2007
Alright I glanced over the forums to see if there was an answer for this and I didn't see one. I saw a few similar issues however nothing that fixes my issue. Here is my problem.
I installed SQL Server 2005 Express on my Vista partition along with Visual C# Express. For some reason I cannot get the SQL Server 2005 Express to function correctly. Back when installed this on XP it worked flawlessly, and I don't even recall doing anything special...I installed it and it worked. I do know that you have to manually add the user account to the admin list for the SQL server on Vista, and I did that. I chose the option to have it do it during installation as well as through the SQL Server Surface Area Configuration just to be sure.
I am just trying to get the basics of it working right, and that is connecting to the server using C# and filling a dataset...it shouldn't be this hard. This morning when I started with this I could connect and fill my DataSet programmatically however it wouldn't pass the test through the Data Source Configuration Wizard. When I did it manually, as I said it worked and filled the DataSet with the info I asked for below in the code sample. After getting annoyed by it not working through the wizard I decided that maybe I had my permissions wrong and I may have messed up when installing it. So I uninstalled everything to do with SQL Server 2005 and reinstalled it fresh.
This time when I installed it I made sure to set it up to use Windows Authentication. Now it will pass the Test in the Data Source Configuration Wizard and everything is working by doing it that way. However now it doesn't work when I do it manually with the code below(same code as before when it worked...lol). When I use the code below it crashes with the error: "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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)". When I go through it with the debugger it throws that error at the call dataAdapter.Fill(...). The code is the following:
Code Snippet
string connStr = "server=localhost;Trusted_Connection=yes;database=northwind";
string commandStr = "Select CompanyName, ContactName from Customers";
SqlDataAdapter dataAdapter = new SqlDataAdapter(commandStr, connStr);
DataSet dataSet = new DataSet();
dataAdapter.Fill(dataSet, "Customers");
DataTable dataTable = dataSet.Tables[0];
foreach(DataRow dataRow in dataTable.Rows)
lbCustomers.Items.Add(dataRow["CompanyName"]+
" ("+dataRow["ContactName"]+")");
Why doesn't that work yet I can basically ask for the same information and it will work if I do it through the wizard? If it works 1 way I wouldn't think there could be any issues with the server being accessed remotely, right?
Thanks
Danny B
View 1 Replies
View Related
Jan 18, 2007
Hi all,
I am having problems with connecting to a SQL Express server running on server 2003. I can connect with the program concerned from a windows xp client without problems. I cannot however connect from a vista machine using the software. In the logs i see the client trying to logon, wich fails with Login failed for user: 'user'. [client: clientIP] severity 14 state 8. On the vista client i have tried everything from disabling the firewall, windows defender, running the app as admin etc. I can connect using sqlcmd or the management tools with the username the app is using. This is a SQL user, we are not using windows users to connect to the DB.I also ran a app like ethereal to see what is happening packet wise, i see the login failed packet on a windows client, from a XP client everything seems fine and it starts using RPC.
Any help appreciated,
FVader
View 1 Replies
View Related
Nov 4, 2005
Hi,My situation follows: I set up a database called TempDB and a test connection to it that works on my machine.In my database class I am trying to create a connection by doing the following:
connToLookUpData.ConnectionString = "Integrated Security=SSPI;Initial Catalog=dbTest;Data Source=testServer;"
but I am getting the following error: Login failed for user "Joe/ASPNET"i have windows XP OS.I based the connection string on the properties of my connection to Database 'Test'.Joe is the name of my computer. Both the application and SQL Server are now on my local machine.What am I doing wrong? any help greatly appreciated.Thanks much,Joe
View 2 Replies
View Related
Oct 8, 2007
Hi,
Just upgraded some development desktops to Vista Business. However we need
to still connect to some older remote windows 2000/SQL 2000 servers.
Trying to setup an ODBC system DSN on our Vista Business local desktop we get the
following errors -
-START ERROR WINDOW-
Connection Failed:
SQLState: '01000'
SQL Server Error: 772
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(SECDoClientHandshake()0.
Connection failed:
SQLState: '08001'
SQL Server Error: 18
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
-END ERROR WINDOW-
Any help greatly appreciated as this is stopping us from making
database/table connections etc. We've checked the firewall setup and all is well there.
PS - we can still connect fine using XP or windows 2000 desktops and their
local DSNs.
View 8 Replies
View Related
Feb 1, 2006
hi ALL !!!
How can I insert Date in SQL Server 2000 database(table ) from ASP.NET 1.1. Program??
pls send me code if u can
pls help me ..
View 2 Replies
View Related
Mar 13, 2007
A client just purchased a new notebook, pre-installed with Vista. He says he is having trouble installing SQL Server 2000 (database and client tools). I am not certain (yet) if this is the standard edition or the desktop version.
What, if any, are known compatibility issues between SQL 2000 and Vista?
View 5 Replies
View Related
Mar 11, 2008
Dear All,
My office computer just had Vista installed on it and I have now encountered a problem in SQL Server 2000 sp4. (Yes, I know it's old and has comparability issues with Vista, but I don't have the option to upgrade at this point.) I have two servers to register. One works fine, but the other won't register and returns the error "SQL Server does not exist or access denied. ConnectionOpen (Connect())". I was able to register this one server that isn't working while previously running XP on my office computer and even as a test on another server running Windows Server 2003. This leads me to believe the problem is isolated with my installation on Vista and not with any permissions, etc. I have been scouring different forums looking for a fix for this, but have come up empty handed. Does anyone have any suggestions on how to fix this problem?
Thank you!
View 14 Replies
View Related
Jan 17, 2008
Hey
Ive read on some pages that it is in fact possible to install and run SQL Server 2000 on Vista. In my university, SQL Server 2000 is still used to teach us about databases and how to administrate them. The computers run Windows 2000 Professional. I need to be able to use 2000 so I can not only have compatibility but also know the steps and all possible conditions and solutions to problems.
Would installing and running SQL Server 2000 on Vista be possible or am I better off using 2005? Is there much difference between these 2 versions?
View 11 Replies
View Related
May 21, 2008
I'm having issues talking to Vista Sql Express, but selectivly.
The following diagram shows you what works, and what doesn't :
http://www.craznar.com/junk/sqlissue.png
As you can see, the Vista/Express server is running - has all the required connectivity enabled, however we cannot talk from the Windows Server 2003 SQL to the Vista SQL.
The error that is given suggests issues with remote access enabling on Vista - but this is working alsoVista's firewall turned off (We can connect to it).
All machines are on the same subnet, behind the same firewall - Neptune and Headoffice are on a domain, Neptune points to Headoffice for DNS, Headoffice forwards DNS requests to the same DNS all other machines use.
File sharing and Ping work from Headoffice to Neptune ... just can't get SQL connection to work.
Any help appreciated.
Thanks
View 8 Replies
View Related
Mar 13, 2007
I am using two almost idential laptops, one with XP and one with Vista, the only differences is that the XP laptop has 1G of RAM and running Office XP and the Vista has 2G RAM and is running Office 2007.
I have a MS Access database that has linked tables to a SQL Server 2000 database. The performance of the Access database on Vista is 5-10 times slower on the Vista machine. Just flipping through records or opening forms can take 5 - 15 seconds on the Vista machine while the XP machine takes 1 sec or less.
What gives? I looked at the CPU performance and the network performance while the Access database was busy flipping through records, the network traffic was < 2% and the CPU would spike to 40% on one of the CPUs (dual core) but would remain under 5% most of the time.
I also previously had Office XP installed on the Vista machine and it had the same performance issue so bought and install Office 2007 on the Vista machine and it did not solve the problem.
It seems that Vista is doing something that is slowing down Access with linked tables. Is this a issue between Vista and using an ODBC connection to SQL Server?
Thanks in advance for any help on this
View 1 Replies
View Related
May 22, 2007
Hi there,
I have 2 servers on our compny'ssql server does not exist or access denied lan, one with fixed ip and the other one with internal ip. I installed SQL server 2000 on the one with internal ip and I want to access it from the other server. when I want to register sql server instanse , I can see the name of that instance in the list but I can't register it. I keep reciving this error : sql server does not exist or access denied!
Could any one told me what to do?
View 2 Replies
View Related
Dec 23, 2005
Hi
I am running Visual Studio 2005 Visual Web Developer Standard Edition on a machine with SQL Server 2000. Could you please teach me how to modify the connection string below so that it connects to SQL Server 2000 with the database called "VisualWebDev".
Thank you.
Jim
<connectionStrings>
<add name="Personal" connectionString="Data Source=.SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Personal.mdf" providerName="System.Data.SqlClient"/>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="Data Source=.SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf"/>
</connectionStrings>
View 12 Replies
View Related
Jul 23, 2005
Hi,I am total newbie to SQL Server. My new host tells me I can connect throughAccessXP or 2002. I have Access 2000. Can I not connect with that also?Thanks, JA
View 4 Replies
View Related
May 15, 2007
I have sql server 2005 (full version) installed on my local machine, while the databases (on the server) I want to program against are in sql 2000. Could I program against sql 2000 databases using sql 2005? If yes, what do I need to know before I start doing that? Any suggestions are welcome.
View 1 Replies
View Related
Jun 4, 2007
Hello,
We have a web based program that is using SQL 2000 as the db. Sql 2000 is running on a Windows 2003 server.
Is it possible to extract the SQL 2000 program(web based) with a clean db onto a blanket CD so another person can install it?
Any help would greatly be appreciated.
Mike
View 1 Replies
View Related
Jan 31, 2007
I am developing a system using VS 2003 with database SQL Server 2000.
In web.config, I have added the following code in it
<sessionState
mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1;Database=grandb;Trusted_Connection=yes"
cookieless="false"
timeout="60"
/>
Actually I don't know if the above code is correct. My database is stored in the SQL Server 2000 and named as grandb.
Thank you.
View 3 Replies
View Related
Jul 24, 2007
Hi,
My problem is somewhat like this that, i want to connect my all applications (developed in asp.net) to one database. In other words i want to make a centralised database that can be accessible from the application running at the different domains. When i did so by using the same username, password, database and server...i recieve an error that, "connection cannot be establised".
If any body have the solution for this problem. then please do write the "connection string" for me that can be efficiantly used on the applications running on differnt domains.
Thanks and Regards,
Steve Dcosta
View 1 Replies
View Related
Jul 24, 2007
Hello All,
I am just getting started on aspx, coming from an asp background.
I created the following connectionString in my web.config file:<connectionStrings>
<add name="OuWebDB"
connectionString="server=OurServer;database=OurDatabase;uid=TheUser;pwd=ThePassword"providerName="System.Data.SqlClient"
/>
</connectionStrings>
when I run this aspx file, from a machine, I get the following error:
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Help!!
thanks
View 3 Replies
View Related
Jan 14, 2004
I've just installed SQL Server 2000 on my local machine. I'm using the following element in my web.config file for my connection string.
<add key="SqlNWind512" value="server=(local)141.705.84.745;database=Northwind;
user id=sa;pwd=h3fe8eq7;packet size=512;" />
Unfortunately, I'm getting the following error on my aspx page:
SQL Server does not exist or access denied.
I had no problem writing a connection string to connect to the MSDE installed on my computer, but making a connection to the Northwind database on my newly installed SQL Server 2000 Developer edition has been elusive to me.
I'm sure my IP address is correct. The authentication mode for logging into the database via Enterprise Manager is setup to require a password for sa. Therefore, I assume it's required in the connection string???
Maybe not so coincidentally, while I have been able to open this database through the Server Explorer in VS.NET, I'm not able to access it via Enterprise Mananger (no response, it just hangs) or my aspx pages.
I'm dying here!!! Is my connection string wrong? Any insights would be greatly appreciated!
View 3 Replies
View Related
Feb 24, 2003
I've installed Sybase client 12.0 and have created the DSN (it is successful, connection is established)
but when I run this ActiveX Script from DTS Package it give me error Data Source Name not found and no default driver specified
Dim RS
Dim oConn
Set oConn = CreateObject("ADODB.Connection")
msgbox "set oConn"
Set RS = CreateObject("ADODB.Recordset")
msgbox "RS"
(I've tried both open statement in both it gives me same error)
oConn.Open = "Driver={Sybase ASE ODBC Drivers};Srvr=Server1;Uid=sa;Pwd=password"
oConn.Open="DSN=Test;Uid=sa;Pwd=password"
msgbox "open"
Can anyone guide me?
Thanks in advance
-Sejal
View 2 Replies
View Related
Mar 15, 2004
We have installed SQL Server 2000 in our new server running on Microsoft Windows Server 2003.
We tried to connect to the database in the Server where it is installed. We are able to connect when we give server name. We are unable to connect when we give IP Address of the server.
We have latest SP3a of SQL Server 2000 installed.
Could anyone help us in resolving this issue?
Thanks in Advance.
View 1 Replies
View Related
Jul 23, 2005
Hi Folks,I'm very new to SQL Server. I have a home network. My primary connectionto the internet is using "Gateway 1" a linksys router, of which, my serveris a LAN node on that router. I have another LAN node connecting to the WANnode of the "Gateway 2" a wireless USR router to use with my laptop. Usingthe wireless laptop, I am on a different subnet than the Server. I'd liketo make a connection to the server through Visual Studio.net but I can'tseem to do it. I'm using TCP/IP with a port different than the default port(let's call it port 2110, even though it's not). I do have port forwardingon Gateway1 and I've tried everything from just the server internal IPaddress, the external IP address, IP address with port designation, URL withport designation, nothing seems to work. Any ideas?Thanks!Rick
View 1 Replies
View Related
Jul 23, 2005
I have an Access 97 database that I connect to a SQL Server 2000through ODBC. I have to manually set up the ODBC connection on eachuser's machine if I want them to be able to use the application though.Is there a way to store the connection string within the Access DB soI don't have to touch the ODBC settings on each user's machine? Or isthere a different solution that I'm missing? There are way too manyfor me tosetup. Thanks in advance.
View 1 Replies
View Related
Apr 24, 2007
Please help to connect SQL server 2000 on different domain.
Please correct if I m wrong.
System details as follows
Client
Domain : DomainA
System : System1
IP Address : 10.10.225.19
SQL server 2000 installed
SQL Server
Domain : DomainB
System : System2
IP Address : 10.108.22.19
SQl Server : System2inst2 ( My database is under inst2 instance)
SQL login : TestUser1
Password : Users123
I have Opened firewall port to access 10.108.22.19 from 10.10.225.19
While connecting the SQL server €śSystem2inst2€? from the client machine enterprise manager with the SQL authentication, I am getting error Login failed for user €śTestUser1€?
And I have noticed in the SQL server log the login attempt shows under System2 default instance ( no instance). Actually I want to connect system2inst2.
Please let me know the steps to connect.
Thanks in advance.
View 3 Replies
View Related
Mar 11, 2007
I get the following error message in quotes. I have a web application written in ASP.NET 2.0 through which I am trying to connect to a remote SQL Server 2000. My operating system is Windows Vista .
I looked at many different sites to find a solution for this but without any luck. I am sure someone would have seen this issue here and I expect them to shed some light.
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).
The connection string is located in my web.config file which looks like
<add name="AMSConn" connectionString="Data Source=xxxx;Initial Catalog=testdb;User ID=sa;Password=xxxx" providerName="System.Data.SqlClient" />
I want to get this issue resolved and I need you guys help.
Please let me know if you need any more information.
Thanks
Bharat
View 3 Replies
View Related
Jun 8, 2007
I'm new to using VS2005 and this is my first project connecting to our MS SQL 2000. App worked fine on my dev PC, connection to the same MS SQL Server. Published the web site to the web server (same server running MS SQL Server) and getting the below error. Is this a permission setup problem on SQL Server or does it really think it's connecting with a MS SQL 2005 database?
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
View 16 Replies
View Related
Jul 11, 2007
My environment is Windows Server2003, ASP.NET 2.0, SQL Server 2000 using SQL authentication (names of DB's, sql id's, passwords are identical on both servers)
My web application successfully connects to my database the web app and the DB are both on the same server (10.144.25.9).This connection string works:
<add name="DefaultDataTierConnectionA" connectionString="Data Source=10.144.25.9,1433; Network Library=DBMSSOCN; Initial Catalog=9D_SQL; User ID=******; Password=******" providerName="System.Data.SqlClient"/>
PROBLEM:
The problem occurs when the DB is mpved to the remote SQL Server (10.144.25.10). I use almost the identical connection string except for the IP address which is changed to the remote machine. The db name, user, password is same on remote machine as on the local, so everything should work but does'nt. This connection string fails:
<add name="DefaultDataTierConnectionA" connectionString="Data Source=10.144.25.10,1433; Network Library=DBMSSOCN; Initial Catalog=9D_SQL; User ID=******; Password=******" providerName="System.Data.SqlClient"/>
error (odd error in that I'm connecting to SQL 2000?) -
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 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: 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 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
There is no DBA on this project, I'm not sure this is a SQL Server set up problem?
View 1 Replies
View Related
Dec 20, 2007
I'm experiencing a problem connecting to a SQL 2000 server through my ASP code. My connection string is as follows:
<add name="TheConnectionString" connectionString="driver={Sql Server};provider=MSDASQL;server=10.0.1.42;database=dbname;uid=*********;pwd=*********" providerName="System.Data.Odbc" />
The problem doesn't occur when I run my ASP code from my workstation using VS.NET's builtin webserver. It makes the connections and executes the CRUD commands successfully. However, when I publish my site to the webserver (which resides on 10.0.1.16) it fails out with the following error:
System.Data.Odbc.OdbcException: ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.ERROR [01000] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
I've verified that the webserver can talk to the DB server by connecting to the remote DB server through SQL Enterprise Manager running locally on the webserver. If I try to do this with a DSN I get the same results. I get the same error from any other webserver on the internal network. The difference between my workstation and the internal network is that I'm using a VPN to connect to our internal network while the webservers are physically connected to it. Firewalling isn't the issue in this case because the webservers and DB server are on a trusted network. I've seen other ways of connecting to the DB server including using Named Pipes (which I would rather not do because I don't want to setup a named pipe on the production db server).
I'm relatively new to ASP.NET 2.0, so the above connection string is an adaptation of some old ASP code. If anybody has any suggestions on a better way to construct this connection string, please let me know. I've been racking my brains trying to get this to work outside of the devel env.
View 4 Replies
View Related
Aug 29, 2006
I have the following problem;
I fully understand that to connect to a named instance of SQL Server you need to use the ServerNameSQLInstanceName. The problem I have is that I have a SQL Server in a different zone. I can connect to the Default instance by IP Address or the ServerName.zone.domain.org. (e.g. MySQLServer.zone1.mydomain.org).
However, the same thing does not work for the Named Instance. It seems to be named instance or nothing.
How can I connect to this named instance across network zones?:S
View 2 Replies
View Related
