And some new level of screwy is going on. I just tried the Connectivity Test Tool (linked on page 1 of this discussion) via Firefox 4 and the test says it can't test my connection because I'm not on a supported browser... yet FF4 is allegedly supported: "Firefox3.5 or above." The connection test works in IE8.
Edit: I tried uninstalling and reinstalling FF4 but got the same result.
Sheesh. I'm turning in for the night.
I'd be worried that FF may be suffering from the problem from the Beta .. that it wasn't unpacking the files for the player until needed. (the supposed fix was to reinstall 3.6.x of FF, then install the plugins <adobe flash & slingplayer> then upgrade to FireFox 4)
Beyond that.. I noticed that you're not running the .117 version of the player in IE .. not that it would fix the issue, but you never know...
http://plugin.slingbox.com/downloads/msi/1.4.0.117/WBSP_IE_Setup.exe
Now as to the lastest log file.. I'm pretty sure the following lines are where the real error occurs.
Code:
00:00:04.737 00000C38 SBREQST : CSBMessageRequest BORN - 0AF41CF0
00:00:04.737 00000C38 SBDEVICE: --[SLING_MSG_SESSION_OPEN_SB]: usSessionId: 0 uiMsgCookie: 1 uibfLength: 200 uibfCtl : 2
00:00:34.740 00000C38 SBREQST : REQ_MESSAGE TIMEOUT : msg_type : 103
00:00:34.740 00000C38 SBDEVICE: Error occured for connectiontype: TCP, Error:0x92340011
00:00:34.750 00000C38 : slingbox_offline_hint : 0
00:00:34.750 000002B8 SPIMPL : CSlingPlayerImpl::OnDeviceNotification : code : 33
00:00:34.750 00000C38 SBDEVICE: ### CSBDevice::SignalClose: LAN - box : ; ip : ; port: 0; finder: [26363D3C3229223A3C2C3D3728333D1E]
00:00:34.780 000002B8 SBSERVIC: Device connect request completed...
00:00:34.780 000002B8 SBSERVIC: Request failed with Error Code: 92340011, (null)
00:00:34.780 000002B8 SBSERVIC: Service 6 failed with error 0x92340011
00:00:34.780 000002B8 : slingbox_offline_hint : 0
00:00:34.780 000002B8 : slingbox_offline_hint : 0
00:00:34.780 000002B8 SPIMPL : ANALYTICS: Analytics_HandledeviceOpenComplete
00:00:34.780 000002B8 : CSlingLogNetFormatter::GetDisconnectionLogData : Invaild xml data.
00:00:34.780 000002B8 SPIMPL : Box is online
00:00:34.780 000002B8 : CConnModeStatistics: 15ed90408X
00:00:34.780 000002B8 Firmware: CFirmwareInformation: 15ed4d408X
Notice the REQ_MESSAGE TIMEOUT ... it occured at 34.740 seconds in..... this is 30 seconds (the default TCP timeout) after an SBREQST or "SlingBox Request" at 4 seconds in...
04.737 00000C38 SBREQST : CSBMessageRequest BORN - 0AF41CF0
so it would seem a request went out .... but did not get answered.. once that happened the Error Code 92340011 was generated
Code:
[URL]http://slingbox.wikia.com/wiki/Slingplayer_Error_Codes[/URL]
([URL="http://slingbox.wikia.com/index.php?title=0x92340011&action=edit&redlink=1"][COLOR=#cc2200]0x92340011[/COLOR][/URL]) The operation failed because it was taking too long to finish.
and all subsequent errors are based off the same thing.. timeouts/unknown, etc..
I think the next thing I'd do, is setup the static DHCP entry for the 722k. Let me know what router it is and I'll see if I can find specifics. When I setup static DHCP entries I like to start from the top down ... getting the non-changing boxes (routers, switches, printers, receivers, etc) high up in the network, away from the normal PC range ... I usually start at 250 or 249, so like in my case the 722k is set to receive a lease for 192.168.1.247, I've other devices above that IP.
Once the IP is set and confirmed seen on the 722k ... I'd add an entry to the firewall (on the computer not the router/firewall) making all traffic trusted from the 722k's ip address. this bypasses the firewall in most respects, and if that clears up the problem, then that's probably been the trouble all along.
If not .. then we're back to looking for any logged messages (pc's firewall / windows event viewer, etc) looking for anything "dropped" or blocked.
(nappies for me now too-see ya)