Why is my BEFW11S4 assigning 192.168.1.36 to nodes? It won't work.

DHCP is supposed to start at 192.168.1.1. Every once in a while it wants to
assign a new connection (wired or wireless) to 192.168.1.36 and that
particular client doesn't seem to accept the address. It can't even see the
LAN.

If I reset the BEFW11S4 it has no effect, but if I unplug it for ten seconds
and then plug it in again all is normal and it starts assigning addresses as
it should. WEP is turned off and will remain that way until I figure out
how to enable it and still access my Netgear wireless print server -- but
that's for another day.

"TPFKAC.C" <(E-Mail Removed)> wrote in
news:bhrkbb$2ek3g$(E-Mail Removed):

> DHCP is supposed to start at 192.168.1.1. Every once in a while it
> wants to assign a new connection (wired or wireless) to 192.168.1.36
> and that particular client doesn't seem to accept the address. It
> can't even see the LAN.
>
> If I reset the BEFW11S4 it has no effect, but if I unplug it for ten
> seconds and then plug it in again all is normal and it starts
> assigning addresses as it should. WEP is turned off and will remain
> that way until I figure out how to enable it and still access my
> Netgear wireless print server -- but that's for another day.
>
>
>

192.168.1.1 is suppose to be the router's device address and not the
start of DHCP IP's. I am wondering how you are getting to the Admin page.

192.168.1.2-192.168.1.99 are suppose to be the router's programmable
static IP's.

192.168.1.100 should be the start of the router's DHCP IP's and is based
on how many DHCP IP's you have told the router it can issue.

If you set the number to 10, then the DHCP IP's that can be issued by the
router are 192.168.1.100-192.168.1.110. Those are programmable IP's too,
where as, you can go to the Admin screen like Port Forwarding and tell
the router to do something with the IP.

Duane

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

Wouldn't I see them on the client table? The poachers, I mean...


<(E-Mail Removed)> wrote in message
news:bhrlpj$l54$(E-Mail Removed)...
> TPFKAC.C <(E-Mail Removed)> wrote:
> > DHCP is supposed to start at 192.168.1.1. Every once in a while it
wants to
> > assign a new connection (wired or wireless) to 192.168.1.36 and that
> > particular client doesn't seem to accept the address. It can't even see
the
> > LAN.
>
> > If I reset the BEFW11S4 it has no effect, but if I unplug it for ten
seconds
> > and then plug it in again all is normal and it starts assigning
addresses as
> > it should. WEP is turned off and will remain that way until I figure
out
> > how to enable it and still access my Netgear wireless print server --
but
> > that's for another day.
>
> There's nothing wrong with 192.168.1.36. That should be a usable address.
> You could permanently assign an address to that one node, if it isn't
happy
> with the one that Linksys wants to give it. Oops, the BEFW11S4 doesn't
> have that option. You could just make the lease as long as possible.
Then
> once that node gets and address it likes, it will probably keep it.
>
> Maybe you have 30 neighbors poaching your wireless.
>
>
> --
> ---
> Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5

I misspoke. I do have 192.168.1.100 as the starting address. But I'm still
not sure why it tosses our 192.168.1.36 from time to time. It's especially
interesting that releasing and reassinging doesn't fix it, nor does
resetting the router. But if I unplug it for ten seconds, all seems fine.
This happens about every couple of weeks.


"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns93DBB69082A7Cnotmenotmecom@204.127.204.17. ..
> "TPFKAC.C" <(E-Mail Removed)> wrote in
> news:bhrkbb$2ek3g$(E-Mail Removed):
>
> > DHCP is supposed to start at 192.168.1.1. Every once in a while it
> > wants to assign a new connection (wired or wireless) to 192.168.1.36
> > and that particular client doesn't seem to accept the address. It
> > can't even see the LAN.
> >
> > If I reset the BEFW11S4 it has no effect, but if I unplug it for ten
> > seconds and then plug it in again all is normal and it starts
> > assigning addresses as it should. WEP is turned off and will remain
> > that way until I figure out how to enable it and still access my
> > Netgear wireless print server -- but that's for another day.
> >
> >
> >
>
> 192.168.1.1 is suppose to be the router's device address and not the
> start of DHCP IP's. I am wondering how you are getting to the Admin page.
>
> 192.168.1.2-192.168.1.99 are suppose to be the router's programmable
> static IP's.
>
> 192.168.1.100 should be the start of the router's DHCP IP's and is based
> on how many DHCP IP's you have told the router it can issue.
>
> If you set the number to 10, then the DHCP IP's that can be issued by the
> router are 192.168.1.100-192.168.1.110. Those are programmable IP's too,
> where as, you can go to the Admin screen like Port Forwarding and tell
> the router to do something with the IP.
>
> Duane
>
> --
> The protection of the machine is a process and not a given!

TPFKAC.C <(E-Mail Removed)> wrote:
> Wouldn't I see them on the client table? The poachers, I mean...

On my SMC, I'd only see them while they were connected.
That was one reason for an incrementing IP address coming out of the DHCP
pool, though.

Is this particular card used somewhere else, where it is 192.168.1.36?
I think the DHCP client will ask for the same IP address that it had
last time, not knowing that it is connected to a different switch.
The Linksys ought to reject it as not being in the assignable range, and
issue a different one, but maybe it's only checking to see if it's within
the proper subnet. I'd set the lease time a lot higher. The DHCP server
should reissue the same IP to the same MAC, if possible.

You could change your Linksys to some other subnet, like 192.168.4.xxx


> <(E-Mail Removed)> wrote in message
> news:bhrlpj$l54$(E-Mail Removed)...
>> TPFKAC.C <(E-Mail Removed)> wrote:
>> > DHCP is supposed to start at 192.168.1.1. Every once in a while it
> wants to
>> > assign a new connection (wired or wireless) to 192.168.1.36 and that
>> > particular client doesn't seem to accept the address. It can't even see
> the
>> > LAN.
>>
>> > If I reset the BEFW11S4 it has no effect, but if I unplug it for ten
> seconds
>> > and then plug it in again all is normal and it starts assigning
> addresses as
>> > it should. WEP is turned off and will remain that way until I figure
> out
>> > how to enable it and still access my Netgear wireless print server --
> but
>> > that's for another day.
>>
>> There's nothing wrong with 192.168.1.36. That should be a usable address.
>> You could permanently assign an address to that one node, if it isn't
> happy
>> with the one that Linksys wants to give it. Oops, the BEFW11S4 doesn't
>> have that option. You could just make the lease as long as possible.
> Then
>> once that node gets and address it likes, it will probably keep it.
>>
>> Maybe you have 30 neighbors poaching your wireless.
>>
>>
>> --
>> ---
>> Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5



--
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5