I have to be honest, up until now I've been a big SlingBox fan. I've convinced lots of my friends to get them. Several ex-pats I know have them just for the ability to watch football.

But this proxy server problem sucks. My fancy and expensive new Pro-HD does me about as much good as a doorstop. Version 1.5 is not on the download page, you have to hunt around for it.

I asked if I could load both versions 1.5 and 2.0 on the same machine as a workaround - no luck.

Basically I'm stuck. I can use 2.0 on the home network PCs but my work machine will have to be stuck with 1.5. I see no reason to hook up the Pro-HD for now, what a waste!

I can't recommend SlingBox to friends any more.

Thanks Brandon. I have loaded both Versions 1 & 2. They seem to work OK on the home LAN. Version 1.5 found the Pro-HD, but when I tried to configure it (tell 1.5 what video source it is hooked to) 1.5 will display the video but when you get to the screen for picking the country it say that USA is not supported, then it just exits setup.

I have a Slingbox A/V and the Pro-HD hooked to the same video source, a DishNetwork 722. Luckily the 722 has both component and composite video out.

Where would I find the IP address of my proxy server? Don't say "call your IT department" - they aren't really inclined to help me. (could it be the "IP Subnet Mask" address? I see in SP 1.5?)

I finally got things working - sort of.

On my new Windows XP notebook I uninstalled SP 2.0 and reinstalled 1.5. I then renamed the 1.5 program file directory to \Slingplayer1\. I created a shortcut to the desktop and renamed it SP 1.5. Then got SP 1.5 working on my home network first. I set up the Solo and the A/V just fine. SP also found the Pro-HD. I could set it up for digital cable, where it functions perfectly and it sort of works for my Dishnetwork VIP722. I can see the picture on 1.5 but the remote is not functional. The picture is converted to SD, but at least I can watch it.

Next I tried to get SP 1.5 to function at work behind the firewall yesterday. No such luck. Then I remembered a trick. I went to a local coffee shop and got it working on their wireless network. Today when I get back to the office, SP 1.5 now works. When I look at the connection page, SP 1.5 is set for a direct connection, but somehow is able to get through the firewall with no problem.

I also loaded SP 2.0 on to the machine. I let the software load itself in whatever directories or shortcuts it wants. I had also created a SlingAccount that had my SB Solo, A/V, and Pro-HD all registered. I was able to configure all 3 SlingBoxes correctly. I went into the network router settings and set up a unique port and IP address for remote viewing of the Pro-HD and confirmed the settings for the other devices. From the coffee shop I was able to pull up all 3 SBs. I am able to watch the Pro-HD in its full HD glory from both home and from the fast wireless over the internet. Although sometimes it slips back th VGA mode.

When I try to bring up SP 2.0 at work behind the proxy server, SP 2.0 says it cannot find an internet connection. For some reason SP 2.0 cannot negotiate its way through our company proxy server, whereas SP 1.5 can.

So, my setup is:

Dish VIP722 ---> SB Pro-HD ---> SB A/V
Digital Antenna---> SB Pro-HD

Dish VIP622 ---> SB Solo

I can watch Slingbox for 2 satellite receivers on 3 Slingboxes. Yes, I have a router and a 16-port ethernet switch with 4 Ethernet connections to my main home theater setup. It all works, but it would sure be nice if SlingMedia could get the proxy server thing working again.

Internet explorer uses a script. I was able to download the script and open it with Notepad. Yes, it looks like 127.0.0.1 and port 1080 is the proxy server address. I entered those into SP 2.0 under Options>connection, then pressed "Test Connection". Instead of failing immediately, it shows "connecting to www.sling.com" and then just hangs.

But it does the same thing if I enter "Direct" as the connection. SP 1.5 also uses a "direct" connection and works fine. I think this is a problem with SlingPlayer 2.0 and certain types of proxy servers, not a configuration setting problem. I've tried a couple of the proxy addresses used in the script. 127.0.0.1 is the only one that doesn't give an error.