Linksys BEFW11S4 V3.2 - No DHCP

Yesterday I purchased a BEFW11S4 v3.2 as part of a kit W11S4PC11 along with a WET11 from
my local retailer. I have since managed to set up my wireless network and successfully
bridge my two LANs via the BEFW11S4 on LAN A and the WET11 on LAN B. One problem I have
not been able to solve thus far is the DHCP feature on the LAN side of the BEFW11S4. No
matter what I do to configure it, no PCs (connected either wirelessly or wired) can get a
DHCP assigned IP address, mask, etc. and they all time out indicating that no DHCP server
is reachable. I have double checked my settings and networking config but I am unable to
find anything wrong. The BEFW11S4 V3.2 came with firmware 1.45 Feb 28 2003 straight out
of the box which is the latest according to the Linksys web site so no need to update
anything on it. The WET11 came with firmware 1.3.1 so I upgraded its firmware to 1.5.4
May 29 2003 and is working just fine to wirelessly bridge LAN B to LAN A. The PCMCIA
wireless B card WPC11 V4 which came in the kit is also using the latest drivers. Signal
strength is 100% and so is the quality.

wired - PC running 98SE and 10/100 Mbit PCI NIC
wireless via bridge - PC running XP Pro and laptop running Win2k Pro
wireless via WPC11 - laptop running Win2k Pro (same laptop as above)

BEFW11S4 DHCP settings
DHCP = enabled
starting IP address is .2 (router is .1)
# of DHCP users 10
client lease time = 10080 minutes (1 week)

All machines have the latest service packs, patches, etc. and work just fine with another
router with a built in DHCP server. Seeing how the BEFW11S4's DHCP server is rather
limited in its functionality and does not have address reservation via MAC capabilities,
it's not that big of a deal anyway since I'd rather have pre-determined known IPs instead
of random ones. But it still bugs me that it is a brand new unit and the DHCP does not
work. Has anybody else seen this before? Anything I missed? Thanks.

"Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in
news:AqnSa.570718$(E-Mail Removed):

> Yesterday I purchased a BEFW11S4 v3.2 as part of a kit W11S4PC11 along
> with a WET11 from my local retailer. I have since managed to set up
> my wireless network and successfully bridge my two LANs via the
> BEFW11S4 on LAN A and the WET11 on LAN B. One problem I have not been
> able to solve thus far is the DHCP feature on the LAN side of the
> BEFW11S4. No matter what I do to configure it, no PCs (connected
> either wirelessly or wired) can get a DHCP assigned IP address, mask,
> etc. and they all time out indicating that no DHCP server is
> reachable. I have double checked my settings and networking config
> but I am unable to find anything wrong. The BEFW11S4 V3.2 came with
> firmware 1.45 Feb 28 2003 straight out of the box which is the latest
> according to the Linksys web site so no need to update anything on it.
> The WET11 came with firmware 1.3.1 so I upgraded its firmware to
> 1.5.4 May 29 2003 and is working just fine to wirelessly bridge LAN B
> to LAN A. The PCMCIA wireless B card WPC11 V4 which came in the kit
> is also using the latest drivers. Signal strength is 100% and so is
> the quality.
>
> wired - PC running 98SE and 10/100 Mbit PCI NIC
> wireless via bridge - PC running XP Pro and laptop running Win2k Pro
> wireless via WPC11 - laptop running Win2k Pro (same laptop as above)
>
> BEFW11S4 DHCP settings
> DHCP = enabled
> starting IP address is .2 (router is .1)
> # of DHCP users 10
> client lease time = 10080 minutes (1 week)
>
> All machines have the latest service packs, patches, etc. and work
> just fine with another router with a built in DHCP server. Seeing how
> the BEFW11S4's DHCP server is rather limited in its functionality and
> does not have address reservation via MAC capabilities, it's not that
> big of a deal anyway since I'd rather have pre-determined known IPs
> instead of random ones. But it still bugs me that it is a brand new
> unit and the DHCP does not work. Has anybody else seen this before?
> Anything I missed? Thanks.
>
>
>

