wireless clients can't get IP's

I've got a wireless router connected to my LAN/WAN router. It has a static
IP from the ISP. It is set in AP mode and acts as a DHCP server. It's IP
is 192.168.0.1 and it hands out 192.168.0.100-255. I have 2 AP's with
reserved IP's in the building patched with CAT5 to the wireless router. The
encryption I set is WPA2-Personal and channel is 6 for all. Same SSID for
all. Same netowkr key for all.

Clients can easily detect the AP's and make an apparent connection, but they
aren't getting the IP's. A typical entry in the LAN/WAN router Status Log
looks like this:
2008/03/12 00:49:21 : duplicate IP address 4514c91c!! sent from ethernet
address: 00:15:e9:69:26:93
[the MAC is the WAN port of the wireless router]

But my wireless router's log this afternoon showed IP's being handed out to
the laptops. I recognized several laptop names. However, on the DHCP
client page, none were listed.

The LAN/WAN router is connected to Small Business Server (SBS) 2003 Premium
SP2 (with 2 NIC's), and it acts as the DHCP server for my LAN. Nothing in
it's Event logs, and nothing in my firewall logs (ISA 2004 SP2, which is a
software firewall on the server).

What am I missing???

Mike

Mike Webb wrote:
> I've got a wireless router connected to my LAN/WAN router. It has a static
> IP from the ISP. It is set in AP mode and acts as a DHCP server. It's IP
> is 192.168.0.1 and it hands out 192.168.0.100-255. I have 2 AP's with
> reserved IP's in the building patched with CAT5 to the wireless router. The
> encryption I set is WPA2-Personal and channel is 6 for all. Same SSID for
> all. Same netowkr key for all.
>
> Clients can easily detect the AP's and make an apparent connection, but they
> aren't getting the IP's. A typical entry in the LAN/WAN router Status Log
> looks like this:
> 2008/03/12 00:49:21 : duplicate IP address 4514c91c!! sent from ethernet
> address: 00:15:e9:69:26:93
> [the MAC is the WAN port of the wireless router]
>
> But my wireless router's log this afternoon showed IP's being handed out to
> the laptops. I recognized several laptop names. However, on the DHCP
> client page, none were listed.
>
> The LAN/WAN router is connected to Small Business Server (SBS) 2003 Premium
> SP2 (with 2 NIC's), and it acts as the DHCP server for my LAN. Nothing in
> it's Event logs, and nothing in my firewall logs (ISA 2004 SP2, which is a
> software firewall on the server).
>
> What am I missing???
>
> Mike
>
>

It sounds as if you may have too many DHCP servers: one on the LAN/WAN
router and one on the wireless router. Do you intend to have the
wireless clients on a different subnet than the ones cabled to the
WAN/LAN router? Do the wireless clients get APIPA addresses or
192.168.x.y type addresses? Do clients behave the same whether they are
in range of the wireless router or of one of the other two APs?

Assuming that you did want a NAT between your cabled LAN and your
wireless LAN, as a long shot, are you positive that when "in AP mode"
your wireless router's DHCP server is active? Some stand-alone wireless
APs have no DHCP server, so perhaps if you're using a device that can be
set to AP mode, that mode disables DHCP.

OTOH, not *all* stand-alone wireless APs lack a DHCP server. Check to
make sure that yours don't or if they do, it's turned off.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

I'd like to keep both DHCP servers going. They handle different networks
(192.168.16.x and 192.168.0.x). And my DHCP address pool was wrong, should
be .100-.199.

"smlunatick" <(E-Mail Removed)> wrote in message
news:1581e554-6892-4857-b4d8-(E-Mail Removed)...


You seem to have two DHCP systems assigning IP address which will
cause problem. You need to set one DHCP service only, unless the
second DHCP is giving out different IP address range (ex
192.168.1.xxx)

BTW: It seem that the IP address 192.168.0.255 is a "reserved"
address for the IP network "broadcast" controls.

