Re: Port 1433 access

Cheryl, a lot depends on the front end application as to whether or not you
can use some form of encryption / authentication.

If the front end application is Web based, then you should be able to use
SSL.

If not, your next best option is to use a VPN and access the SQL server
through the tunnel. However, if you are experiencing slow performance
through RWW, where the client and SQL server are local to one another, then
you're not going to be impressed with any solution that puts the front end
across a WAN.

You might want to test and see if running RDP across a VPN is any faster
than using RWW.

I think you sould consider investigating *why* RWW is slow, as this is the
best option. How does the application perform when you are on site? RWW
should deliver similar performance. If not, you may have slow internet
service, or a high latency connection with a high hop count. Can you get
Internet service from the same provider as the office?
You may have a slow workstation that you are using for remote desktop.
Consider building a terminal server, they do remote desktop better and
faster than an XP box.

Some well thought out indexes can greatly ehnance any SQL based app. How
large is the database? How many users are accessing it? What is the disk
configuration of your SBS box? SQL apps are disk-intensive. Maybe you
might need to move the application onto it's own server.

Printing across RDP works quite nicely, and you should be able to access an
Outlook client on the remote box for e-mailing stuff. Terminal services /
RDP is your best choice

There are probably other, more stealthy, methods of accessing SQL that I
have not looked into. For example, if you are running ISA 2004, then you
could create a publishing rule to open up 1433 and limit the scope to only
your remote IP address. This will not satisfy your need to have remote
access to various files, though.

You may want to post in an ISA or SQL focused group to see what other
options you might have.

I hope I've given you a few things to think about.

Buddy G ~

"CherylDetrick" <CherylDetrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1E79227C-C627-4D73-A816-23B7DF37573A@xxxxxxxxxxxxxxxx
I know leaving ports open is dangerous. However, I need access to a
database
that when I use RWW is just TOOO slow and I have too many issues with it.
Also, I need to be able to print reports and access the files for
emailing.
Again.. I know it is dangerous, I'm looking for a way to minimize that
danger
as much as possible.

Using SBS 2003 r2 and SQL server 2005, can someone give me a procedure to:

1) Open port 1433 for access to my DB remotely
2) How to create a secure logon and password protected entry for that
A number of our users login to Outlook 2003 using RPC over HTTP and
those connections are login and password protected --- I"m looking for
something similar.

Thanks,

Cheryl


.

Relevant Pages