February 19, 2018, 04:35:29 PM

Author Topic: Remote Web Access: Clicking Connect does nothing  (Read 7195 times)

Offline Adventech

  • Bringing Integrity to Information Technology
  • Administrator
  • Jr. Member
  • *****
  • Posts: 60
  • Karma: +0/-0
    • Adventech Group, Inc.
Re: Remote Web Access: Clicking Connect does nothing
« Reply #2 on: January 07, 2016, 07:43:27 PM »
Edit the web.config file in "C:\Program Files\Windows Small Business Server\Bin\WebApp\RemoteAccess"

Find the line <serviceHostingEnvironmentaspNetCompatibilityEnabled="true" /> [near the bottom]

Change <serviceHostingEnvironmentaspNetCompatibilityEnabled="true" /> to <serviceHostingEnvironment aspNetCompatibilityEnabled="true" minFreeMemoryPercentageToActivateService="0" />

Restart "World Wide Web Publishing Service". This will also restart "Remote Desktop Gateway".
« Last Edit: January 07, 2016, 07:45:47 PM by Adventech »
Adventech Group, Inc.
Bringing Integrity to Information Technology

Offline James

  • Administrator
  • Newbie
  • *****
  • Posts: 26
  • Karma: +1/-0
  • I'm New!
Remote Web Access: Clicking Connect does nothing
« Reply #1 on: February 13, 2014, 08:22:58 AM »
When trying to connect to a remote workstation through Remote Web Access, nothing happens when clicking connect.

Review the following steps to re-enable access:

  • Ensure that the remote computer has remote access enabled and that the firewall settings are correct
  • Ensure that you are connecting using Internet Explorer 10, or if using IE11, ensure that the server has the latest updates (these address connection issues with IE11)
  • ActiveX needs to be enabled and scripts allowed (on the computer you're connecting from). You can reset Internet Explorer, and click 'Always Allow' when prompted after clicking Connect.
  • Add your Remote Web Access portal address to your list of trusted sites

If, after clicking connect, you have been prompted to allow ActiveX controls, but then nothing else happens, and you are able to connect after restarting your server, the issue is more than likely due to your Remote Web Access not starting due to excessive memory usage on your server. To correct the issue you can set the Remote Web Access to ignore available memory:

Using Notepad open the Web Configuration file on the server located at:
C:\ProgramFiles\Windows Small Business Server\Bin\WebApp\RemoteAccess

Locate the command line (near the bottom of the file):
<serviceHostingEnvironment aspNetCompatibilityEnabled="true"/>

Insert the following code into the above command line:

So the completed line should be (all on one line):
Code: [Select]
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" minFreeMemoryPercentageToActivateService="0" />
This should allow your Remote Web Access to connect regardless of the available memory on the server.
« Last Edit: January 07, 2016, 07:44:30 PM by Adventech »