I'd like to use both as eahc handles a separate network - and I'd really
like to keep any guests/visitors out of my LAN.
I don't know what an APIPA address is, I am having my wireless router
handout addresses from 192.168.0.100-.199.
The clients behave the same, regardless of what AP they're near.
I know what NAT stands for, but don't really know what it is.
Am not absulutely positive the router is handing out IP's, but I have it set
to do so. Followed the manual and triple-checked the settings.

Mike
"Lem" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> It sounds as if you may have too many DHCP servers: one on the LAN/WAN
> router and one on the wireless router. Do you intend to have the wireless
> clients on a different subnet than the ones cabled to the WAN/LAN router?
> Do the wireless clients get APIPA addresses or 192.168.x.y type addresses?
> Do clients behave the same whether they are in range of the wireless
> router or of one of the other two APs?
>
> Assuming that you did want a NAT between your cabled LAN and your wireless
> LAN, as a long shot, are you positive that when "in AP mode" your wireless
> router's DHCP server is active? Some stand-alone wireless APs have no
> DHCP server, so perhaps if you're using a device that can be set to AP
> mode, that mode disables DHCP.
>
> OTOH, not *all* stand-alone wireless APs lack a DHCP server. Check to
> make sure that yours don't or if they do, it's turned off.
>
> --
> Lem -- MS-MVP
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm

Mike Webb wrote:
> I'd like to use both as eahc handles a separate network - and I'd really
> like to keep any guests/visitors out of my LAN.
> I don't know what an APIPA address is, I am having my wireless router
> handout addresses from 192.168.0.100-.199.
> The clients behave the same, regardless of what AP they're near.
> I know what NAT stands for, but don't really know what it is.
> Am not absulutely positive the router is handing out IP's, but I have it set
> to do so. Followed the manual and triple-checked the settings.
>
> Mike
> "Lem" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> It sounds as if you may have too many DHCP servers: one on the LAN/WAN
>> router and one on the wireless router. Do you intend to have the wireless
>> clients on a different subnet than the ones cabled to the WAN/LAN router?
>> Do the wireless clients get APIPA addresses or 192.168.x.y type addresses?
>> Do clients behave the same whether they are in range of the wireless
>> router or of one of the other two APs?
>>
>> Assuming that you did want a NAT between your cabled LAN and your wireless
>> LAN, as a long shot, are you positive that when "in AP mode" your wireless
>> router's DHCP server is active? Some stand-alone wireless APs have no
>> DHCP server, so perhaps if you're using a device that can be set to AP
>> mode, that mode disables DHCP.
>>
>> OTOH, not *all* stand-alone wireless APs lack a DHCP server. Check to
>> make sure that yours don't or if they do, it's turned off.
>>
>> --
>> Lem -- MS-MVP
>>
>> To the moon and back with 2K words of RAM and 36K words of ROM.
>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>> http://history.nasa.gov/afj/compessay.htm
>
>

APIPA means "Automatic Private IP Addressing" and is what Windows
defaults to if a NIC is configured to get an address from a DHCP server
but no server is found. These addresses are in the range 169.254.0.1 to
169.254.255.254. Do an ipconfig /all from a command prompt on a couple
of the wireless clients (both next to the wireless router and next to
one of the APs). If they have IP addresses of the form 169.254.x.y,
they are not seeing any DHCP server.

NAT means Network Address Translation, and is used in a router to
translate IP addresses between two separate networks (such as the
Internet and a LAN or between 2 local networks that use different
subnets). If you want your wireless clients to have addresses in the
range 192.168.0.100-.199 and you want your wired clients to be separate
(which you do), you probably have your LAN/WAN router set to hand out
addresses in a different range, such as 192.168.1.100 - 199 (the
difference is the 3rd octet).

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

Thanks for the info. They DO get 169.x.x.x's. And the LAN/WAN router
doesn't handle the LAN DHCP; my server does (Small Business Server (SBS)
2003 Premium SP2). Kind of an extra puzzler as it's one 'device' removed
from the wireless router.

