Quantcast
Channel: Small Business Server forum
Viewing all articles
Browse latest Browse all 8539

Windows 8 error when connecting to SBS2003 Remote Web Workplace

$
0
0

Ok, now that we know what the solution is to get Windows 8 working with RWW for SBS 2008, 2011 it is time to look at SBS 2003 and see if there is a solution.

Using Windows RT for this test, using IE in Desktop. Set the address in Trusted Sites, and compatibility view settings.

(I already expect that it is related to something included in Rollup 6 as Susan mentioned in another thread.)

We are able to get to OWA and use companies internal web site from RWW just fine.

When connect to my computer at work is selected the following happens.

Get the standard selection box to select the computer, and click the connect button.

The get the following box:

VBScript

The Remote Desktop Web connection ActiveX control can only run in the 32bit version of Internet Explorer.

OK button

Click on the OK Button and then get the Remote Desktop Connection Pop-Up box about the resources trying to open.

Just for grins click on the Connect button, then get a box with this long message.

VBScript: Remote Desktop Disconnected

The client could not connect to the remote computer. Remote connections might not be enabled of the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connection again later. If the problem continutes to occur, contact your administrator.

OK Button

Click the OK, and back at selection screen to select system.

(I had tried this a few times)

Now this gets more interesting.

Just did this with administrator level ID, and selected Connect to Server Desktops

I get the first error about 32-bit, click OK, click connect in pop up, get sign in for SBS 2003.

Then complete sign in. and at desktop for server.

Now try this with admin level ID and I am into a workstation and at the desktop.

Closed IE down, reopend and went to RWW and used regular User ID, and I get the first error code and then get into the workstation.

Go figure.... Would love to get rid of the first error message, but I can live with it if I can connect.

Anyone else seen this behavior? Come up with a reason or solution?

Thanks

Tom



Viewing all articles
Browse latest Browse all 8539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>