xp not detecting correct dhcp address

I have 2 computers that will connect wirelessly without any problems.
However, the third is being a pain. As I've been sifting through
options on it, I found that it is not connecting to the dhcp server (my
router) at the correct ip. I can change all sorts of other option, but
I am at a loss as to how to make it look at the correct spot. I have
been looking at all kinds of information today, most of it not usefull,
so please tell me if I need to supply you with more information. Thank
you.

(E-Mail Removed) wrote:
> I have 2 computers that will connect wirelessly without any problems.
> However, the third is being a pain. As I've been sifting through
> options on it, I found that it is not connecting to the dhcp server (my
> router) at the correct ip. I can change all sorts of other option, but
> I am at a loss as to how to make it look at the correct spot. I have
> been looking at all kinds of information today, most of it not usefull,
> so please tell me if I need to supply you with more information. Thank
> you.
>

The make it use static IP(s) on the router.

Duane

(E-Mail Removed) hath wroth:

>I have 2 computers that will connect wirelessly without any problems.
>However, the third is being a pain. As I've been sifting through
>options on it, I found that it is not connecting to the dhcp server (my
>router) at the correct ip. I can change all sorts of other option, but
>I am at a loss as to how to make it look at the correct spot. I have
>been looking at all kinds of information today, most of it not usefull,
>so please tell me if I need to supply you with more information. Thank
>you.

More information please:
1. What exact operating system?
2. What model router?
3. What is the "correct" IP you're expecting?
4. What is it getting instead? If it's 169.254.xxx.xxx, that's the
default IP that Windoze assigns if the DHCP client can't an IP address
from the DHCP server.
5. Does your router have any MAC address filters setup? If so, is
the 3rd computah's MAC address in the filter table?
6. Are you using any form of encryption? You should be using WPA-PSK
or better. If you're using WEP, be sure to use the Hex key, not the
ASCII key. Details on request.
7. Are you sure you're connecting to your own wireless router and not
the neighbors? Is the SSID unique?

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

@Duane:
I tried that, but it still wasn't connecting. I seem to remember that
it would connect, but I couldn't ping anything.

