[AccessD] Across across the internet

Why not use DynDNS or no-IP in connection with teamviewer installed as a
service. This is like having a static IP with 24/7 secure connection.

Helmut

-----Ursprungliche Nachricht-----
Von: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]Im Auftrag von jwcolby
Gesendet: Samstag, 8. Januar 2011 20:35
An: Access Developers discussion and problem solving
Betreff: 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