- 11-17-2012, 02:43 PM #1
For anyone interested, Slingbox seems to be working on the Surface by going to this link within the Slingbox website:
The only problem is, it only works in the desktop version of IE 10. Anyone have any idea why it's not working in the Metro version??
- 11-18-2012, 07:27 PM #4
Here's how you can get it working with the Metro version of IE 10.
How to use SlingPlayer to watch SlingBox video on the Surface RT | Microsoft Surface Blog, Windows RT, Windows 8, Surface Pro, Xbox Surface, Microsoft
Works fine, the only issue is when it comes to closing and reopening IE. I've found that you have to reconnect the player.
Hope that helps.
- 11-19-2012, 08:09 PM #5
- 11-20-2012, 07:46 PM #9
- 12-11-2012, 12:20 AM #10
I have tried the embedded player in the desktop browser and it works fine over my home network...ie when in the house. I tried over internet sharing on my Nokia 920 to get off the home network and it didn't work. Anyone else have this problem or able to access it outside of their home network??
- 12-11-2012, 11:40 AM #11
I have it working when tethered to my Lumia 920. The embedded player doesn't work outside your home network unless port forwarding is set up on your router for the slingbox. I believe the port for the slingbox is set to 5001 by default.
- 12-11-2012, 01:37 PM #12
- 12-11-2012, 10:16 PM #15
Also, make sure you hit the disconnect icon when you want to disconnect. If you just close out the window, the slingbox thinks it's still connected to something. After that, you can't reconnect unless you unplug the box. Screwed me over when I was away for a weekend.
02-07-2013, 01:45 PM #16
- 8 Posts
Hi, can you be specific as to how you set up the port forwarding here? I had this working perfect after setting up port forwarding on the network of where the slingbox is set up while I was on the same network as the slingbox last week, however now that my Surface is not on the same network as the actual slingbox, I'm getting the "We're sorry, but your current web browser, operating system, or the combination of both is not currently supported by the SlingPlayer plug-in. Please click here for more information." message.
Thanks in advance for any tips you can give.
- 03-13-2013, 11:42 PM #17
Prior to early February the embedded Slingplayer approach was working fine on my Surface RT. Since then Adobe has coordinated several cumulative Flash patches with Microsoft that address potential security risks and these patches have the effect of rendering the embedded Slingplayer inoperative. I have implemented all the whitelist and registry modifications but nothing solves the issue except uninstalling these patches as they arrive. The latest patch reference number is KB2824670 released yesterday. Same result. Also requires inhibiting auto updating via a registry setting so I don't have to uninstall the latest patch daily. I'm sure the Flash security patches are important and would rather have the latest fixes but also want to use my Surface with the Slingbox. So, after explaining this experience I'm curious to know if others are experiencing the same problem and, more importantly, has anyone found a solution.
Thanks in advance for any insights.
- 03-14-2013, 12:26 PM #18
I'm still having no problems connecting to the Slingbox Embedded Player though the desktop browser, even after yesterday's latest patches. Still doesn't work in Metro IE10 and I doubt it ever will. When you try to start the player in IE10, what happens exactly?
- 03-19-2013, 01:08 AM #19
clarity1981, thanks for the feedback.
Noting your ability to use embedded slingplayer with all the latest Flash patches I took it upon myself to completely restore my surface to factory software load and proceed to reinstall all patches from scratch. Unfortunately this did not solve the problem and I still need to uninstall latest Flash patch for the player to function. What happens when the patch is installed is rather odd. The player behaves normally establishing a connection (upside down horseshoe screen) and will display Slingbox Directory with my device. If I perform the network test I obtain excellent bandwidth performance and the player recommends using Best Quality so everything seems fine. However, once I click my slingbox the horseshoe screen reappears as it should but takes an excessive amount of time 'Optimizing' then eventually comes back with the No Video Detected screen. I know the slingbox is operating correctly via my laptop and, after I uninstall the patch, my surface will work as well. Also makes no difference whether I connect locally on my wireless LAN or remotely or reduce quality setting. Perhaps something in the router but 5001 port is correctly forwarded and all works well either locally or remotely as long as the patch is not installed on the Surface. Soooo, still looking for ideas.
07-03-2013, 05:51 PM #21
- 9 Posts
THe problem I have is working out which patch(es) need to come out as we are many months down the line since this was first discussed - certainly I'm wondering if making my system more vulnerable is worth it just for the sling player though. I really wish that sling would take some interest and at least update their knowledgebase with some patch numbers that break it or something. At least then people can decide if they want to try it.
07-21-2013, 02:53 PM #22
- 9 Posts
just an update - on the 8.1 preview, with flash patches taken out, definetly doesn't work. I read on a site that the new slingbox the 350 and the 500 work fine with it though. I have an older solo. Oh, and if you take the patches out they don't stay out - no way to turn off autoupdate on an RT.
- By franzoso in forum Microsoft Surface for Windows RTReplies: 4Last Post: 11-03-2012, 09:30 AM
- By Daniel0418 in forum Microsoft Surface for Windows RTReplies: 0Last Post: 10-27-2012, 10:17 PM
- By franzoso in forum Microsoft Surface for Windows RTReplies: 12Last Post: 10-26-2012, 07:46 AM
- By nuprotocol in forum Microsoft Surface for Windows RTReplies: 11Last Post: 10-21-2012, 03:13 AM
- By mafu6 in forum Microsoft Surface for Windows RTReplies: 5Last Post: 10-18-2012, 09:07 AM