Hi Aldo,
That's interesting.
If your home remote connection is noticeably better than your office connection at night when the office is not operating . . .
Then your office connection might be tying up your remote AC server with a flaky connection.
When the remote AC server isn't dealing with static from the office, so to speak, it might be able to talk to your home system normally.
****
At your office, you can search for "command" in the Windows 10 search box . . .
Use the result to open a command prompt window . . .
And run a ping -t ipaddress from 9am to 5pm to see if packets are being dropped.
You can minimize the ping window and work normally--it won't slow you down.
Use 8.8.8.8 as an ipaddress if your AC ipaddress doesn't respond--some sites block ping.
CTRL-C will exit from ping, and CTRL-BREAK will pause ping and show the current error percentage.
This is just a way to try to rule out some less than obvious problems at your end.
Cheers,
Carl Fogel