"Lem" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> APIPA means "Automatic Private IP Addressing" and is what Windows defaults
> to if a NIC is configured to get an address from a DHCP server but no
> server is found. These addresses are in the range 169.254.0.1 to
> 169.254.255.254. Do an ipconfig /all from a command prompt on a couple of
> the wireless clients (both next to the wireless router and next to one of
> the APs). If they have IP addresses of the form 169.254.x.y, they are not
> seeing any DHCP server.
>
> NAT means Network Address Translation, and is used in a router to
> translate IP addresses between two separate networks (such as the Internet
> and a LAN or between 2 local networks that use different subnets). If you
> want your wireless clients to have addresses in the range
> 192.168.0.100-.199 and you want your wired clients to be separate (which
> you do), you probably have your LAN/WAN router set to hand out addresses
> in a different range, such as 192.168.1.100 - 199 (the difference is the
> 3rd octet).
>
> --
> Lem -- MS-MVP
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm

Mike Webb wrote:
> Thanks for the info. They DO get 169.x.x.x's. And the LAN/WAN router
> doesn't handle the LAN DHCP; my server does (Small Business Server (SBS)
> 2003 Premium SP2). Kind of an extra puzzler as it's one 'device' removed
> from the wireless router.
>
> "Lem" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> APIPA means "Automatic Private IP Addressing" and is what Windows defaults
>> to if a NIC is configured to get an address from a DHCP server but no
>> server is found. These addresses are in the range 169.254.0.1 to
>> 169.254.255.254. Do an ipconfig /all from a command prompt on a couple of
>> the wireless clients (both next to the wireless router and next to one of
>> the APs). If they have IP addresses of the form 169.254.x.y, they are not
>> seeing any DHCP server.
>>
>> NAT means Network Address Translation, and is used in a router to
>> translate IP addresses between two separate networks (such as the Internet
>> and a LAN or between 2 local networks that use different subnets). If you
>> want your wireless clients to have addresses in the range
>> 192.168.0.100-.199 and you want your wired clients to be separate (which
>> you do), you probably have your LAN/WAN router set to hand out addresses
>> in a different range, such as 192.168.1.100 - 199 (the difference is the
>> 3rd octet).
>>
>> --
>> Lem -- MS-MVP
>>
>> To the moon and back with 2K words of RAM and 36K words of ROM.
>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>> http://history.nasa.gov/afj/compessay.htm
>
>

It sound's as if the wireless router's DHCP server isn't working. If
it's a typical SOHO wireless router and has several LAN ports on it, try
connecting a client computer to one of the LAN ports on the wireless
router and then check its IP address. If the client still gets a
169.254.x.y address, then the wireless router's DHCP server is either
turned off or busted.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

I have an old laptop wired to the router and it got an IP right away.

I don't know if this will help, but the SBS NG had a suggestion to put the
wireless router right off the LAN/WAN router with an IP in the same subnet.
It's isolated from the LAN, and elimination of the 2nd static IP might help.
D-Link also suggested I use WDS with AP mode so the AP's can act as bridges
between our buildings, as well as AP's.

"Lem" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Mike Webb wrote:
>> Thanks for the info. They DO get 169.x.x.x's. And the LAN/WAN router
>> doesn't handle the LAN DHCP; my server does (Small Business Server (SBS)
>> 2003 Premium SP2). Kind of an extra puzzler as it's one 'device' removed
>> from the wireless router.
>>
>> "Lem" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> APIPA means "Automatic Private IP Addressing" and is what Windows
>>> defaults to if a NIC is configured to get an address from a DHCP server
>>> but no server is found. These addresses are in the range 169.254.0.1 to
>>> 169.254.255.254. Do an ipconfig /all from a command prompt on a couple
>>> of the wireless clients (both next to the wireless router and next to
>>> one of the APs). If they have IP addresses of the form 169.254.x.y,
>>> they are not seeing any DHCP server.
>>>
>>> NAT means Network Address Translation, and is used in a router to
>>> translate IP addresses between two separate networks (such as the
>>> Internet and a LAN or between 2 local networks that use different
>>> subnets). If you want your wireless clients to have addresses in the
>>> range 192.168.0.100-.199 and you want your wired clients to be separate
>>> (which you do), you probably have your LAN/WAN router set to hand out
>>> addresses in a different range, such as 192.168.1.100 - 199 (the
>>> difference is the 3rd octet).
>>>
>>> --
>>> Lem -- MS-MVP
>>>
>>> To the moon and back with 2K words of RAM and 36K words of ROM.
>>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>>> http://history.nasa.gov/afj/compessay.htm
>>
>>
>
> It sound's as if the wireless router's DHCP server isn't working. If it's
> a typical SOHO wireless router and has several LAN ports on it, try
> connecting a client computer to one of the LAN ports on the wireless
> router and then check its IP address. If the client still gets a
> 169.254.x.y address, then the wireless router's DHCP server is either
> turned off or busted.
>
> --
> Lem -- MS-MVP
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm

