data access strategy



I've developed an app for our company using VB.NET (winforms) and SQL server express running on our SBS server 2003 Standard

The app works really well within our LAN but I often work remotely and quite often would benefit from using my custom app. I've tried the VPN but for some reason my app just won't connect to the database.

What I'd like is some advice about how I can allow remote clients to access a SQL database that lives inside our LAN. I've never done any work with web services but I thought I might be able to do something there. Or maybe it's a simple matter of a firewall port and a clever connection string (trying and failing), plus not sure thats a good idea. I also have external windows hosting and the ability to host the database on a remote site. Although I'm nervous of doing that I would be happy if it was possible to mirror my database onto the ISP's server so my remote clients can connect to that instance. Assuming of course that mirroring works both ways.

I've tried all manner of connection strings to connect remotely. I believe I have opened port 8082 on my firewall (it's managed so I can't see it with my own eyes) and pointing it to my SQL server machine.

I was using the SQL instance with windows authentication only but just changed it to test in mixed mode as well.

My SQL instance is set to listen on port 8082 (using IPALL in the TCP/IP Properties dialog)

Some of the connection strings I've tried:
Data Source=<<ext IP>>,8082;Network Library=DBMSSOCN;Initial Catalog=eproject;User ID=sa;Password=<<password>>"
Data Source=<<ext IP>>,8082\sqlexpress;Network Library=DBMSSOCN;Initial Catalog=eproject;User ID=sa;Password=<<password>>"
Data Source=<<ext IP>>,8082;Initial Catalog=eproject;Integrated Security=True"

and various other combinations. All of these connection strings work from clients within my LAN so it must be to do with my firewall or the SQL server instance itself.

I don't really know anything about database mirroring, or even if it's possible with SQL Express to a remote DB on the web.

Any advice on the best strategies to adopt for this problem would be hugely appreciated.

TIA

Russ

.



Relevant Pages

  • Re: Port 1433 access
    ... your next best option is to use a VPN and access the SQL server ... than using RWW. ... You may have a slow workstation that you are using for remote desktop. ...
    (microsoft.public.windows.server.sbs)
  • Re: ODBC Timeout problems but very hard to pin down
    ... APP 1: Access 2000 database ... I ran SQL Profiler to capture the ... validated by SQL Server. ... As it happens, the default display contains ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Openrowset Jet OLEDB
    ... Front end app means the app we wrote and wich the users use to modify the ... This works fine in our development enviroment where the sql service is ... And what do you mean by "speedily import an mdb into the ... > Microsoft Access Developer's Guide to SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: A complicate cluster configuration...
    ... The SQL Server 2000 EE will be running just in one node, ... It is possible that an operator can manage the cluster from a terminal ... > and SFTPs them to a remote machine. ...
    (microsoft.public.windows.server.clustering)
  • Re: Fail to remotely connect to SQL 2005 named instance
    ... Microsoft Online Partner Support ... SQL Browser doesn't work. ... Microsoft SQL Server MVP ... I am able to connect to SQL2005 from within the remote machine itself ...
    (microsoft.public.sqlserver.connect)

Quantcast