DHCP works perfectly on my 11S4 v1 router with NIC MAC tied IP. I suggest
you take the router back and get a replacement or contact Linksys for a
replacement.

Duane

--
The protection of the machine is a process and not a given!

Disable DHCP and try setting fixed IP's to see if everything works. Then
turn on DHCP. Check to see if still working with fixed IP's. Then set
individual NIC's to get IP automatically. Use IPConfig to check what's gong
on. Last resort, return it.

"Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
news:AqnSa.570718$(E-Mail Removed)...
> Yesterday I purchased a BEFW11S4 v3.2 as part of a kit W11S4PC11 along
with a WET11 from
> my local retailer. I have since managed to set up my wireless network and
successfully
> bridge my two LANs via the BEFW11S4 on LAN A and the WET11 on LAN B. One
problem I have
> not been able to solve thus far is the DHCP feature on the LAN side of the
BEFW11S4. No
> matter what I do to configure it, no PCs (connected either wirelessly or
wired) can get a
> DHCP assigned IP address, mask, etc. and they all time out indicating that
no DHCP server
> is reachable. I have double checked my settings and networking config but
I am unable to
> find anything wrong. The BEFW11S4 V3.2 came with firmware 1.45 Feb 28
2003 straight out
> of the box which is the latest according to the Linksys web site so no
need to update
> anything on it. The WET11 came with firmware 1.3.1 so I upgraded its
firmware to 1.5.4
> May 29 2003 and is working just fine to wirelessly bridge LAN B to LAN A.
The PCMCIA
> wireless B card WPC11 V4 which came in the kit is also using the latest
drivers. Signal
> strength is 100% and so is the quality.
>
> wired - PC running 98SE and 10/100 Mbit PCI NIC
> wireless via bridge - PC running XP Pro and laptop running Win2k Pro
> wireless via WPC11 - laptop running Win2k Pro (same laptop as above)
>
> BEFW11S4 DHCP settings
> DHCP = enabled
> starting IP address is .2 (router is .1)
> # of DHCP users 10
> client lease time = 10080 minutes (1 week)
>
> All machines have the latest service packs, patches, etc. and work just
fine with another
> router with a built in DHCP server. Seeing how the BEFW11S4's DHCP server
is rather
> limited in its functionality and does not have address reservation via MAC
capabilities,
> it's not that big of a deal anyway since I'd rather have pre-determined
known IPs instead
> of random ones. But it still bugs me that it is a brand new unit and the
DHCP does not
> work. Has anybody else seen this before? Anything I missed? Thanks.
>
>

Been there, done that, still the same problem exists. Going to try a hard reset and then
perhaps a re-flash. Then if it still does not work, going bring it back.

"John" <(E-Mail Removed)> wrote in message news:3f1960ac_4@newsfeed...
> Disable DHCP and try setting fixed IP's to see if everything works. Then
> turn on DHCP. Check to see if still working with fixed IP's. Then set
> individual NIC's to get IP automatically. Use IPConfig to check what's gong
> on. Last resort, return it.
>
> "Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
> news:AqnSa.570718$(E-Mail Removed)...
> > Yesterday I purchased a BEFW11S4 v3.2 as part of a kit W11S4PC11 along
> with a WET11 from
> > my local retailer. I have since managed to set up my wireless network and
> successfully
> > bridge my two LANs via the BEFW11S4 on LAN A and the WET11 on LAN B. One
> problem I have
> > not been able to solve thus far is the DHCP feature on the LAN side of the
> BEFW11S4. No
> > matter what I do to configure it, no PCs (connected either wirelessly or
> wired) can get a
> > DHCP assigned IP address, mask, etc. and they all time out indicating that
> no DHCP server
> > is reachable. I have double checked my settings and networking config but
> I am unable to
> > find anything wrong. The BEFW11S4 V3.2 came with firmware 1.45 Feb 28
> 2003 straight out
> > of the box which is the latest according to the Linksys web site so no
> need to update
> > anything on it. The WET11 came with firmware 1.3.1 so I upgraded its
> firmware to 1.5.4
> > May 29 2003 and is working just fine to wirelessly bridge LAN B to LAN A.
> The PCMCIA
> > wireless B card WPC11 V4 which came in the kit is also using the latest
> drivers. Signal
> > strength is 100% and so is the quality.
> >
> > wired - PC running 98SE and 10/100 Mbit PCI NIC
> > wireless via bridge - PC running XP Pro and laptop running Win2k Pro
> > wireless via WPC11 - laptop running Win2k Pro (same laptop as above)
> >
> > BEFW11S4 DHCP settings
> > DHCP = enabled
> > starting IP address is .2 (router is .1)
> > # of DHCP users 10
> > client lease time = 10080 minutes (1 week)
> >
> > All machines have the latest service packs, patches, etc. and work just
> fine with another
> > router with a built in DHCP server. Seeing how the BEFW11S4's DHCP server
> is rather
> > limited in its functionality and does not have address reservation via MAC
> capabilities,
> > it's not that big of a deal anyway since I'd rather have pre-determined
> known IPs instead
> > of random ones. But it still bugs me that it is a brand new unit and the
> DHCP does not
> > work. Has anybody else seen this before? Anything I missed? Thanks.
> >
> >
>
>

