I am now getting this error too with beta version 2.0 It worked for a few days, but now it get this error. I have restarted the slingbox, and I removed reinstalled beta 2.0.

Anybody have any ideas?

I too am receiving error 0x80004004 using the Beta. It worked fine up until today...

Thanks for the reply...I got it fixed. It appeared that one of the Beta updates changed the port setting as I wasn't using 5001. Upon resetting my port assigment it worked again.

I wish Sling would allow a way to make changes to the box itself when I am on the road.

If using a Cisco ASA...

Create a "Static NAT" rule (Actually two, one for TCP the other for UDP)
- Orginal Interface is the Internal Network
- Source is the Slingbox IP Address
- Translated Interface is "outside" and "Use Interface IP Address"
- Use Port Address Translation (PAT) with 5001 as "Original" port and "Translated"
- You create two rules because you will need one for TCP PAT and the other for UDP PAT.

static (DMZ,outside) udp interface 5001 192.168.1.254 5001 netmask 255.255.255.255 tcp 0 0 udp 0

Ensure you have the proper Access Rules as well...
- on the outside interface create a rule to Permit "any" from the "source", Destination should be the "outside" interface, TCP/UDP 5001 for the service.

Seems backwards, but that is how Cisco does it.

Any idea how to get around this with a NetGear WGT-624 router? I am running the same version of Sling Player on a Pro-HD. Streaming stopped yesterday and then restarted when I had my son go through the set up again. Of course, now I can not watch the end of the playoff game from London.

Ok I got mine fixed. What it was: Firewall software (Windows Live OneCare) was not recognizing the current version of Slingbox. I too had thought I'd disabled everything by going into software - turning firewall off, right clicking on software shutting it down.... But this Windows Live OneCare kept running (Taskmanager). I found the problem by actually uninstalling the whole Onecare package and then it worked again! Then I re-installed Windows Live One care and it worked fine. Now, this is a really ridiculous way to fix this, but remember I was in a debugging mode just trying to find the root cause.... what this tells me though is that Windows Live OneCare must run in the background to some extent and had the wrong signature version of the Slingbox software. So, at somepoint after Windows Live OneCare was put on the machine, Slingbox was updated so the 'Allowed' version of slingbox was no longer allowed ;o). So make sure your firewall software allows the version of the slingbox that you have. I'm new to this onecare package so I can't give you specifics - I actually use McAffee and this was a problem on my daughters and husbands machines but it fixed both..... I can see versions of software in McAffee.....

Just remember Version signatures of software do matter. You were right to eliminate all the more probable reasons first though - like port forwarding and connectivity (make sure you can ping the port...). Hope this helps.