Bugzilla – Bug 1431
SB1s constantly lose contact with server
Last modified: 2007-10-22 16:34:30 UTC
About once every 24 hours--but not at a specfic time of day--one of my SB1s (wireless) will lose contact with the server and not recover until I reset the client. I can see these SB1s via the web interface. Clicking on or off on the web interface doesn't recover. My third device, a wireless SB2, never seems to lose contact.
Phillip: what's on the display of the SB1? Can you reset the player with the remote control (press and hold POWER for 5 seconds?) Also, what access point are you using with your player?
I hope I'm making my comments in the correct area. Anyway, on my display it's 100% blank. I can click and hold to reset it. Naturally, this is less than ideal. It definitely seems to coincide with the 6.x version of the server; or the fact I have 3 wireless boxes (instead of 1 wireless and 1 wired which was the case before I got an SB2 and upgraded the server). I have a Linksys BEFW11S4 Firmware Version: 1.50.14
I have exactly the same problem with my SB1. Its the wireless model, but currently connected via Ethernet to my Netgem DG834G router. Meanwhile, my SB2 (connected via wireless to the same router) stays connected with no problems. Therefore I assume that: 1) The problem is not specific to the router 2) The problem only affects SB1 (and not SB2) 3) The problem occurs for both wired and wireless connections The symptoms are as follows: - Screen goes blank - Pressing the cursor keys on the remote brings up "lost contact with server" message on screen - The only way to regain contact is to reset by holding down Power key for 5 seconds Hope this helps, Chris
Chris & Philip: Are you both using Windows XP?
I'm on XP, yes.
Philip: one more question- does this problem happen if you are connected d via ethernet? I want to know if this is related to bug 969?
I can't really say if it happens via ethernet because I don't have any boxes hooked up this way. Back when one of my two SB1s was connected that way, I don't think this ever happened--but that was version 5.4x.
Also, that other bug sounds like the SB resets itself. My bug it definitely doesn't go through that sequence but rather it just gets disconnected.
I've got a somewhat similar situation with an SB1. I was running it wired with no problems, then replaced it with an SB2 on the wired connection which is running fine. In trying to configure the SB1 to run wireless, it sees the SSID, gets a DHCP address from my router (not part of the AP), finds the Slimserver, then goes blank. Hitting a key on the remote has either brought up "Can't connect to wireless network" or "Lost contact with server" depending on I don't know what. Symptoms are the same if I manually configure an IP address in the SB1. I can reliably ping the SB1 from my server machine. Server is running Win XP SP 2 (Win firewall is off), Slimserver 6.0.2, Belkin F5D7230 AP (Mac laptop and various other gadgets are connecting fine) with latest load (4.03.03), 128 bit WEP, no address filtering on AP, router/switch is Linksys BEFSX41. Let me know if you want a separate bug filed.
Ignore my comment above. User error in not reconfiguring slimserver security settings.
does the BEFW11S4 have an option for automatic channel switching? I had to set my Pre-N to a specific channel becuase the channel switching in automatic mode seemed to leave the clients lost.
I'm seeing similar behavior with my wired SB1. It worked flawlessly wired, but now I'm running it through a wireless bridge and about every day, the screen is blank. I can hold down the power button to reset the box, and it reconnects and all is well. I assumed this was some flakiness with the bridge but given the reports in this bug, maybe not? And even so, it'd be nice if the SB could recover gracefully.
Any thoughts on this? I'm still seeing a blank screen a lot, requiring a manual reboot. Bummer.
Can't reproduce this here. Please reopen if it happens with 7.0.
I actually drilled a hole in my living room floor and ran cat5 between floors as a bug workaround. :) So I won't be able to follow up for future versions.