D-Link router - Ethernet works but wireless does not

I have a desktop with a wireless PCI card (D-Link DWL-G250) and a
wireless router to connect to (D-Link DI-624). Of late, I haven't been
able to connect to it over wireless. Using an ethernet cable, I am able
to connect to the internet via the cable modem connection that I have.

I have the ethernet connection configured to obtain an IP address and
DNS server address automatically, and it works fine with that setting.
I can surf webpages without problems.

For the wireless connection, when I do the same thing, (i.e. ask it
obtain IP and DNS server address automatically), I get no internet
connectivity. My card is able to detect the wireless network, though. I
can also ping the router over wireless (i.e. after unplugging the
ethernet cable) whose IP is 192.168.0.1. But when I go to 'View
wireless networks', click on mine and say connect, the status
indefinitely shows as 'Acquiring Network Address'.

What am I missing here?

SD

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

>I have a desktop with a wireless PCI card (D-Link DWL-G250) and a
>wireless router to connect to (D-Link DI-624). Of late, I haven't been
>able to connect to it over wireless. Using an ethernet cable, I am able
>to connect to the internet via the cable modem connection that I have.
>
>I have the ethernet connection configured to obtain an IP address and
>DNS server address automatically, and it works fine with that setting.
>I can surf webpages without problems.
>
>For the wireless connection, when I do the same thing, (i.e. ask it
>obtain IP and DNS server address automatically), I get no internet
>connectivity. My card is able to detect the wireless network, though. I
>can also ping the router over wireless (i.e. after unplugging the
>ethernet cable) whose IP is 192.168.0.1. But when I go to 'View
>wireless networks', click on mine and say connect, the status
>indefinitely shows as 'Acquiring Network Address'.

"Acquiring Network Address" means that you have successfully found the
wirless router, but that the encryption key exchange probably failed.
However, it shouldn't sit there indefinitely. It should eventually
say "limited connectivity...". If you're using WEP, be sure to use
the Hex WEP key, not the ASCII. Also try it with no encryption and
see if that works. Both ends will do WPA-PSK, so you should be using
that. Also, check the DLink web pile for the latest drivers and
firmware.

Note that DLink has finally posted the latest beta firmware for
various DI-624 models. For Rev C:
http://support.dlink.com/products/vi...I%2D624%5FrevC
Hmmm.... 2.75beta2. This is new.

--
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

Duh.. how could I miss this? It was the WEP key that was incorrect, and
now the problem is fixed, although one would imagine that if the key
were incorrect, an error message would pop up to that effect. Anyway,
thanks much.

SD

Jeff Liebermann wrote:
>
> "Acquiring Network Address" means that you have successfully found the
> wirless router, but that the encryption key exchange probably failed.
> However, it shouldn't sit there indefinitely. It should eventually
> say "limited connectivity...". If you're using WEP, be sure to use
> the Hex WEP key, not the ASCII. Also try it with no encryption and
> see if that works. Both ends will do WPA-PSK, so you should be using
> that. Also, check the DLink web pile for the latest drivers and
> firmware.
>
> Note that DLink has finally posted the latest beta firmware for
> various DI-624 models. For Rev C:
> http://support.dlink.com/products/vi...I%2D624%5FrevC
> Hmmm.... 2.75beta2. This is new.
>
> --
> 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 19 Jul 2006 14:46:31 -0700, "SD" <(E-Mail Removed)> wrote:

>Duh.. how could I miss this? It was the WEP key that was incorrect, and
>now the problem is fixed, although one would imagine that if the key
>were incorrect, an error message would pop up to that effect. Anyway,
>thanks much.

Actually, it's very easy to miss and not your fault. Microsloth
simply forgot to include useful connection progress diagnostics.
Wireless Zero Config should indicate that there was an encryption or
authentication mismatch, but it doesn't.

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

On Thu, 20 Jul 2006 01:03:29 GMT, Jeff Liebermann
<(E-Mail Removed)> wrote in
<(E-Mail Removed)>:

>On 19 Jul 2006 14:46:31 -0700, "SD" <(E-Mail Removed)> wrote:
>
>>Duh.. how could I miss this? It was the WEP key that was incorrect, and
>>now the problem is fixed, although one would imagine that if the key
>>were incorrect, an error message would pop up to that effect. Anyway,
>>thanks much.
>
>Actually, it's very easy to miss and not your fault. Microsloth
>simply forgot to include useful connection progress diagnostics.
>Wireless Zero Config should indicate that there was an encryption or
>authentication mismatch, but it doesn't.

It's really a WEP issue, not a Microsoft issue -- WEP has no real
handshake mechanism that could provide feedback on key mismatch, just
encryption and decryption. If each end has a different key, then
decryption results in meaningless garbage at the receiving end. There's
no error sent back to the sender, since the packet has been received
over Wi-Fi without error. Thus the DHCP client just keeps sending
discovery requests that the DHCP server never sees, until the DHCP
client eventually times out. This is why we just see long "acquiring
network address" delays.

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_How_To>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>