[AccessD] Across across the internet

Maybe I'm missing the point, but why would you *ever* expose the db on the internet?  

Charlotte Foust

Sent from my Samsung Captivate(tm) on AT&T

Stuart McLachlan <stuart at lexacorp.com.pg> wrote:

>If not using a VPN, at least change the default port from 1433.   Using the default port makes 
>sense over a LAN, but makes it that much easier for miscreants if you expose it to the 
>internet.
>
>-- 
>Stuart
>
> On 8 Jan 2011 at 12:03, Eric Barro wrote:
>
>> SQL server listens in on port 1433. If you open that port on your
>> firewall you should be able to see your SQL server db over the
>> internet. However it's not advisable and is not generally good
>> business practice to do so. The best way is to VPN into your network
>> and then access SQL server that way. You will still need to configure
>> SQL server to listen in for inbound connections on port 1433.
>> 
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
>> Sent: Saturday, January 08, 2011 11:35 AM To: Access Developers
>> discussion and problem solving Subject: Re: [AccessD] Across across
>> the internet
>> 
>> Next question, how do you expose a SQL Server to the internet.  If I
>> were to set up a MV that runs a SQL Server instance, how would I allow
>> it to be seen through my firewall?  I assume I would use SQL Server
>> authentication with users / groups in order to control access.
>> 
>> I have a dynamic IP and used to use an application that essentially
>> provided a fixed IP by tracking the changes if any in my dynamic IP. 
>> Would I use that and port forwarding?
>> 
>> Or could I use Hamachi and create a VPN in to the VM, then "see" the
>> sql server over that vpn?
>> 
>> This is all new to me.
>> 
>> John W. Colby
>> www.ColbyConsulting.com
>> 
>> On 1/8/2011 12:45 PM, Gustav Brock wrote:
>> > Hi John
>> >
>> > Yes, often, at zero errors.
>> >
>> > /gustav
>> >
>> >>>> jwcolby at colbyconsulting.com 08-01-2011 18:28>>>
>> > I know that the common wisdom is that Access Fe talking to an Access
>> > MDB
>> across the internet is a
>> > bad idea.  But what about talking to a SQL Server BE across the
>> > internet?
>> The issue with the MDB is
>> > corruption.  SQL Server doesn't corrupt, at least in the same
>> > fashion.
>> >
>> > Has anyone tried this?
>> >
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>> 
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>> 
>
>
>-- 
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com