Bugzilla – Bug 1219
DHCP client woes with BEFSR41
Last modified: 2005-07-27 15:36:29 UTC
I had my SB2 connected via ethernet to one router/DHCP server, and it was working fine. I moved it to another, and it seems to remember only the net address it was originally assigned. That is, it does not get an ip address from the new DHCP server, and it cannot connect to my slimserver. Details follow... Originally, the SB2 was connected to a netgear RP114. It was given an ip address beginning with 192.168.0... The second router is a Linksys BEFSR41. I plug into this router, and walk through the network setup. The DHCP steps takes a second, and it comes back with 192.168.0.10. But the router is assigning address that begin 192.168.1... So clearly the SB2 is confused. Other devices (a desktop, laptop, SB1 and VOIP phone) are all able to get IP address from the new server, and they all begin 192.168.1... Ok... just discovered something new. I power cycled the SB2, and now it fails to get an IP address at all. So its not finding the DHCP server at all. If I can learn any more I'll attach another comment.
More info... After the earlier failed attempt to connect to the DHCP server. I went to enter an ip address manually. Suprisingly, the SB2 had a default there of 192.168.1.14. This look suspiciously like it had been assigned by my dhcp server. So I suspect it had had been assigned the ip address after all, but somehow the network setup did not realize it. So I tried one more time, and it got the same ip address immediately. And from then on the setup went smoothly.
I've got a BEFSR11 (the one port version of the BEFSR41) here and it gets a DHCP address just fine. Dave: can you try to reproduce this with latest firmware on both the router and the player? if it still fails, can you grab a tcpdump of the DHCP transaction on your setup or loan vidur the router to reproduce?
spoke with a customer today who was having a smiilar issue with a netgear wgr614 and wired-only sb2. it would hang for the entire duration of trying to get an address via dhcp, and report that it didn't get one... but then afterwards i had him go through and specify a static IP and surprisingly it already had all of his network settings. can not reproduce (i have a wgr614v4 at home and it works fine)
would love a reproducible case.
ehh, should probably close until we can get a reproducable case and/or packet trace.
Closing unless we can reproduce.