Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 256
  • Last Modified:

MsSQL Server outside a Firewall. What ports? How to setup?

I'm having problems and I don't want someone to tell me to follow the steps on Microsoft's Support info from:
Q269882
Q238949

I've tried them.
I have a SQL server outside the firewall, it's using it's default 1433 port. There's a port open on the firewall in/out for 1433 and listening on 1024 to 65535.

I use the Connection String in my ASP Page like the example. "Provider=SQLOLEDB;Password=password;Persist Security Info=True;User ID=username;Initial Catalog=DBNAME;Data Source=servername;Network Library=dbmssocn"

I'm using the IP Address for the Servername.
When ever I try Conn.Open line in my ASP I get 'Connection Not Open' error.  So I can't figure out if it's something I have to do on the SQL or what other ports I need to open up on the firewall.

Any ideas how I can get this working?
0
Helpdesk
Asked:
Helpdesk
  • 2
1 Solution
 
gmoriakCommented:
I would suggest to set up an ODBC setting on that machine just to get to the point where you can hit test connection.  If this doesn't work, it is likely to get you more info as to why.  If it does work, the problem isn't getting through the firewall.
0
 
sanjaykpCommented:
1. Check your SQL Server's client network utility and ensure that it is actually listening on TCP/IP and not named pipes. Although within an intranet, pipes work just fine, through your firewall presumably, only IP packets are allowed through.

2. I'd also drop the 'Network Library=dbmssocn' bit from the connection string, since you are actually indicating to the provider that that is the network library it should use.

Cheers
0
 
sanjaykpCommented:
To answer the last part of you question, what you are doing is just fine. Actually you can ask your network bods to close every port except 1433 (other than those being used for other applications). This should also be the port indicated in the TCP/IP setup in the netowrk client utility.

0
 
HelpdeskAuthor Commented:
Well this ended up working. I setup a DSN connection on the webserver, it's not a normal IIS server, it's actually a Linux server running ChilliSoft which supports ASP, so within the Chillisoft configuration we added the DSN connection and I can connect that way, I perferd to use DSN-less but I'm still working on that. At least it works now thanks.  

The ports ended up working correctly after all.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now