Mike Webb wrote:
> I have an old laptop wired to the router and it got an IP right away.
>
> I don't know if this will help, but the SBS NG had a suggestion to put the
> wireless router right off the LAN/WAN router with an IP in the same subnet.
> It's isolated from the LAN, and elimination of the 2nd static IP might help.
> D-Link also suggested I use WDS with AP mode so the AP's can act as bridges
> between our buildings, as well as AP's.
>
> "Lem" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Mike Webb wrote:
>>> Thanks for the info. They DO get 169.x.x.x's. And the LAN/WAN router
>>> doesn't handle the LAN DHCP; my server does (Small Business Server (SBS)
>>> 2003 Premium SP2). Kind of an extra puzzler as it's one 'device' removed
>>> from the wireless router.
>>>
>>> "Lem" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> APIPA means "Automatic Private IP Addressing" and is what Windows
>>>> defaults to if a NIC is configured to get an address from a DHCP server
>>>> but no server is found. These addresses are in the range 169.254.0.1 to
>>>> 169.254.255.254. Do an ipconfig /all from a command prompt on a couple
>>>> of the wireless clients (both next to the wireless router and next to
>>>> one of the APs). If they have IP addresses of the form 169.254.x.y,
>>>> they are not seeing any DHCP server.
>>>>
>>>> NAT means Network Address Translation, and is used in a router to
>>>> translate IP addresses between two separate networks (such as the
>>>> Internet and a LAN or between 2 local networks that use different
>>>> subnets). If you want your wireless clients to have addresses in the
>>>> range 192.168.0.100-.199 and you want your wired clients to be separate
>>>> (which you do), you probably have your LAN/WAN router set to hand out
>>>> addresses in a different range, such as 192.168.1.100 - 199 (the
>>>> difference is the 3rd octet).
>>>>
>>>> --
>>>> Lem -- MS-MVP
>>>>
>>>> To the moon and back with 2K words of RAM and 36K words of ROM.
>>>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>>>> http://history.nasa.gov/afj/compessay.htm
>>>
>> It sound's as if the wireless router's DHCP server isn't working. If it's
>> a typical SOHO wireless router and has several LAN ports on it, try
>> connecting a client computer to one of the LAN ports on the wireless
>> router and then check its IP address. If the client still gets a
>> 169.254.x.y address, then the wireless router's DHCP server is either
>> turned off or busted.
>>
>> --
>> Lem -- MS-MVP
>>
>> To the moon and back with 2K words of RAM and 36K words of ROM.
>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>> http://history.nasa.gov/afj/compessay.htm
>
>

Could work. I'd try to do things piece by piece. For example, if your
old laptop gets an IP, that sounds as if the router's DHCP is working.
Try disconnecting the wireless APs from router. Then see if a different
client computer can get an IP from the router. I don't have time to
think it through right now, and I'll be off the air for a while. Good luck.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

Also, if no joy, you might try starting a new thread (perhaps
cross-posted here) in microsoft.public.windowsxp.network_web. It seems
to me that your problem is more of a "networking" problem than a
"wireless" problem.

Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm