myPractice not communicating with Server over a VPN Connection - Powered by Kayako eSupport Help Desk Software

08 Sep 2010

Support Center » Knowledgebase » myPractice not communicating with Server over a VPN Connection

	myPractice not communicating with Server over a VPN Connection

Article If you are hosting your own myPractice Live set up and are having problems with myPractice working Online while using a VPN connection please try the following:

On the Server:

Open SQL Configuration Manager on the Server go to - Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager

If there are multiple instances of SQL Server running, you should look for the one called <ServerName>\MP (where <servername> is the name of your server :)

1: TCP/IP should be enabled

2: Client Protocols > TCP/IP should be enabled

3: Right Click the TCP/IP Protocol and scroll to the bottom - To set a static TCP/IP port, make sure 'TCP Dynamic Ports' is blank and TCP Port has a value set. The default SQL Server Port is 1433, but SBS runs at least one or more instances - so you have to select a port that doesn't clash with another instance.

4: Scroll up the list and make sure that each required Interface IP has 'Active' and 'Enabled' set to yes. Note: you don't need to worry about the TCP Dynamic Ports and TCP Port settings on each IP because the Port settings at the bottom (for 'IP All') overrides all the Port Settings above.

5: You should then restart the SQL Server Instance you have just adjusted to put the new settings into effect.

On the Client Computer:

If the above steps do not resolve the issue please try the following in case there is a problem with name resolution.

1: On the Client, go to the C:\Program Files\myPractice folder and find myPractice.exe.config

2: Open it in Notepad and search for the tag "DBServer" (note there are 2 similar entries, DBServer and DBServerSolo - you want the former)
It will show the SQL Instance name which will likely be <servername>\MP

3: You can eliminate name resolution as the problem by changing that setting to <IPAddress>\MP, where <IPAddress> will be the IPAddress of the server on the VPN Interface.

Article Details

Article ID:

Created On:

18 Sep 2009 11:06 AM