We manage a law firm's computer network. The server operating system is Windows Server Essentials 2012 R2. We installed the new network in 2015, and overall it has worked very well.
One of the senior partners at the firm lives a long distance from the office. As a result, he relies on the Remote Web Access (Anywhere Access) to work remotely. His desktop computer has Windows 10 and he uses Google Chrome as his primary web browser.
Until recently, the RWA system has worked very well for him. Recently, though, he has been unable to connect to Remote Web Access. Instead his attempt to do so with Chrome results in a timeout error and failure. Please note that he has used Chrome for this function since 2015 and it has worked consistently and reliably. Also, he is able to connect to many other web address without problem.
We tested connecting to their Remote Web Access system from our office, using various browsers, computer and operating systems (Windows 10 and 7). In every case we have connected easily to RWA. The only time we experienced the timeout error with Chrome was when we incorrectly typed the RWA address. Once that was fixed, everything worked perfectly again.
Given this background and recent problem, does anyone have any ideas how we can fix this? Thanks very much for your help.
TechNet forum original post link:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/9ab758e8-2e5a-472d-a48f-252393528c73/one-client-computer-suddenly-cannot-connect-to-remote-web-access-system?forum=winserveressentials