Hi manilae90, I'm having the same problem, it was working for couple of months then suddenly got same error '0x9234006D'. All other laptops connects with no problem, except the newest and the most powerful laptop with the best graphic capability. I submitted the problem to SlingMedia tech support, it's been a week and I'm still waiting. If you get or find the solution to the problem, please post it. Tryng to be patient, jhirata

Same error message here as well.  I am having problems connecting to my Slingbox from work.  I have to connect using an IP address and an open port because my company has the Finder website blocked.  All has been going well for about a year now but suddenly it stopped.  The only change that I know of was when I upgrading my firmware last week.  It worked the reset of that day then no luck since.  I am able to ping the port sucessfully.  I also reset, rebooted, and reconfigured my slingbox several times but still no luck.  I am able to watch it at the house just fine.  Sounds to me like there may be a problem with the newer firmware.  Does anyone know where I can get the previous version to try?

Just to add to my earlier post.   I've decided to use Norton Security System in place of McAfee that came installed with my laptop.  My reason, I've had to de-install McAfee with it's updates for the second time.  It caused my error again and disappeared once McAfee was remove totally from my laptop.  I've had no problem with Norton.

Hi TNT,

If your laptop connects to Slingbox at home with the firmware upgrade on your laptop but not at work, then you may want to ask your network administrator if there's been any changes to security and firewall within your work network. Good luck and let me know how it was resolved.

Regards jhirata 

Use a different port then like 443 or do they have "WebSense" if they are using the later you will need to setup a SSH connection... That number looks the one I got when we tested the new WebSense update and selected Slingbox in the configuration when I tried to connect I received an error similiar to above. 

A shortcut has to be a challenge, because if it was easy, then it would just be the way.

oh man, that's a little involved. This should give you an idea of what to do. May not fit your setup but will point ya in the right direction. Also search these forums, I have seen some other posts with links talking about SSH.

A shortcut has to be a challenge, because if it was easy, then it would just be the way.

Long story short, I received my new router (WRT54GL) last night after sending back a (WRT54G) because I was not sure if it would handle the firmware upgrade that I needed to SSH.  Setup everything the way the http://hetos.de/sshtut.html website describes.  From the house I am able to get PuTTY to connect just fine but, from work I am getting "network error: connection refused" when trying to "Open" PuTTY.

IT'S ALIVE!!! As I said above, it was something simple that I was doing wrong. I was confused by some of the SSH post that I read. Originally I was putting the IP Address (127.0.0.1) and port (22) information in the Player>Slingplayer Options>Connection>Connection preferneces>Server Address and Port fields for HTTPS proxy(tunneling). WRONG!!! I unchecked the Player>Slingplayer Options>Connection>Connection preferneces "I use a proxy server to connect to the internet" checkbox. Then I checked the Slingbox>properties>Connection>Direct Connection checkbox", and entered the IP Address (127.0.0.1) and Port number(5001). I would personally like to thank "tbone_razor" for this suggestion. I always like a callenge and this was a big one for me. I won all the way around with this suggestion... New router and I can close all but one port allowing for more security. Not to mention the encryption that SSH uses for the data being sent and received.

Got this error today on my first try of setting up slingbox remote.  (Slingbox is located at home location behind a linksys router & testing slingbox player from a corporate network with a not overly restrictive corporate firewall in place.)  Looked at zonealarm, security settings, corporate firewall settings, anti-virus, windows defender, etc but nothing stopped the error.  Fixing the problem took two steps in our case:

1 - The automatic port forwarding configuration on the home slingbox & linksys did not check the option to allow remote connections so carefully double check your settings at home if you did the automatic configuration.

2 - Still got the error even after fixing that option.  I disabled the ip address/host address part of the remote forwarding on the slingbox player side and instead relied only on the Alias, Finder ID, and password.  Device connected great after that!

Also FYI:  Just wanted to mention that our slingbox did come with bad infrared cable.  Had to call slingbox and get them to send us a new cable.  (Quickest way: Use the digital camera test as suggested by slingbox to check this: Check the infrared flash on your remote and then check it on your cables - our cable didn't flash at all.  Don't forget to ensure you checked a remote infrared because tech support might try to say your digital camera is one that doesn't see infrared flashes.)