2 Replies Latest reply: Nov 10, 2012 12:12 PM by doitt2 RSS

    Slingbox 500 wireless connection funny with Airport Extreme


      I have my new Slingbox 500 wirelessly connected to my Apple Extreme router via the 802.11 5Ghz channel.  The airport extreme radio mode is set to the default of "802.11a/n - 802.11b/g/n (automatic)".  Also, as I have done in the past with Slingboxes, I have manually opened TCP port 5201 and assinged it to the Slingbox IP address assigned by the extreme.


      The Slingbox connected flawlessly to Airport Extreme, but the Airport Extreme is reporting it is connected as a "802.11a" connection, vice the expected "802.11n" connection. 


      A picture is attached of what the Airport Utility is reporting.  The MAC address with the 802.11a next to it is the Slingbox 500


      Is this some incompatibility with Airport Extreme's ??

        • Re: Slingbox 500 wireless connection funny with Airport Extreme

          Slingbox doesn't publish the detailed specs of this device. I am seeing the same behavior on my network.I suspect they went with a less expensive a/b/g radio, rather than an a/b/g/n. I suspect if they were using an "n" radio, they would have published that fact.

          • Re: Slingbox 500 wireless connection funny with Airport Extreme
            doitt2 Newbie

            My Extreme is the latest generation model, and the slingbox 500 is configured for the 5GHz band.  The Airport Utility 6.1 reports 802.11a/n, no different than many other devices on my network.  My qualm is that the signal strength of the 500 is particularly weak in comparison to other devices in the same room, but it still is able to stream 6000-8000 to the browser client. and 4000-6000 to the iPad.  My other qualm is that the slingbox won't connect when the WiFi is configured as hidden, so I have to broadcast it just for the slingbox to connect.


            I see from your image that your rate of 54 is consistent with the max rate that 802.11a is capable of.  In my case, I see a reported rate of 120 Mb/s, so I believe it is actually connecting using n and not a.  If I were troubleshooting it, I would power down both router and slingbox and try relocating the router close to the slingbox, then power up, and check to see if it initiates a connection with n.