Bug 551 - Server reconnect
: Server reconnect
Status: RESOLVED WORKSFORME
Product: SB 1
Classification: Unclassified
Component: Firmware
: 37
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Sean Adams
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-14 14:04 UTC by Stuart Beesley
Modified: 2009-09-08 09:28 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Beesley 2004-09-14 14:04:56 UTC
I turn my SlimServer PC off every night. Every morning, I start it up and my SB 
is showing "lost connection to the server". It won't reconnect. If I do a soft 
reboot on the SB then it connects fine. It seems that the SB stops trying to 
reconnect after an amount of time.
Comment 1 KDF 2004-09-20 10:09:53 UTC
do you use DHCP for assigning IP addresses on your network?  Could it be that
the lease is short enough that the PC reboots in the morning and gets a
different IP?
Comment 2 Stuart Beesley 2004-09-20 11:06:51 UTC
Nope - all IP addresses remain the same.
Comment 3 Stuart Beesley 2004-09-20 11:07:09 UTC
Nope - all IP addresses remain the same.
Comment 4 Blackketter Dean 2004-09-20 22:33:49 UTC
Please try the latest nightly release and let us know if this problem remains.
Comment 5 Stuart Beesley 2004-09-21 12:39:20 UTC
Tried latest release with V38 firmware. Same problem! I also just checked 
wheter after turning on my PC, I could ping the SB and it's not pingable. The 
PC IP number is the same. After rebooting the SB, I can ping it fine. It seems 
that after a certain amount of time not being able to reconnect, it looses 
interest and even the SB Network card drops the IP connection and it doesn't 
try to reconnect?
Comment 6 Stuart Beesley 2004-11-22 11:44:22 UTC
I still have this problem. I am now on V40 for Firmware and latest build. The 
SBG gives up retrying after several hours of the SS being off. Pressing & 
holding the red off button reboots it OK.
Comment 7 Stuart Beesley 2004-11-28 14:31:19 UTC
I have now changed my AP to a netgear and this issue has gone away.