connecting to SQL DB through a firewall

Hi there!

I'm a bit new to all this, so please bear with me! :)

I've got a webserver in our DMZ and I'm trying to create an ODBC connection from that server to a db server within our firewall. When I try and connect, the following message appears:

Connection failed:
SQLState: '01000'
SQL Server Error: 10060
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()),
Connection failed:
SQL State: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied

I'm at a bit of a loss as to what's going on, as we have an application on the webserver that connects to another SQL DB server within our firewall with no problem!

webserver:
OS - win2000 standard server sp4

db server:
OS - WinNT 4.0
SQL - 7.0

If anyone can help, it would be much appreciated!!

Cheers,

Ewan :)I'd recommend (so does MS) to have a VPN tunnel for intrasver communications, especially if they are on opposite sides of the firewall.

Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy

Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy

Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy

Connecting to a sql server from home.

Here is the problem, i'm sure there is quite a bit on google but i'mnot sure what to search for. I want to know how to connect to asql server from my home machine using the localhost for testing asp.netfiles out. At work the machines will connect fine usinglocalhost. The server we connect to is in another location. If someone could get me started on what to search for i wouldappreciate it.
Do you want to connect to the same SQL Server (which is at work), using 'Localhost'?
If so - you can't - localhost is used only for a Server which resides locally - on the computer where your web pages are residing.
(I'm not sure how you say it's using Localhost but, at the same time, you say it's in another location)
The SQL Server at work would become, by default, a 'remote' host - to do that, you'd need to use the IP address or the like, enter the username and password for it, and login that way - of course if it's using Windows Authentication, you'd need to work something else out...
Now - if you wanted to just work on pages, testing, etc...you could install SQL Server on your own computer and use localhost - but you'd need to have an identical database (you could do several things, like DTS, if the work computer is accessible outside the walls, along with other things)
|||Ok thanks for the reply.
This was what was throwing me off the computer i use at work doesn'thave sql server on it. The sql Server resides in Chicago and weare in TN. But when testing and using the local host it willconnect to the sql server fine. When i try the same thing at homei can not connect. I'll look more into remote hosting.
|||Is it possible your host has a firewall set up to only allow incoming connections from certain IP addresses (your work), and you need to ask someone to add your home IP address to those that are trusted by the firewall?

Connecting 32bit ASP to 64 bit SQL Server 2005

issue:

i have an ASP-Application running fine with both SQL Server 2000 and SQL 2005 (both 32 bit)

Now i have to attach a 64bit SQL-Server.

I have a problem with the connection:

This one runs fine with sql 2005 32bit

<%set myConn = Server.CreateObject("ADODB.Connection")

myConn.open "driver={SQL Native Client};server=<servername>;database=<dbname>;uid=<uid>;pwd=<pwd>" %>

but not with the 64-bit server:

ADODB.COnnection error "800a0ea9". Provider is not specified and there is no standard provider.

ok, i did some research and came up with the following:

<%set myConn = Server.CreateObject("ADODB.Connection")

myConn.open "PROVIDER=SQLOLEDB;DATA SOURCE=<serverip>,<serverport>;database=<dbname>;uid=<uid>;pwd=<pwd>" %>

thats fine, now i get a connect.

Unfortunately, this provider seems to behave different to the one i use in 32bit :

Lets say i have a stored procedure"

create spName as

select * from mytable

when i execute the following

<%sqlstr = "exec spname"

set myRecSet = CreateObject("ADODB.Recordset")

myRecSet.open SQLStr, myConn

response.write(myRecSet(0)) %>

it gives the first value of the first row with the Connection to a 32bit SQL-Server

but myRecSet seems to be empty on my 64bit SQL Server the response.write leads to an error message.

As far as i understand this, the provider used when connecting to a 32bit Server returns the records selected by the last row of the stored procedure into the recordset, but the provider when connecting to a 64bit server does not return these results.

What can i do, if i dont want to rewrite my asp-programming. I hope somebody has the correct naming / syntax for an connection string which allows me to connect my asp-application to the 64bit SQLServer which behaves like the "old" one for 32bit.

I hope my comments are clear enough - english is obviously not my mother-tongue - and somebody can give me a hint.

Thanks,

Heinrich

What is the error message?