Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
robbieleo
Starting Member
3 Posts |
 Posted - 2011-06-24 : 15:59:22
|
| Hello allI am in the process of moving a classic ASP application from win server 2003 / IIS6 / SQL 2000 to Winserver 2008 / IIS7 / SQL 2005 Express and have not been able to get remote connections to work.Local connections are OK.I have followed the instructions here:http://support.microsoft.com/kb/914277I have verified that port 1433 is open using canyouseeme.orgI don't know which other ports to check (eg for the sql server browser service ?)I have tried connecting remotely using1. ODBC client 2. SQL Server 2000 Query Analyzer3. ASP application which works with existing SQL Server 2000 DB and a copy of the same code also works locally on the machine in question. The connection string is:Provider=SQLOLEDB; Data Source=aaa.bbb.ccc\SQLEXPRESS;UID=abc; PWD=def; Initial Catalog=dbname;"[note, on the local machine the only change to the code is that the ip address is replaced by "localhost" and this works fine. The error generated is:Microsoft OLE DB Provider for SQL Server error '80004005'[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied./LM/W3SVC/1/Root/blah/blah.asa, line 32The only other thing i have wondered about is that the server is currently not licensed /activated - we are changing ISPs to a cloud service where the provider has given us a trial account which will be licensed/activated once we "go live" with them. Could this be the problem with remote connections ?Any other suggestions/ideas/comments ?Thanks in advanceRL |
|
|
robbieleo
Starting Member
3 Posts |
Posted - 2011-06-26 : 04:44:35
|
| This problem is resolved now, by adding ,1433 to the connection string/server name |
 |
|
|
|
|
|
Remote connections problem