Orchid

Please be advised that our integrated credit card processing through Card Connect is currently experiencing transaction timeouts and failures. Investigations are underway and a resolution is coming soon. For more immediate updates, visit status.cardconnect.com and subscribe for text and email alerts. We apologize for the inconvenience and thank you for your patience!

Happy Holidays! Please be advised that our offices will be closed December 24th, 25th, 31st, and January 1st to allow out employees to spend time with their families this holiday season.
Thank you for your understanding.

>System Maintenance is scheduled Sunday night, April 22nd, between 10:00 PM and 5:00 AM EST Monday, April 23rd. While these database upgrades and maintenance is necessary, it will mean that our online services will not be available during this maintenance window. These services include: online booking, messaging, remote access, memberships or any account management. We apologize for any inconvenience this work may cause and thank you for your service and patience.

We recently experienced a service outage related to some Amazon Web Services, which affected key functionality of our Remote Access Service. This interruption happened on Thursday, June 22nd, between the hours of 9:00pm and 2:00am EST. The Remote Access Service is now fully restored. If you continue to experience issues with your Remote Access Service, please follow the directions on this Support Article to restart the Remote Access Service and try reconnecting again. You can also restart your computer to restart your service. If you are still experiencing issues afterwards please contact our support team at 1 (800) 604-2040.

All of our services have been restored after a brief interruption that impacted our Cloud online services. This interruption occurred between 9:45 a.m. and 10:55 a.m. EST on September 18th. We apologize for the inconvenience and thank you for your patience!

Using Norton Security 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 Norton Security enabled. These instructions do not extend to any other 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 Norton Security Firewall
To connect a client to a server in a network environment, Norton Security will likely need added rules and/or exceptions. If you cannot connect your client to the server with Norton Security enabled, then follow these steps on all computers in your network to configure it properly to allow connections.
  1. Right click on the Norton Security icon, which is typically located in the system tray in the bottom right of the screen, and select Open Norton Security.
  2. Click Settings in the top right corner. 
  3. Select Firewall.
  4. Click on the Traffic Rules tab.
  5. Scroll down the list of items until you locate Default Block Inbound and Outbound ICMP. Uncheck the box to disable the rule. 
  6. Scroll down the list of items until you locate Default Block All Inbound Windows Services (Public Networks). Uncheck the box to disable the rule. 
  7. Press the Add button.
  8. On the new window that comes up, select Allow. Press Next.
  9. Select the option for Connects to and from other Computers. Press Next.
  10. Select the option for Any Computer. Press Next.
  11. From the drop down list, select TCP and UDP. You will then want to select The rule will apply only if it matches all of the ports listed below.
  12. Press Add.
  13. On the Specify ports window, select Known port from list for the Filter by option and select Remote for the Locality option. Scroll down the list and locate ports 1433 and 1434. Check both boxes and press OK
  14. The window you have open should match the picture below. If everything matches, press Next
  15. Verify that the option for "Create a Security History log entry" is unchecked and the option for If Explicitly requested is enabled. Press Next.
  16. When asked what to call the rule, enter SQL Server (TCP and UDP). Press Next.
  17. Verify that the settings on screen match the picture below. If not, go back and follow the previous steps for creating this new rule. Once everything matches, press Finish
  18. Press Apply to save all of these changes. You can then close all of the windows for Norton Security.
These are all the exceptions Norton Security requires to be enabled and allow client connections to the server. If you still cannot connect with Norton Security 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 herin are the ones that will need to be opened on those firewalls.

Did you find this article helpful?