Well 2 hours later this morning I managed to narrow down the problem to a setting I made
in the router. I did a hard reset followed by a load of setup defaults which restored the
unit to a virgin or new state. The DHCP server works! I then changed 1 setting at a time
and tried the DHCP server to see at what point the DHCP server stops. Finally determined
it was after I changed the working mode of the router from gateway to router that the DHCP
server stopped. I then performed another hard reset and the DHCP server worked once
again. Then I left all settings at their defaults and jumped right to this page and
changed just the working mode once again. Voila! DHCP server stops. Change it back and
DHCP works again. I downloaded the latest firmware and reflashed but it never changed
anything - still the same problem. I double checked my documentation and there is no
mention of this, i.e. does not say anything about the DHCP not working in you use router
mode. Guess I found another bug in their firmware. Any PC with a static IP can connect
to the unit just fine and see the other LAN, Internet, etc. Now what to do...

"Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
newsEySa.612156$(E-Mail Removed)...
> Been there, done that, still the same problem exists. Going to try a hard reset and
then
> perhaps a re-flash. Then if it still does not work, going bring it back.
>
> "John" <(E-Mail Removed)> wrote in message news:3f1960ac_4@newsfeed...
> > Disable DHCP and try setting fixed IP's to see if everything works. Then
> > turn on DHCP. Check to see if still working with fixed IP's. Then set
> > individual NIC's to get IP automatically. Use IPConfig to check what's gong
> > on. Last resort, return it.
> >
> > "Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
> > news:AqnSa.570718$(E-Mail Removed)...
> > > Yesterday I purchased a BEFW11S4 v3.2 as part of a kit W11S4PC11 along
> > with a WET11 from
> > > my local retailer. I have since managed to set up my wireless network and
> > successfully
> > > bridge my two LANs via the BEFW11S4 on LAN A and the WET11 on LAN B. One
> > problem I have
> > > not been able to solve thus far is the DHCP feature on the LAN side of the
> > BEFW11S4. No
> > > matter what I do to configure it, no PCs (connected either wirelessly or
> > wired) can get a
> > > DHCP assigned IP address, mask, etc. and they all time out indicating that
> > no DHCP server
> > > is reachable. I have double checked my settings and networking config but
> > I am unable to
> > > find anything wrong. The BEFW11S4 V3.2 came with firmware 1.45 Feb 28
> > 2003 straight out
> > > of the box which is the latest according to the Linksys web site so no
> > need to update
> > > anything on it. The WET11 came with firmware 1.3.1 so I upgraded its
> > firmware to 1.5.4
> > > May 29 2003 and is working just fine to wirelessly bridge LAN B to LAN A.
> > The PCMCIA
> > > wireless B card WPC11 V4 which came in the kit is also using the latest
> > drivers. Signal
> > > strength is 100% and so is the quality.
> > >
> > > wired - PC running 98SE and 10/100 Mbit PCI NIC
> > > wireless via bridge - PC running XP Pro and laptop running Win2k Pro
> > > wireless via WPC11 - laptop running Win2k Pro (same laptop as above)
> > >
> > > BEFW11S4 DHCP settings
> > > DHCP = enabled
> > > starting IP address is .2 (router is .1)
> > > # of DHCP users 10
> > > client lease time = 10080 minutes (1 week)
> > >
> > > All machines have the latest service packs, patches, etc. and work just
> > fine with another
> > > router with a built in DHCP server. Seeing how the BEFW11S4's DHCP server
> > is rather
> > > limited in its functionality and does not have address reservation via MAC
> > capabilities,
> > > it's not that big of a deal anyway since I'd rather have pre-determined
> > known IPs instead
> > > of random ones. But it still bugs me that it is a brand new unit and the
> > DHCP does not
> > > work. Has anybody else seen this before? Anything I missed? Thanks.
> > >
> > >
> >
> >
>
>

