On 1 out of 11 Balance One’s will not connect via Remote Web Admin on the Incontrol2.peplink.com management portal. It starts out normally: opens in a new tab, rectangle screen with the spinning circle appears, after about 45 seconds it simply does goes to a blank white screen. This started around December 11th.
Tried: Chrome 70 and IE 11, Incognito and Inprivate, cleared temp files, connect from a remote computer (behind balance one) and another in Azure (no peplink firewall), upgraded firmware from 7.0.1 to 7.1.1, rebooted Balance, rebooted cable modem (ATT U-verse [other U-Verse sites work]), all three user accounts on InControl having same issue (earth.ic.peplink.com), turned off InControl on the Balance–applied changes–reboot–turned InControl back on–rebooted.
I can connect from local computer to the admin console.
OK, we figured out that ATT U-Verse was blocking or throttling the connection port. We contacted their support staff and had them put the modem in Bridged mode–open pass thru. Requires a reboot whether they think so–two other sites had to do the same to get SMTP to send and both required reboot of modem. Rebooted modem and now I can connect.
Micheal’s response was: " managed to find the device you are referring to is . I find the RWA connection between the device and IC2 can be established. But the connectivity just stalls when the device sends a larger amount of data (i.e. web admin contents). I find the same behavior in connecting to our remote assistance server too.
Usually, the behavior is due to a too large MTU value being set on the WAN. But I find the MTU is not large which is 1440. So I suspect your ISP is applying traffic control on uncommon outgoing TCP ports.
I suggest you try another WAN connection and see if the problem still persists. If not, it will mean the problem is really related to your existing ISP."
FYi Micheal wrote “I find the same behavior in connecting to our remote assistance server too”. He could see that because I enabled remote support prior to being requested to do so. I figured it would be tried and would speed up troubleshooting.
Follow up: Ultimately we ended up having ATT replace the modem. After a day, the remote console began failing to load again. We remoted onto a local PC and connected to the modem web admin console to compare its settings to another ATT site that was working. In the process of doing that we noticed that the ATT modem’s firewall settings page and several others would not load. We just had the modem replaced this morning and can connect again.
