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 |
|
rb112978
Starting Member
11 Posts |
 Posted - 2005-06-18 : 05:33:02
|
We are about to have our server (Win XP SP1 with SQL Server 2000 Personal Ed.) connect to INTERNET via DSL by having 2 IP address (1 Static IP for Internet, 1 for LAN).Question: Can I map an ODBC DSN from a remote area (via Dial-up Internet) to our server using Static IP as server name? Still have 45 days and counting. Getting anxious and about to be worried. Proud to be Pinoy |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-06-18 : 08:01:38
|
| Yes, you can have an ODBC DSN connect via IP address. Naturally you have to be sure your SQL Server is running the TCP/IP network library (it does by default).What you SHOULD be worried about is getting hacked. Make sure you have a good firewall and it is enabled...and no, Windows firewall is NOT adequate. You should also set up SQL Server to listen on a different port besides the default port 1433. Many worms are still out there that look for that port. If you do change the port, you need to include it at the end of the IP address:123.45.67.89:1499 --SQL Server is listening on port 1499IMHO, it's NEVER a good idea to make your SQL Server visible to the internet. Another worry is that you're using Windows XP, and without Service Pack 2. That setup is exactly the kind that attracts hackers and hijackers the most. I've seen more than one article posted by reputable tech web sites who tested configurations like that, and the machines got hijacked in under 5 minutes when first connected to the internet. |
 |
|
|
rb112978
Starting Member
11 Posts |
Posted - 2005-06-19 : 21:11:16
|
| Thank you very much for the information, I will be using Zone Alarm Pro Firewall and definitely I will change the SQL port. Point well takenProud to be Pinoy |
|
|
|
|
|
|
Another ODBC DSN Question