WRT54G Doesn't Send Correct IP Address

In trying to run down a friend's network problem between two XP Home
computers and a LinkSys WRT54G Router, I noticed that the router is
not sending the IP address expected on the wireless connection. The
problem has been that both computers can connect to the internet, but
can't see each other. Now I see why. The desktop, hardwired from a
NIC, gets a what you would expect 192.168.1.100 (may not be exact.)
It has a subnet mask of 255.255.255.0. The laptop (wireless) gets a
completely unrelated IP address (beginning with 162 or 168, and a
subnet mask of 255,255,0.0. The connection to the modem through the
router works, but of course it can't find the desktop. What do I need
to do to get the WRT54G to sent the correct IP address to the laptop?

"Dick" <LeadWinger> wrote in message
news:(E-Mail Removed)...
> In trying to run down a friend's network problem between two XP Home
> computers and a LinkSys WRT54G Router, I noticed that the router is
> not sending the IP address expected on the wireless connection. The
> problem has been that both computers can connect to the internet, but
> can't see each other. Now I see why. The desktop, hardwired from a
> NIC, gets a what you would expect 192.168.1.100 (may not be exact.)
> It has a subnet mask of 255.255.255.0.

> The laptop (wireless) gets a
> completely unrelated IP address (beginning with 162 or 168, and a
> subnet mask of 255,255,0.0. The connection to the modem through the
> router works, but of course it can't find the desktop. What do I need
> to do to get the WRT54G to sent the correct IP address to the laptop?

If the machine is not getting a DHCP IP from the DHCP server in the router,
then it may be a sign that machine is having some kind of time out condition
in getting an IP from the DHCP server in the router. The IP being assigned
may allow the machine to access other machines on the LAN. However, the
machine will not be able to access the Internet. This is usually due to a
mis-configuration of the NIC.

Did you connect the machine to the wire on the router and does the problem
follow? If it does, then it may be a sign that the TCP/IP Stack may be
locked and will need to be reset.

Duane

Dick <LeadWinger> wrote:
> It has a subnet mask of 255.255.255.0. The laptop (wireless) gets a
> completely unrelated IP address (beginning with 162 or 168, and a
> subnet mask of 255,255,0.0. The connection to the modem through the
> router works, but of course it can't find the desktop. What do I need
> to do to get the WRT54G to sent the correct IP address to the laptop?

That looks like a Windows Auto-Configuration IP address, which happens if
no DHCP is found.

http://support.microsoft.com/default...;EN-US;Q220874
169.254.x.y - subnet mask of 255.255.0.0

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

On Wed, 09 Jun 2004 04:57:08 GMT, "Duane Arnold" <(E-Mail Removed)>
wrote:

>
>"Dick" <LeadWinger> wrote in message
>news:(E-Mail Removed).. .
>> In trying to run down a friend's network problem between two XP Home
>> computers and a LinkSys WRT54G Router, I noticed that the router is
>> not sending the IP address expected on the wireless connection. The
>> problem has been that both computers can connect to the internet, but
>> can't see each other. Now I see why. The desktop, hardwired from a
>> NIC, gets a what you would expect 192.168.1.100 (may not be exact.)
>> It has a subnet mask of 255.255.255.0.
>
>> The laptop (wireless) gets a
>> completely unrelated IP address (beginning with 162 or 168, and a
>> subnet mask of 255,255,0.0. The connection to the modem through the
>> router works, but of course it can't find the desktop. What do I need
>> to do to get the WRT54G to sent the correct IP address to the laptop?
>
>If the machine is not getting a DHCP IP from the DHCP server in the router,
>then it may be a sign that machine is having some kind of time out condition
>in getting an IP from the DHCP server in the router. The IP being assigned
>may allow the machine to access other machines on the LAN. However, the
>machine will not be able to access the Internet. This is usually due to a
>mis-configuration of the NIC.
>
>Did you connect the machine to the wire on the router and does the problem
>follow? If it does, then it may be a sign that the TCP/IP Stack may be
>locked and will need to be reset.
>
>Duane
>
I tried my own HP laptop on his network and it connected right away.
However, it also got a screwy IP address and subnet mask. The problem
is the opposite of what you describe. The wireless laptops connect to
the internet OK, but can't connect with each other or the hardwired
desktop.

the 162.xxx address is assigned by Microsoft when
- no static IP is pre-defined on the PC
- no DHCP address was retrieved for the PC
I would address that problem first -
Not sure how they could be connecting to the Internet
thru your router - with a local 162.xxx address ?
Go to the start / run / cmd / and in the DOS window type - route print -
that should show you how your network looks to the PC -

Not seeing each other is a Netbios problem with the "MS sharing"
and that comes after solving the IP problem -
Can only see each other if they have something to share...
and the firewall is allowing 135 -139 ports to be open
and .....etc...

That sure seems to nail the problem. I'm wondering now if there is a
problem with the router itself. My own laptop, that works perfectly
on my own wireless network, got the same auto-config IP address. The
fact that a hard-wired computer gets the correct DHCP assigned IP
address, and the wireless laptops do not should be a clue for me to
work on.

On Wed, 9 Jun 2004 05:05:19 +0000 (UTC), (E-Mail Removed)
wrote:

>Dick <LeadWinger> wrote:
>> It has a subnet mask of 255.255.255.0. The laptop (wireless) gets a
>> completely unrelated IP address (beginning with 162 or 168, and a
>> subnet mask of 255,255,0.0. The connection to the modem through the
>> router works, but of course it can't find the desktop. What do I need
>> to do to get the WRT54G to sent the correct IP address to the laptop?
>
>That looks like a Windows Auto-Configuration IP address, which happens if
>no DHCP is found.
>
>http://support.microsoft.com/default...;EN-US;Q220874
>169.254.x.y - subnet mask of 255.255.0.0

"Dick" <LeadWinger> wrote in message
news:(E-Mail Removed)...
> That sure seems to nail the problem. I'm wondering now if there is a
> problem with the router itself. My own laptop, that works perfectly
> on my own wireless network, got the same auto-config IP address. The
> fact that a hard-wired computer gets the correct DHCP assigned IP
> address, and the wireless laptops do not should be a clue for me to
> work on.
>
How do you know that you are even connected to the AP ?
Can you see the MACs listed inside the router status ?
of the hardwired PC ?
Is there any WEP or WPA that is turned on ?

On Wed, 09 Jun 2004 20:27:49 GMT, "Phil Schuman"
<(E-Mail Removed)> wrote:

>
>"Dick" <LeadWinger> wrote in message
>news:(E-Mail Removed).. .
>> That sure seems to nail the problem. I'm wondering now if there is a
>> problem with the router itself. My own laptop, that works perfectly
>> on my own wireless network, got the same auto-config IP address. The
>> fact that a hard-wired computer gets the correct DHCP assigned IP
>> address, and the wireless laptops do not should be a clue for me to
>> work on.
>>
>How do you know that you are even connected to the AP ?
>Can you see the MACs listed inside the router status ?
> of the hardwired PC ?
>Is there any WEP or WPA that is turned on ?
>
>
The only computer appearing in the router status is the hard-wired
desktop. All security is temporarily turned off. I am going to try
using static IP's.

"Dick" <LeadWinger> wrote in message
news:(E-Mail Removed)...
> On Wed, 09 Jun 2004 20:27:49 GMT, "Phil Schuman"
> <(E-Mail Removed)> wrote:
>
> >
> >"Dick" <LeadWinger> wrote in message
> >news:(E-Mail Removed).. .
> >> That sure seems to nail the problem. I'm wondering now if there is a
> >> problem with the router itself. My own laptop, that works perfectly
> >> on my own wireless network, got the same auto-config IP address. The
> >> fact that a hard-wired computer gets the correct DHCP assigned IP
> >> address, and the wireless laptops do not should be a clue for me to
> >> work on.
> >>
> >How do you know that you are even connected to the AP ?
> >Can you see the MACs listed inside the router status ?
> > of the hardwired PC ?
> >Is there any WEP or WPA that is turned on ?
> >
> >
> The only computer appearing in the router status is the hard-wired
> desktop. All security is temporarily turned off. I am going to try
> using static IP's.

I don't know if the first post ever made it.

It sounds to me like you have a mis-configuration of the NIC that is
preventing the machine from getting a IP from the DHCP server on the
router. That's usually what it means if you get an IP that has not been
issued from the DHCP server.

Have you tried a wired connection with the machine to the router? A wired
connection may not work either now, because the TCP/IP stack on the machine
may be locked.

Did you try a IPCONFIG /release and /renew to see if the machine will get an
IP from the DHCP Server?

You may not be able to use a static IP either, if the TCP/IP Stack is
locked.

Duane

On Thu, 10 Jun 2004 03:38:20 GMT, "Duane Arnold" <(E-Mail Removed)>
wrote:

>> The only computer appearing in the router status is the hard-wired
>> desktop. All security is temporarily turned off. I am going to try
>> using static IP's.
>
>I don't know if the first post ever made it.
>
>It sounds to me like you have a mis-configuration of the NIC that is
>preventing the machine from getting a IP from the DHCP server on the
>router. That's usually what it means if you get an IP that has not been
>issued from the DHCP server.
>
>Have you tried a wired connection with the machine to the router? A wired
>connection may not work either now, because the TCP/IP stack on the machine
>may be locked.
>
>Did you try a IPCONFIG /release and /renew to see if the machine will get an
>IP from the DHCP Server?
>
>You may not be able to use a static IP either, if the TCP/IP Stack is
>locked.
>
>Duane
>
>

I have discounted that possibility because I tried my own laptop,
similar to the one in the problem system, and got the same auto IP
from windows. I know mine works because I use it at home on my
network. I am going to try the ipconfig/release/renew. Thanks.

Dick