The manual does mention something about loosing DHCP when you have port
forwarding.

"Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
news:GoBSa.621723$(E-Mail Removed)...
> Well 2 hours later this morning I managed to narrow down the problem to a
setting I made
> in the router. I did a hard reset followed by a load of setup defaults
which restored the
> unit to a virgin or new state. The DHCP server works! I then changed 1
setting at a time
> and tried the DHCP server to see at what point the DHCP server stops.
Finally determined
> it was after I changed the working mode of the router from gateway to
router that the DHCP
> server stopped. I then performed another hard reset and the DHCP server
worked once
> again. Then I left all settings at their defaults and jumped right to
this page and
> changed just the working mode once again. Voila! DHCP server stops.
Change it back and
> DHCP works again. I downloaded the latest firmware and reflashed but it
never changed
> anything - still the same problem. I double checked my documentation and
there is no
> mention of this, i.e. does not say anything about the DHCP not working in
you use router
> mode. Guess I found another bug in their firmware. Any PC with a static
IP can connect
> to the unit just fine and see the other LAN, Internet, etc. Now what to
do...
>
> "Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
> newsEySa.612156$(E-Mail Removed)...
> > Been there, done that, still the same problem exists. Going to try a
hard reset and
> then
> > perhaps a re-flash. Then if it still does not work, going bring it
back.
> >
> > "John" <(E-Mail Removed)> wrote in message news:3f1960ac_4@newsfeed...
> > > Disable DHCP and try setting fixed IP's to see if everything works.
Then
> > > turn on DHCP. Check to see if still working with fixed IP's. Then set
> > > individual NIC's to get IP automatically. Use IPConfig to check what's
gong
> > > on. Last resort, return it.
> > >
> > > "Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in
message
> > > news:AqnSa.570718$(E-Mail Removed)...
> > > > Yesterday I purchased a BEFW11S4 v3.2 as part of a kit W11S4PC11
along
> > > with a WET11 from
> > > > my local retailer. I have since managed to set up my wireless
network and
> > > successfully
> > > > bridge my two LANs via the BEFW11S4 on LAN A and the WET11 on LAN B.
One
> > > problem I have
> > > > not been able to solve thus far is the DHCP feature on the LAN side
of the
> > > BEFW11S4. No
> > > > matter what I do to configure it, no PCs (connected either
wirelessly or
> > > wired) can get a
> > > > DHCP assigned IP address, mask, etc. and they all time out
indicating that
> > > no DHCP server
> > > > is reachable. I have double checked my settings and networking
config but
> > > I am unable to
> > > > find anything wrong. The BEFW11S4 V3.2 came with firmware 1.45 Feb
28
> > > 2003 straight out
> > > > of the box which is the latest according to the Linksys web site so
no
> > > need to update
> > > > anything on it. The WET11 came with firmware 1.3.1 so I upgraded
its
> > > firmware to 1.5.4
> > > > May 29 2003 and is working just fine to wirelessly bridge LAN B to
LAN A.
> > > The PCMCIA
> > > > wireless B card WPC11 V4 which came in the kit is also using the
latest
> > > drivers. Signal
> > > > strength is 100% and so is the quality.
> > > >
> > > > wired - PC running 98SE and 10/100 Mbit PCI NIC
> > > > wireless via bridge - PC running XP Pro and laptop running Win2k Pro
> > > > wireless via WPC11 - laptop running Win2k Pro (same laptop as above)
> > > >
> > > > BEFW11S4 DHCP settings
> > > > DHCP = enabled
> > > > starting IP address is .2 (router is .1)
> > > > # of DHCP users 10
> > > > client lease time = 10080 minutes (1 week)
> > > >
> > > > All machines have the latest service packs, patches, etc. and work
just
> > > fine with another
> > > > router with a built in DHCP server. Seeing how the BEFW11S4's DHCP
server
> > > is rather
> > > > limited in its functionality and does not have address reservation
via MAC
> > > capabilities,
> > > > it's not that big of a deal anyway since I'd rather have
pre-determined
> > > known IPs instead
> > > > of random ones. But it still bugs me that it is a brand new unit
and the
> > > DHCP does not
> > > > work. Has anybody else seen this before? Anything I missed?
Thanks.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

