Networking Forums  

Go Back   Networking Forums > Networking Newsgroups > Windows ME Networking

Windows ME doesn't seem to send out DHCP request

Reply
 
Thread Tools Display Modes
  #1  
Old 10-02-2005, 12:42 PM
Default Windows ME doesn't seem to send out DHCP request



Hello!

I've got a GigaByte GN-WMAG WiFi card, which uses
an Atheros AR5212 802.11abg chipset. On Windows
ME, I installed the latest driver made by GigaByte.
The AP is a Linksys WRT-54G running OpenWrt firmware.

The driver comes with a tool called "G-EsLink
Utility", which allows to easily enter the
WEP key and set authentication mode. I entered
my WEP key. After a reboot, the tool shows the
Link-Status as "Associated", which means two
things:

1) Connection is (on a low level) possible and made
2) Correct WEP key

To make things a bit easier, I decided (for now)
to use static IP address assignment: 192.168.1.4/255.255.255.224,
Default GW: 192.168.1.1. 192.168.1.1 is the IP of
the AP/Router.

But even with this static assignment, I cannot connect
to the network - even a simple "ping 192.168.1.1"
fails - 4 misses out of 4.

Why is the networking not working and how can I debug
it further, so that it'll work eventually?

Thanks a lot,

Alexander Skwar

PS:
Crosspost microsoft.public.windowsme.networking,microsoft.pu blic.windows.networking.wireless
Followup-To microsoft.public.windowsme.networking


Alexander Skwar
Reply With Quote
  #2  
Old 10-03-2005, 09:44 AM
Steve Winograd [MVP]
Guest
 
Posts: n/a
Default Re: Windows ME doesn't seem to send out DHCP request

In article <(E-Mail Removed)>, Alexander
Skwar <(E-Mail Removed)> wrote:
>Hello!
>
>I've got a GigaByte GN-WMAG WiFi card, which uses
>an Atheros AR5212 802.11abg chipset. On Windows
>ME, I installed the latest driver made by GigaByte.
>The AP is a Linksys WRT-54G running OpenWrt firmware.
>
>The driver comes with a tool called "G-EsLink
>Utility", which allows to easily enter the
>WEP key and set authentication mode. I entered
>my WEP key. After a reboot, the tool shows the
>Link-Status as "Associated", which means two
>things:
>
>1) Connection is (on a low level) possible and made
>2) Correct WEP key
>
>To make things a bit easier, I decided (for now)
>to use static IP address assignment: 192.168.1.4/255.255.255.224,
>Default GW: 192.168.1.1. 192.168.1.1 is the IP of
>the AP/Router.
>
>But even with this static assignment, I cannot connect
>to the network - even a simple "ping 192.168.1.1"
>fails - 4 misses out of 4.
>
>Why is the networking not working and how can I debug
>it further, so that it'll work eventually?
>
>Thanks a lot,
>
>Alexander Skwar


While troubleshooting, disable WEP on the access point and computer,
and disable any firewall program on the computer. Don't enable them
until everything else is working

Try a wired connection to the router. Does pinging work then?

Check for MAC address filtering on the router.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm
Reply With Quote
Reply

Tags
dhcp, request, send, windows

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 09:22 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.