Salon Iris

We are experiencing increased error rates with our online services and are actively working to resolve them. Please check our Facebook page for periodic updates.

We are currently experiencing a service outage impacting our Cloud, Remote Access, Online Booking, and other online services. We have committed all of our resources to repairing this outage and expect all services to be restored shortly. Please check our Facebook page for periodic updates.

We have some maintenance scheduled for tonight, May 11th, between 10:30 pm and 11:30 pm EST. Customers may experience a brief interruption in our Cloud, Remote Access, Online Booking, and other online services during this time frame. We don't expect any long outages and all services should be restored quickly. We apologize for any inconvenience this may cause and thank you for your service and patience.

All of our services have been restored after a brief interruption that impacted our Cloud, Remote Access, Online Booking, and other online services. This interruption occurred between 9:30 p.m. and 11 p.m. EST on April 10th. Thank you for your patience!

Using Windows Firewall in a Network Environment

These instructions will help you properly configure SQL Server to allow connection of client computers to a server computer in a network with the Windows Firewall enabled. These instructions do not extend to any antivirus firewalls that may also be installed on your workstations. For help with these, refer to vendor specific support literature or a local computer technician.

Configuring SQL Server
To connect client computers in a network environment, the SQL Server instance you’ll be using needs to be properly configured to allow client computer connections.
  1. On the Server computer navigate to SQL Server Configuration Manager. Click Windows Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager. If you cannot find it under that path, choose Windows Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager.
  2. In the left pane, double-click on SQL Server Network Configuration and highlight Protocols for CMJ.
  3. In the right pane, right click on TCP/IP and select Enable if it’s not already. You should get a warning window to restart SQL Server. Click OK. Right click on TCP/IP again and select Properties.
  4. In the TCP/IP Properties window, click the IP Addresses tab. Scroll to the bottom and in the IP All section, delete whatever contents are in the TCP Dynamic Ports row and type 1433 in the TCP Port row. Click Apply once completed.
  5. You should get a warning to restart SQL Server. Click OK.
  6. Click OK to close the TCP/IP Properties window then click SQL Server Services in the left pane.
  7. Right click on SQL Server (CMJ) and select Restart.
  8. Close the SQL Server Configuration Manager. SQL Server is now configured properly to allow client connections to the server computer.
Configuring Windows Firewall
To connect a client to a server in a network environment, Windows Firewall will likely need added rules and/or exceptions. If you cannot connect your client to the server with Windows Firewall enabled, then follow these steps on all the computers in your network to configure it properly to allow connections.
  1. Go to Control Panel and click on Windows Firewall. If Control Panel is set to Category view, click System and Security then Windows Firewall.
  2. Verify that Windows Firewall is set to On (recommended). If it’s not, select Turn Windows Firewall on or off from the left panel and set the radio buttons to Turn on Windows Firewall for both Home or work (private) and Public network settings. Click OK to accept changes.
  3. Click Advanced Settings in the left panel and select Inbound Rules in the left pane and then New Rule in the Actions panel on the right.
  4. In the New Inbound Rule Wizard select Port then Next.
  5. Select the TCP and Specific local ports radio buttons. Type 1433, 1434 and click Next.
  6. Select Allow the connection and click Next.
  7. Apply the rule to Domain, Private, and Public by checking all three boxes and click Next.
  8. Name the rule SQL TCP (1433,1434) and click Finish.
  9. Click New Rule in the Actions panel again.
  10. This time select the UDP and Specific local ports radio buttons. Type 1433, 1434 again and click Next.
  11. Select Allow the connection and click Next.
  12. Apply the rule to Domain, Private, and Public by checking all three boxes and click Next.
  13. Name the rule SQL UDP (1433,1434) and click Finish. All the Inbound Rules needed are now created.
  14. Click Advanced Settings in the left panel and select Outbound Rules in the left pane and then New Rule in the Actions panel on the right.
  15. In the New Outbound Rule Wizard select Port then Next.
  16. Select the TCP and Specific local ports radio buttons. Type 1433, 1434 and click Next.
  17. Select Allow the connection and click Next.
  18. Apply the rule to Domain, Private, and Public by checking all three boxes and click Next.
  19. Name the rule SQL Server (TCP) and click Finish.
  20. Click New Rule in the Actions panel again.
  21. This time select the UDP and Specific local ports radio buttons. Type 1433, 1434 again and click Next​​
  22. Select Allow the connection and click Next.
  23. Apply the rule to Domain, Private, and Public by checking all three boxes and click Next.
  24. Name the rule SQL UDP (1433,1434) and click Finish. All the Outbound Rules needed are now created.
These are all the exceptions Windows Firewall requires to be enabled and allow client connections to the server. If you still cannot connect with Windows Firewall disabled and you are certain your network is functioning properly, then it is likely you will need to create exceptions in other anti-virus or hardware firewalls installed on your workstations. The same ports (1433 & 1434) detailed herein are the ones that will need to be opened on those firewalls.

Did you find this article helpful?