This is an old revision of the document!
Table of Contents
IT/Network Troubleshooting
.decimal System Status
Prior to beginning the network troubleshooting steps refer to our status page to determine if there is a service outage with any of the .decimal backend services.
As the software provided by .decimal requires access to the internet to place orders, the proper functioning of our software can be affected by the local network within which the software is installed. Since each customer facility implements their own unique security, firewall, and networking policies we cannot guarantee support for all configurations. Therefore, this guide was created to provide general troubleshooting steps to help our customers and their IT departments ensure they are not blocking or interfering with .decimal software and the HTTPS requests to .decimal's servers that are required to install, authenticate, and place device orders.
Traffic Architecture
.decimal's applications communicate via HTTPS to our server resources. The diagram below demonstrates how our HTTPS traffic flows through each piece of infrastructure and identifies common failure points:
Common Issues and Resolutions
- Blocking or filtering the required .decimal urls or ports:
- .decimal applications require specific urls(or IPs) and ports to be unblocked and unimpeded in order to authenticate and place orders to .decimal's servers. Refer to the System and Network Requirements document provided by .decimal staff. At a minimum the url direct.dotdecimal.com (64.128.252.104) port 443 is always used. See below for each applications latest network requirements (please ensure you have the correct application and app version):
- Proxies / Web Security Appliance (WSA):
- Some WSAs will attempt to decrypt and inspect our HTTPS traffic. Some customers have needed to include an exception in this network security device as this can impact and cause our encrypted and authenticated HTTPS traffic to encounter errors while in transit between the client software installed at the clinical facility and .decimal's servers.
Troubleshooting Steps
The following steps may help when troubleshooting network security and IT issues for your facility.
1. Compatibility Checker
Running the compatibility checker will ensure that all required .decimal IP addresses and ports are not being blocked.
Note:
The Compatibility Checker only ensures that the primary .decimal IPs and ports are not being completely blocked or blacklisted. Additional network security devices may impede or be filtering the HTTPS traffic. If .decimal software continues to encounter problems, please ensure other network security appliances and devices are not filtering or impeding .decimal's HTTPS traffic.
2. Guest/Unrestricted Network
This option is advised if your network IT has whitelisted and unblocked .decimal's urls and ports (as evidenced by a successful Compatibility Checker run), but you still encounter issues using .decimal's software and communicating to .decimal's servers.
- Attempt to download and install the .decimal client software on a device (e.g.: a laptop) not connected to your main cooperate network (e.g.: a guest WiFi network or smart phone hotspot) that has absolutely zero security or firewall blocking, filtering, or packet inspection.
- Attempt to login to the .decimal client software
- Confirm you are able to download, install, login, and use the .decimal software on an unrestricted device on an unrestricted internet connection. This ensures no security, firewall, or packet inspection security policies are interfering with your HTTPS connection and traffic to .decimal servers.
- Conclusion: If Step #3 passes, then there is still security policies in place on your main facility network impeding .decimal HTTPS traffic. We recommend disabling each network security device one by one until the .decimal client software operates normally. Then consider allowing an exception only on the offending network security devices impeding .decimal's HTTPS traffic.