From what I have read in the manual, you should disable the DHCP on the PC to which you
want to forward traffic. That only makes sense given that the DHCP server in this
BEFW11S4 does not have the ability to reserve IP addresses based on the MAC address so
unless you only have 1 PC accessing the BEFW11S4 for DHCP, the IP address of the PC you
want to forward traffic to is somewhat uncertain and you may end up forwarding to the
wrong PC. That does not say/mean that the BEFW11S4's DHCP server will stop functioning if
port forwarding is used, its just a warning of a possible error condition.

I've used the Adobe Acrobat Reader to search through the entire PDF for "DHCP" and I was
unable to find any mention of this DHCP disabling side affect. I've also tried the
Linksys web site without any luck.


"neo" <(E-Mail Removed)> wrote in message
news:WrBSa.9148$(E-Mail Removed)...
> The manual does mention something about loosing DHCP when you have port
> forwarding.
>
> "Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
> news:GoBSa.621723$(E-Mail Removed)...
> > Well 2 hours later this morning I managed to narrow down the problem to a
> setting I made
> > in the router. I did a hard reset followed by a load of setup defaults
> which restored the
> > unit to a virgin or new state. The DHCP server works! I then changed 1
> setting at a time
> > and tried the DHCP server to see at what point the DHCP server stops.
> Finally determined
> > it was after I changed the working mode of the router from gateway to
> router that the DHCP
> > server stopped. I then performed another hard reset and the DHCP server
> worked once
> > again. Then I left all settings at their defaults and jumped right to
> this page and
> > changed just the working mode once again. Voila! DHCP server stops.
> Change it back and
> > DHCP works again. I downloaded the latest firmware and reflashed but it
> never changed
> > anything - still the same problem. I double checked my documentation and
> there is no
> > mention of this, i.e. does not say anything about the DHCP not working in
> you use router
> > mode. Guess I found another bug in their firmware. Any PC with a static
> IP can connect
> > to the unit just fine and see the other LAN, Internet, etc. Now what to
> do...
> >
> > "Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in message
> > newsEySa.612156$(E-Mail Removed)...
> > > Been there, done that, still the same problem exists. Going to try a
> hard reset and
> > then
> > > perhaps a re-flash. Then if it still does not work, going bring it
> back.
> > >
> > > "John" <(E-Mail Removed)> wrote in message news:3f1960ac_4@newsfeed...
> > > > Disable DHCP and try setting fixed IP's to see if everything works.
> Then
> > > > turn on DHCP. Check to see if still working with fixed IP's. Then set
> > > > individual NIC's to get IP automatically. Use IPConfig to check what's
> gong
> > > > on. Last resort, return it.
> > > >
> > > > "Press Ctrl-Alt-Del Now" <(E-Mail Removed)> wrote in
> message
> > > > news:AqnSa.570718$(E-Mail Removed)...
> > > > > Yesterday I purchased a BEFW11S4 v3.2 as part of a kit W11S4PC11
> along
> > > > with a WET11 from
> > > > > my local retailer. I have since managed to set up my wireless
> network and
> > > > successfully
> > > > > bridge my two LANs via the BEFW11S4 on LAN A and the WET11 on LAN B.
> One
> > > > problem I have
> > > > > not been able to solve thus far is the DHCP feature on the LAN side
> of the
> > > > BEFW11S4. No
> > > > > matter what I do to configure it, no PCs (connected either
> wirelessly or
> > > > wired) can get a
> > > > > DHCP assigned IP address, mask, etc. and they all time out
> indicating that
> > > > no DHCP server
> > > > > is reachable. I have double checked my settings and networking
> config but
> > > > I am unable to
> > > > > find anything wrong. The BEFW11S4 V3.2 came with firmware 1.45 Feb
> 28
> > > > 2003 straight out
> > > > > of the box which is the latest according to the Linksys web site so
> no
> > > > need to update
> > > > > anything on it. The WET11 came with firmware 1.3.1 so I upgraded
> its
> > > > firmware to 1.5.4
> > > > > May 29 2003 and is working just fine to wirelessly bridge LAN B to
> LAN A.
> > > > The PCMCIA
> > > > > wireless B card WPC11 V4 which came in the kit is also using the
> latest
> > > > drivers. Signal
> > > > > strength is 100% and so is the quality.
> > > > >
> > > > > wired - PC running 98SE and 10/100 Mbit PCI NIC
> > > > > wireless via bridge - PC running XP Pro and laptop running Win2k Pro
> > > > > wireless via WPC11 - laptop running Win2k Pro (same laptop as above)
> > > > >
> > > > > BEFW11S4 DHCP settings
> > > > > DHCP = enabled
> > > > > starting IP address is .2 (router is .1)
> > > > > # of DHCP users 10
> > > > > client lease time = 10080 minutes (1 week)
> > > > >
> > > > > All machines have the latest service packs, patches, etc. and work
> just
> > > > fine with another
> > > > > router with a built in DHCP server. Seeing how the BEFW11S4's DHCP
> server
> > > > is rather
> > > > > limited in its functionality and does not have address reservation
> via MAC
> > > > capabilities,
> > > > > it's not that big of a deal anyway since I'd rather have
> pre-determined
> > > > known IPs instead
> > > > > of random ones. But it still bugs me that it is a brand new unit
> and the
> > > > DHCP does not
> > > > > work. Has anybody else seen this before? Anything I missed?
> Thanks.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>