@Jeff:
1. Windows XP Home SP2
2. WRT54GL (haven't flashed with 3rd-party firmware)
3. 192.168.1.1
4. 255.255.255.255
5. no
6. wpa-psk; the encryption's correct. It's working correct on the
other two, and it worked once on the problem computer, but it randomly
stopped (without me changing anything, including (un)installing
anything.
7. Yep, I'm connecting to mine; around me around linksys and deh2, but
I'm connecting to nubcakes (which is pretty unique, I'd say).

"Xiong Chiamiov" <(E-Mail Removed)> hath wroth:

>@Duane:
>I tried that, but it still wasn't connecting. I seem to remember that
>it would connect, but I couldn't ping anything.
>
>@Jeff:
>1. Windows XP Home SP2
>2. WRT54GL (haven't flashed with 3rd-party firmware)

You really should. I like DD-WRT v23 SP1.

>3. 192.168.1.1

Yep. That's the routers IP address.

>4. 255.255.255.255

Impossible. That's not a valid IP address. It's probably the netmask
or a mistake. Run:
Start -> run -> cmd <enter>
ipconfig
and check the IP address line. If it's 192.168.xxx.xxx, then DHCP is
working. If it's 169.254.xxx.xxx, DHCP has failed. If it's 0.0.0.0,
wait a while and it will eventually change. If it's a routeable IP
address, you have the DSL/cable/whatever modem plugged into the WRT54G
LAN port instead of the the proper WAN (internet) port.

>5. no
>6. wpa-psk; the encryption's correct. It's working correct on the
>other two, and it worked once on the problem computer, but it randomly
>stopped (without me changing anything, including (un)installing
>anything.

Random? Just try reloading the WPA key again on the computer. Typos
are epidemic. If that doesn't play, try temporarily turning off
encryption in the WRT54GL router. If that works, check for driver and
firmware updates for both the router and your computer.

Since it's probably something on this computer, some details like
maker, model, wireless card, operating system, and whether it works
with a wired connection would be nice. Numbers, not descriptions are
what I need.

It's probably too late to use system restore to put things back. My
best guess is that you recovered from a spyware or virus infection in
the past and the LSP is messed up.
If your computer works with a wired connection, ignore the following.
If your computer works with a wired connection, ignore the following.
If your computer works with a wired connection, ignore the following.
If it does NOT work with a wired connection, try:
http://www.snapfiles.com/get/winsockxpfix.html
or one of several LSP editors and repair utilties such as Hijack This:
http://www.tomcoyote.org/hjt/#Top
Note that this one is for experts. If you don't know what you're
doing, don't try this one.

Be sure to backup the registry before attacking. Do it once with
system restore:
Start -> Programs -> accessories -> system tools -> system restore
and again with ERUNT:
http://www.larshederer.homepage.t-online.de/erunt/
The main benifit of ERUNT is that is makes recovery of just the
registry quick, easy and reliable.

>7. Yep, I'm connecting to mine; around me around linksys and deh2, but
>I'm connecting to nubcakes (which is pretty unique, I'd say).

Can you see the nubcakes SSID with whatever client manager you're
using on this computah?

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Xiong Chiamiov wrote:
> @Duane:
> I tried that, but it still wasn't connecting. I seem to remember that
> it would connect, but I couldn't ping anything.
>
> @Jeff:
> 1. Windows XP Home SP2
> 2. WRT54GL (haven't flashed with 3rd-party firmware)
> 3. 192.168.1.1
> 4. 255.255.255.255
> 5. no
> 6. wpa-psk; the encryption's correct. It's working correct on the
> other two, and it worked once on the problem computer, but it randomly
> stopped (without me changing anything, including (un)installing
> anything.
> 7. Yep, I'm connecting to mine; around me around linksys and deh2, but
> I'm connecting to nubcakes (which is pretty unique, I'd say).
>

Is not 192.168.1.1 the Device IP for any Linksys router? So how can the
computer be using 192.168.1.1?

I have not be connected to a router in several months. What's the Subnet
Mask and IP for a machine wired or wireless that has a good
connection, can ping and access the Internet connected to the router?

If the NIC can't get a DHCP IP from the router nor will it work with a
static IP if you are correct is making the computer use a static IP on
the router, then the card may be defective.

Duane

>>2. WRT54GL (haven't flashed with 3rd-party firmware)

>You really should. I like DD-WRT v23 SP1.

Well, I was told not to unless I was comfortable with linux, which I am
not.

>>4. 255.255.255.255

>Impossible. That's not a valid IP address. It's probably the netmask
or a mistake. Run:
Start -> run -> cmd <enter>
ipconfig
and check the IP address line. If it's 192.168.xxx.xxx, then DHCP is
working. If it's 169.254.xxx.xxx, DHCP has failed. If it's 0.0.0.0,
wait a while and it will eventually change. If it's a routeable IP
address, you have the DSL/cable/whatever modem plugged into the WRT54G
LAN port instead of the the proper WAN (internet) port.

I know, I know. That's what's bugging me. When I do an ipconfig /all,
that's what shows up. Now, to clarify, that is what shows up as the
DHCP address. The IP address of the computer is 0.0.0.0. But that
doesn't change (how long should I wait?).

>>6. wpa-psk; the encryption's correct. It's working correct on the
>>other two, and it worked once on the problem computer, but it randomly
>>stopped (without me changing anything, including (un)installing
>>anything.

>Random? Just try reloading the WPA key again on the computer. Typos
>are epidemic. If that doesn't play, try temporarily turning off
>encryption in the WRT54GL router. If that works, check for driver and
>firmware updates for both the router and your computer.

Last time I reset the router, and it worked again. I enabled
encryption and everything, and it continued. But then it didn't work
any more after a few days. And the firmware and drivers are updated.

>>7. Yep, I'm connecting to mine; around me around linksys and deh2, but
>>I'm connecting to nubcakes (which is pretty unique, I'd say).

>Can you see the nubcakes SSID with whatever client manager you're
>using on this computah?

Yep. My wireless card is a Planet (off of Newegg), and I'm using their
utility. It shows the connection being good for about 4 secs, then
goes to no connection for about 1/2 sec, then repeats, which keeps it
in the "aquiring network address" stage.


Now, I tried the winsock fix shortly before coming here. No go. I
don't know if it will work wired in its present state because it's not
close and not mobile. As I said before, it used to be the only
computer in the house and connected straight to the modem, which
worked.
It is an old-ish Gateway running XP Home SP2 (originally ME). Wireless
card is a Planet WL-8310.
[http://www.newegg.com/Product/Produc...2E16833322201] It has
been reformatted once ('bout a year, year and a half ago) and is
working fine other than that. I am pretty darn sure that it hasn't had
any spyware on it for a long time, or viruses either.
My other comps are connected with IPs of 192.168.1.101, 192.168.1.102,
etc. I have IP addresses open for much longer than that, and no limit
on DHCP clients.
Subnet mask: 255.255.255.128
Gateway and DHCP server: 192.168.1.1
DNS Servers: 207.69.188.185, 207.69.188.186, 207.69.188.187

I will check again without encryption, as well as with static IP, and
report back to you. If it is the card, I can still get a replacement
from Newegg, so that's all good.
Thanks.

"Xiong Chiamiov" <(E-Mail Removed)> hath wroth:

> >>2. WRT54GL (haven't flashed with 3rd-party firmware)
>
>>You really should. I like DD-WRT v23 SP1.
>
>Well, I was told not to unless I was comfortable with linux, which I am
>not.

DD-WRT and others have web interfaces. There is very little there
that is Linux specific. It looks like an expanded version of the
stock Linksys firmware. This may be a problem as there are at least
twice as many options and menus. I don't think the problem will be
lack of Linux knowledge. It will be trying to decode the strange
network feature names.

>>>4. 255.255.255.255
>I know, I know. That's what's bugging me. When I do an ipconfig /all,
>that's what shows up. Now, to clarify, that is what shows up as the
>DHCP address. The IP address of the computer is 0.0.0.0. But that
>doesn't change (how long should I wait?).

The DHCP client should take about 30 seconds to give up. Something is
seriously wrong with your Windoze IP network stack. It might be
getting garbage from the DHCP server in the WRT54GL. Try downloading
a DHCP/BOOTP query tool:
| http://www.weirdsolutions.com/weirdS...ytool_free.exe
You do NOT need a valid IP address to use this tool. The XP DHCP
client must be set to DHCP (get IP from router) for this to work. My
guess is that when DHCP is working, the tool will show a proper
response. When it craps out, my guess is that it will show garbage.

>Last time I reset the router, and it worked again. I enabled
>encryption and everything, and it continued. But then it didn't work
>any more after a few days. And the firmware and drivers are updated.

Days? Any chance you have an interference problem from something like
a cordless phone or nearby community wireless network? The
intermittent nature of the problem sounds like interference. (I'm
guessing here).

>>Can you see the nubcakes SSID with whatever client manager you're
>>using on this computah?
>
>Yep. My wireless card is a Planet (off of Newegg), and I'm using their
>utility. It shows the connection being good for about 4 secs, then
>goes to no connection for about 1/2 sec, then repeats, which keeps it
>in the "aquiring network address" stage.

I've have very bad luck with "no name" wireless devices from various
mail order sources.

>Now, I tried the winsock fix shortly before coming here. No go. I
>don't know if it will work wired in its present state because it's not
>close and not mobile. As I said before, it used to be the only
>computer in the house and connected straight to the modem, which
>worked.

Well, I hate to suggest dragging the computer to near the WRT54GL, but
that will tell quite a bit. Maybe borrow a long CAT5 cable and run it
temporarily to the WRT54GL. If it works with the wired ethernet, then
it's unlikely that it's a Windoze IP stack or LSP problem. That makes
it a wireless card or driver problem. However, if it screws up with a
wired connection, then it's a Windoze problem.

>It is an old-ish Gateway running XP Home SP2 (originally ME). Wireless
>card is a Planet WL-8310.
>[http://www.newegg.com/Product/Produc...2E16833322201]

See:
http://www.planet.com.tw/product/pro...166&menu_id=14
Sorry, I have no experience with this card. The download page shows
quite a few driver and utility updates.

>It has
>been reformatted once ('bout a year, year and a half ago) and is
>working fine other than that. I am pretty darn sure that it hasn't had
>any spyware on it for a long time, or viruses either.
>My other comps are connected with IPs of 192.168.1.101, 192.168.1.102,
>etc. I have IP addresses open for much longer than that, and no limit
>on DHCP clients.

>Subnet mask: 255.255.255.128

Bingo! Use 255.255.255.0 instead. That's the problem and why the
DHCP server is working but not delivering an IP address.

Also, did you perhaps limit the number of available DHCP addresses in
the router as some manner of security measure? I know you said "no
limit on DHCP clients" but I want to be sure we're talking about the
same thing.

>Gateway and DHCP server: 192.168.1.1
>DNS Servers: 207.69.188.185, 207.69.188.186, 207.69.188.187
>
>I will check again without encryption, as well as with static IP, and
>report back to you. If it is the card, I can still get a replacement
>from Newegg, so that's all good.
>Thanks.

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

On Mon, 03 Jul 2006 21:19:41 -0700, Jeff Liebermann
<(E-Mail Removed)> wrote:
: "Xiong Chiamiov" <(E-Mail Removed)> hath wroth:
: >It has
: >been reformatted once ('bout a year, year and a half ago) and is
: >working fine other than that. I am pretty darn sure that it hasn't had
: >any spyware on it for a long time, or viruses either.
: >My other comps are connected with IPs of 192.168.1.101, 192.168.1.102,
: >etc. I have IP addresses open for much longer than that, and no limit
: >on DHCP clients.
:
: >Subnet mask: 255.255.255.128
:
: Bingo! Use 255.255.255.0 instead. That's the problem and why the
: DHCP server is working but not delivering an IP address.

Why so? Nothing we've heard so far suggests that he needs the wider range. Are
his other computers getting their addresses from the Linksys? They could be,
since their addresses fall within the range.

: Also, did you perhaps limit the number of available DHCP addresses in
: the router as some manner of security measure? I know you said "no
: limit on DHCP clients" but I want to be sure we're talking about the
: same thing.
:
: >Gateway and DHCP server: 192.168.1.1

Which is consistent with the existing subnet mask.

: >DNS Servers: 207.69.188.185, 207.69.188.186, 207.69.188.187
: >
: >I will check again without encryption, as well as with static IP, and
: >report back to you. If it is the card, I can still get a replacement
: >from Newegg, so that's all good.
: >Thanks.

My bet is that the interface is misconfigured on the client.

Robert Coe <(E-Mail Removed)> hath wroth:

>On Mon, 03 Jul 2006 21:19:41 -0700, Jeff Liebermann
><(E-Mail Removed)> wrote:
>: "Xiong Chiamiov" <(E-Mail Removed)> hath wroth:
>: >It has
>: >been reformatted once ('bout a year, year and a half ago) and is
>: >working fine other than that. I am pretty darn sure that it hasn't had
>: >any spyware on it for a long time, or viruses either.
>: >My other comps are connected with IPs of 192.168.1.101, 192.168.1.102,
>: >etc. I have IP addresses open for much longer than that, and no limit
>: >on DHCP clients.
>:
>: >Subnet mask: 255.255.255.128
>:
>: Bingo! Use 255.255.255.0 instead. That's the problem and why the
>: DHCP server is working but not delivering an IP address.
>
>Why so? Nothing we've heard so far suggests that he needs the wider range. Are
>his other computers getting their addresses from the Linksys? They could be,
>since their addresses fall within the range.

You're right. It should work with a netmask of 255.255.255.128. That
gives a host range of 192.168.1.1 thru 192.168.1.126 (with .127 as
broadcast). All his IP's fall inside this range, so it should work.

However, my suspicious mind always looks for settings that are out of
the ordinary and not part of the standard wireless router
configuration. The odd netmask is one. If he doesn't need two
subnets, then there's no reason to NOT use the standard 255.255.255.0.
The list of IP's used is also incomplete. I doubt that he's using
over 26 computers that need IP's, but it's possible. The fact that it
is intermittent sorta hints that he might be running out of IP's in
the DHCP address pool. Dunno. I suggest he put the router back to
something resembling the simple default settings. It can't hurt.

>My bet is that the interface is misconfigured on the client.

I've been trying to figure out how one could do that and get a DHCP
delivered IP address of 255.255.255.255. It might be misconfigured
but there are a limited number of ways to screw up the client setup.
If the wired ethernet is functional, then it's a fair bet that the IP
stack is intact. The fact that it sometimes works makes the logic
even more complex. I don't think it's misconfiguration as
configurations don't change by themselves intermittently (unless he's
using multiple Profiles or Netswitcher). My guess(tm) is a broken
wireless driver.

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558