VPN access to VMWare Server 2003 with SQL Server 2005

Associate
Joined
19 Mar 2008
Posts
638
Location
London
Hi all,

I'm trying to set up a development environment at home but I'm lost in setting up the VMs using Workstation 6. I have a few questions that give me way too many dead-end links in Google so I'm hoping someone will be able to shed some light or point me towards the right direction.

wanted Setup:

VM with Server 2003 + SQL Server 2005 (call it sqlsrv)
VM with Server 2003 configured for IIS, XML Web Services (call it appsrv)
2 or more VMs XP Clients (xp01...xp02 etc.)

behaviour:

- XP client VMs with VB.Net front end apps to call XML services on appsrv
- XML services in appsrv must be able to connect to the sql server database sqlsrv to read/write

To do the above, all documentation points towards setting up a team on Workstation or can I have separate VMs? Any settings I need to be aware of/change?

The next bit is where even the documentation looses me:

- On my laptop, where I have Visual Studio setup, along with IIS; I want to be able to configure it to connect to the SQL Server database on appsrv even when I'm not at home. In other words I want my laptop to connect remotely via VPN? to the database sitting at home on a VMWare instance (sqlsrv). And use it just like any other database engine listed in SQL Server Management Studio (on the laptop). I'm hoping this is possible.

How would I go about doing that? I know I need to enable some ports on my router for VPN, which if I google I should be able to do. But how do I expose the SQL server instance within the VM for remote usage?

I'm running VMWare workstation 6 on a vista 64 host at home, XP laptop. Be Broadband, with the speedtouch modem/router.

Loads of questions I know, but I could appreciate some direction.

Many thanks.
 
i must admit i'm not familiar with VPNs/sql server at all.... :o

but if you configure each VM with a bridged network adapter and you configure the IP addresses manually in the same range as the router and your host machine, you're basically taking the fact they are virtual out of the equation. now you can just look at bog standard guides for accessing your servers from outside your local network. :)
 
Back
Top Bottom