I used VPN for years when I was with MS. It was okay, but there were issues
on occasion with administration, but I expect those issues to be resolved
now. Peter Blackburn (my co-author) recommends VPNs for some of his
customers and he's smarter than I in this area...
--
William (Bill) Vaughn, Author, Trainer, Mentor
Microsoft Pacwest Regional Director, MVP
"ADO and ADO.NET Examples and Best Practices for VB Programmers--2nd
Edition" (ISBN: 1-893115-68-2)
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
________________________________
> Our final solution is to use ADO with VPN over the
> internet. Our decision based on the facts:
> - not many database hits in our applications
> - reduce software complexity
> - finite number of branch offices
> - data security provided
> Comments ?
> >-----Original Message-----
> >I expect you can do this, but I might tend to create a
> middle-tier approach
> >that used ASPX to achieve it. Depending on a connection
> over TCP/IP can
> >work, but it's likely to cause some problems later. The
> ASPX approach or
> >using a WebService accessed from a Windows Forms
> application would permit
> >the data access operations to take place on the central
> server. This way you
> >would not have to transmit large bodies of data across
> the wire (if designed
> >correctly). I would also investigate .NET Remoting as
> well.
> >As I disuses in my book, using individual user IDs and
> passwords is also not
> >a particularly good idea for a litany of reasons.
> >Discussion?
> >--
> >William (Bill) Vaughn, Author, Trainer, Mentor
> >Microsoft Pacwest Regional Director, MVP
> >"ADO and ADO.NET Examples and Best Practices for VB
> Programmers--2nd
> >Edition" (ISBN: 1-893115-68-2)
> >www.betav.com
> >Please reply only to the newsgroup so that others can
> benefit.
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >________________________________
> >> Hi,
> >> I have a scenario that multiple geographically
> distributed
> >> branch offices ( over 20 ) would like to perform
> database
> >> access (R/W/U) in the main office.
> >> I understand that ADO.NET allows me to do connection to
> a
> >> remote server via IP address with encrytion turned on (
> >> please see attached ). I would like to find out any
> >> potential pitfalls I may be facing down the stretch.
> >> Questions like connection resources, performance
> issues ...
> >> Is there any more optimal solution for the above
> >> scenario ??
> >> Eric
> >> ================ attachment =================
> >> If connection to a remote server (via IP address):
> >> oSQLConn.ConnectionString = "Network Library=DBMSSOCN;"
> & _
> >> "Data
> >> Source=xxx.xxx.xxx.xxx,1433;" & _
> >> "Initial
> >> Catalog=mySQLServerDBName;" & _
> >> "User ID=myUsername;" & _
> >> "Password=myPassword"
> >> Where:
> >> - "Network Library=DBMSSOCN" tells SqlConnection to use
> >> TCP/IP Q238949
> >> - xxx.xxx.xxx.xxx is an IP address.
> >> - 1433 is the default port number for SQL Server.
> Q269882
> >> and Q287932
> >> - You can also add "Encrypt=yes" for encryption
> >> For more information, see: System.Data.SQL Namespace,
> >> Q308656, and .NET Data Providers
> >> Note: Microsoft SQLXML Managed Classes exposes the
> >> functionality of SQLXML inside the Microsoft .NET
> >> Framework.
> >.
by