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 |
|
mrgr8avill
Starting Member
16 Posts |
 Posted - 2009-08-21 : 05:25:29
|
| Hi, and thanks for taking the time to read this. I have just started distributing applications in order to save some of the processing resources on the server. Things worked fine on my test machine by using:Provider=SQLOLEDB;Network Library=DBMSSOCN;Data Source=xxx.xxx.xxx,1433;Initial Catalog=mycat;User ID=sa;Password=myPasswordBut lo and behold -- when I started testing on other remote clients I found that firewalls block port 1433 by default. Windows firewall will recognize the traffic and throw a block/allow but anyone using a hardware router/firewall would have to manually open ports for the connection to work.I have tried to google, but I am such a nooB at remote connections (and an almost blathering idiot at ports) that I have no clue and figured I'd ask here for help. So here's my question:When dealing with distributed apps that will need to access my instance of sql server from behind different firewalls of different types, what is the best method to insure the highest rate of connectivity?Thanks again for reading this, and in advance for any help or information you can provide! |
|
|
cat_jesus
Aged Yak Warrior
547 Posts |
Posted - 2009-08-21 : 10:56:56
|
| I wouldn't use sa over the internet. That's just asking for trouble.You're going to have to open a port one way or the other unless the client is behind the firewall with the database. Have you looked into VPN?Also, I think this is the wrong forum.An infinite universe is the ultimate cartesian product. |
 |
|
|
mrgr8avill
Starting Member
16 Posts |
Posted - 2009-08-21 : 19:19:18
|
| Thanks for the reply and info, and apologies for OT post (mods -- move or kill?)Not much data or many connections to worry about, so I can just put a port listener on the server and stream what I need by http. I hadn't thought much about security since this is a semi "back office" app not readily visible to the masses, but now that you mention it, it is a good thing to keep away from. The port listener app between the WAN and the SQL instance looks like a much better idea.Thanks again for your help and information. Sometimes staring at something for 20 hours straight can get you a little fixated on the left path when the right path is easier and staring you in the face! |
|
|
|
|
|
|
Conn string/port; remote access/Port 1433 blocked?