Playing on BBO today I was disconnected more than 20 times. Happened multiple times on some boards. The system often did not tell me - I thought I was still connected, waiting for opponents to bid or play. Once I realized I was off line, I was always able to reload and quickly reconnect, so I think my internet connections was okay, it was the link between my browser and BBO. I use Optimum as my ISP, and Google Chrome as my browser. I also have Optimum 5G, and can also use a VPN. I rebooted my system while dummy, and nothing seemed to improve the situation. any suggestions? Thanks!
Page 1 of 1
connectivity issue got disconnected more than 20 times during 18 boards
#2
Posted 2023-April-13, 14:33
If your computer is connected to wired ethernet, and it was having issues (My example was powerline ethernet) AND wireless was also available, it could be that your computer was swapping between the wired and wireless (and back) every time there was an issue. Every time the network changes - and that counts as a network change - BBO drops. And frequently it fails like that - it all looks fine, just that everybody else isn't doing anything, until boom, logout.
I'm sure others will have other ideas, but that one is one I know about. There are several examples of this behaviour on the forums.
I'm sure others will have other ideas, but that one is one I know about. There are several examples of this behaviour on the forums.
Long live the Republic-k. -- Major General J. Golding Frederick (tSCoSI)
#3
Posted 2023-April-13, 15:02
mycroft, on 2023-April-13, 14:33, said:
If your computer is connected to wired ethernet, and it was having issues (My example was powerline ethernet) AND wireless was also available, it could be that your computer was swapping between the wired and wireless (and back) every time there was an issue. Every time the network changes - and that counts as a network change - BBO drops. And frequently it fails like that - it all looks fine, just that everybody else isn't doing anything, until boom, logout.
As mentioned recently on a related thread, you can replicate this defect consistently by forcing a network change, at least under Android.
Page 1 of 1