Mobile Traffic Change Monday


A second IT department out in the healthcare world has updated their servers to block an older encryption mechanism that one of our network devices currently utilizes. This happens to be the network device the Mobile communication servers route through.

What this means is that they were unable to update mobile or upload charts because the current internet network they connected to didn’t “trust” the connection. The simple fix was to push that agency to another set of servers on our side.

While we had planned to eventually move the Mobile servers to the newer network device, we are moving up the plan to prevent any additional confusion.  However, we will NOT be shutting down the old device, just pushing the primary traffic to the new device.

This switchover on MONDAY JULY 27th should be seamless for all intents and purposes.

Essentially, if your network/internet provider does NOT update their records, it will push your traffic to our old load balancer and you’ll be OK since we’re still accepting traffic there. If your network/internet provider does update their records, then you’ll be hitting the new site.

We determined those who will have an unresolvable problem will be those forced to run an old version of an OS, such as XP Service Pack 1/2, for example AND whose IT staff has purposely blocked the older encryption mechanism (i.e. “the problem”). If you upgrade to Service Pack 3, then you can contact support to help you switch to our alternative (older) site:

In the end, if anyone has any problems connecting to mobile just give us a call and we can look at your configuration and alter your configuration file.

In case of a problem AFTER Monday,  we’ll have our staff request a couple steps from you:

1. If you hit the Start button and type CMD and hit Enter, it will take you to a DOS prompt.

2. From there, if you type “nslookup” (without the quotes) it should give you an IP address.

3.  If it ends with “.131” then your provider hasn’t switched you over to the new server yet – which may be fine, but if you have an issue then please give us a call.

4. If it ends with “.148”. Then type “ping” and let it timeout. If this time it ends with “.131”, then when the ping times out type “ipconfig /flushdns” (always without the quotes) and try it again. It should update to “.148”. If it doesn’t AND you have a problem, then give us a call.

In summary, it should be fine, but if you have troubles, try the above first. Thank you!