Why do you wnat to use router mode?

wk

Press Ctrl-Alt-Del Now wrote:
>
> Well 2 hours later this morning I managed to narrow down the problem to a setting I made
> in the router. I did a hard reset followed by a load of setup defaults which restored the
> unit to a virgin or new state. The DHCP server works! I then changed 1 setting at a time
> and tried the DHCP server to see at what point the DHCP server stops. Finally determined
> it was after I changed the working mode of the router from gateway to router that the DHCP
> server stopped. I then performed another hard reset and the DHCP server worked once
> again. Then I left all settings at their defaults and jumped right to this page and
> changed just the working mode once again. Voila! DHCP server stops. Change it back and
> DHCP works again. I downloaded the latest firmware and reflashed but it never changed
> anything - still the same problem. I double checked my documentation and there is no
> mention of this, i.e. does not say anything about the DHCP not working in you use router
> mode. Guess I found another bug in their firmware. Any PC with a static IP can connect
> to the unit just fine and see the other LAN, Internet, etc. Now what to do...
>
[SNIP]

Press Ctrl-Alt-Del Now wrote:
>
> To join 2 LANs and the other LAN already has a router on it with better specs and
> performance. I've tried to use the BEFW11S4 as just an access point but that had mixed
> results. It is solid (so far, knocking on wood...) when used in this (router) mode but
> the DHCP server stops working. Damn, never an easy solution...

That last comment I can relate to. I used my BEFW11S4 V1 as an access point only
until newer firmware fixed the PPPoE. Now I use it as a wireless NAT/router,
but it's still kind of flakey if I change anything. When I change any settings
it sometimes loses others. Good and solid though if I leave it alone once I have
it working. I've never tried router mode though.

wk

>
> "wk" <wk-(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> > Why do you wnat to use router mode?
> >
> > wk
> >
[SNIP]