To begin, set aside one computer on your network to host your server. Run the server installer from your start package to install the server software. When your done, make sure you can log-in and run the RepairShopPro. On first time login, use username="Admin", password="Welcome". After that, set-up dedicated user accounts using the Employee Editor under the Editors menu. When a user logs-in to your network, he will have his own private session dashboard. You can optionally restrict access on a user account by customizing his role using the Roles Editor under the Editors menu. At this point you can begin using the system for production work. When you're ready to add more terminals, proceed to the next steps.
(Step 1) Make sure SQL Server is running and configured to accept remote connections. To do that, go to the Windows Start Menu and type "SQL Server Configuration Manager" into the Search Programs text box to open the main dialog. Next, select the "SQL Server Services" node. In the right pane, confirm the SQL Server (SQLREPAIRSHOPPRO) and SQL Server Browser (SQLREPAIRSHOPPRO) services are running and the Start Mode property is set to Automatic.
If either service is disabled or the Start Mode property is not set to Automatic, then double click the service name, select the Service tab from the pop-up, then set the Start Mode property to Automatic. Click OK to accept. When you're returned to the main form, right click the service name, then select Start if it's not running.
(Step 2) Enable TCP\IP protocol. Expand the SQL Server Network Configuration Node and select Protocols for SQLREPAIRSHOPPRO. In the right pane, double click TCP\IP. From the Pop-up switch to the Protocol tab and set Enabled = Yes and Listen ALL = Yes. Next switch to the IP Addresses tab and scroll to the bottom. Under IPALL, set TCP Port to 1433. Select OK to confirm your selections. The SQL Server service is now ready.
(Step 3) This completes the SQL Server setup. Next we will open a few ports on Windows Firewall to allow inbound traffic on the SQL Service ports. To do that, open a command prompt using the "Run as Administrator" option and execute the following commands. Note: If you're running MacFee or some other 3rd party application to manage Windows Firewall, then you will have to open the service ports on it too. Or can turn it off temporarily.
This command opens the SQL Service port on TCP 1433
This command opens the SQL Browser Service port on UDP 1434
When you're done, go to the Windows Start Menu and type "Windows Firewall" into the search box. Next, select the "Advanced Settings" link and click on Inbound Rules. Confirm the highlighted rules have been created.
(Step 4) Install the client software from your start package on as many terminals as you have licenses.
(Step 5) Configure client connection strings. On each terminal you will be prompted to enter your connection string when the program starts. If you installed your server using the supplied installer, you will only need to enter your Server IP Address or Computer Name as shown in the sample below. Everything else will remain the same. If you're doing a custom server install, then the format will be the same, but the values will be different. If you're using a commercial host, then they will supply you with a connection string. When you're ready, select "Test Connection" from the Connection String editor as shown below. If you can't connect, go to the Troubleshooting section.
Data Source=YourServerIPorComputerName\SqlRepairShopPro;Initial Catalog=RepairShopPro;User ID=SA;Password=1Administrator$
Troubleshooting Log-in Issues:
First, take note of your server's IP address. To do that, open a Command Prompt on the server and type-in IPCONFIG, then hit ENTER. The IP address is listed as the "IPv4 Address" as shown below.
To determine whether your SQL Server is running, configured to accept remote connections and your firewall is open on the correct service ports, open a Command Prompt on one of your network terminals. Type-in TELNET, your Server IP Address and 1433 (ex. TELNET 192.168.1.2 1433), then hit Enter. If a TELNET session does not begin: