Remote Web Access – techspeeder

Remote Web Access Server 2012 – Opens only Dashboard not Remote Desktop Session

Merlin Halteman — Wed, 25 Feb 2015 00:42:19 +0000

Here is a small tip for the enterprise user. The new remote web access that comes with Windows Server 2012 and 2012 R2 is really nice. However, I ran into a problem when I wanted to connect to the server using the remote web access website. When I clicked on the server I wanted to connect to, instead of connecting to the server using a remote desktop connection, it would connect to the server dashboard instead. It is actually quite simple to disable the setting when you know where to look. Here are the instructions.

Step One: Open Windows Server Dashboard and click on Home > Getting Started

Step Two: Click on Setup Anywhere Access > Click to Configure Anywhere Access

Step Three: Click on the Customize option beside Website Settings.

Step Four: Click on Server Connection Options tab. Under Server Connection Options you can select how you want to connect to your server using remote web access. By default Open Dashboard will be selected, just select Open Remote Desktop instead. Save your settings and you will be all set.

This was posted by techspeeder.

Server Error 404 – File or directory not found – When accessing Remote Web Access

Merlin Halteman — Sat, 01 Mar 2014 13:34:58 +0000

Here is a compatibility issue I ran into a couple times. When a someone tries to access their remote web access portal, they get an error. After putting in their credentials the remote web access portal will begin to load then all of a sudden they will get the following error.

Server Error 404 – File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Sometimes this error indicates something more serious, but recently I have found that you will get this error because of an Internet Explorer 11 and remote web access incompatibility.

The first thing to do is check which version of Internet Explorer you are using. Go to the Gear icon and click about Internet Explorer. Check if you are running Internet Explorer 10 or 11. If you are , add your remote web access URL into the compatibility mode list.

Here are the steps to add the site into Compatibility View. Click the gear icon

and select the Compatibility View Settings options. Add your website to the Compatibility View list and hit Close. Refresh your tab and see if that makes a difference, it did for me.

This was posted by techspeeder.

Remote Web Access Error ” An unexpected error occurred”

Merlin Halteman — Tue, 14 Jan 2014 23:34:44 +0000

Remote Web Access is awesome, when it works. We recently set up Remote Web Access on a server running Server Essentials R2 . It was working beautifully, until it went down without warning. You could log onto the website but when you clicked on a computer to connect remotely nothing would happen. When I tried to click on a shared folder it would come up with the following error:

An unexpected error occurred. Please try again. If the problem continues, contact the person who manages your server.

Between another tech and I, we troubleshot this error for hours, but we couldn’t find a solution. I called Microsoft about the issue and after a one and a half hours of troubleshooting they fixed the issue. This is what they said was the issue.

Troubleshooting Steps:

1. We were getting unexpected errors while accessing shared folders remotely

2. The tech found IIS handlers were missing

3. She went to IIS > server level ( parent level) and added managed handler mapping :

Name: svc-Integrated-4.0
Request path: *.svc
Executable: System.ServiceModel.Activation.ServiceHttpHandlerFactory, System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

4. Added script mapping:
Name: svc-ISAPI-4.0_64bit
Request path: *.svc
Executable: windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
Name: svc-ISAPI-4.0_32bit
Request path: *.svc
Executable: windir%\Microsoft.NET\Framework32\v4.0.30319\aspnet_isapi.dll

5. Ran IISreset.
6. We were able to access resources in Remote access, then.

This frankly went over my head, but I thought I would post this just in case someone else had the same issue as our client had. Good luck!

Update: 1/22/14 Another customer was getting the same error when trying to connect to their computer remotely. For that situation, the problem was resolved when I opened command prompt as an administrator and ran the command: IISreset (step five). I could then access the computers and shared files just fine.

This was posted by techspeeder.