Metropol

I'm trying to get my Netgear MA101 wireless network adaptor to work with Windows 2000. It is supposed to work with the Netgear ME102 access point downstairs providing me with internet access. However, when I set the software and everything up as instructed, the IP address is being assigned by the computer (i.e. 169.254.12.231), and therefore I cannot connect to the internet. All of my settings are configured correctly, and something it works fine on the XP computer next door, with identical hardware (i.e. the same model of MA101 connecting to the same ME102 downstairs, but when I had XP on the computer in question it still didn't work). I have also tried the 'netsh' command, which successfully gets the IP address from DHCP, but still offers no internet connection. When I tried ipconfig /release, I got the message "Adapter Local Area Connection 2 was automatically configured and does not currently have a DHCP address. The IP address for this adapter cannot be released." and "The following error occured when renewing adapter Local Area Connection 2: DHCP Server unavailable) when I tried ipconfig /renew.

Anyone have any ideas?

Does it work if you configure the lan card with a static address on the same subnet as the accesspoint?

ITV Lover wrote:I'm trying to get my Netgear MA101 wireless network adaptor to work with Windows 2000. It is supposed to work with the Netgear ME102 access point downstairs providing me with internet access. However, when I set the software and everything up as instructed, the IP address is being assigned by the computer (i.e. 169.254.12.231), and therefore I cannot connect to the internet. All of my settings are configured correctly, and something it works fine on the XP computer next door, with identical hardware (i.e. the same model of MA101 connecting to the same ME102 downstairs, but when I had XP on the computer in question it still didn't work). I have also tried the 'netsh' command, which successfully gets the IP address from DHCP, but still offers no internet connection. When I tried ipconfig /release, I got the message "Adapter Local Area Connection 2 was automatically configured and does not currently have a DHCP address. The IP address for this adapter cannot be released." and "The following error occured when renewing adapter Local Area Connection 2: DHCP Server unavailable) when I tried ipconfig /renew.

Anyone have any ideas?

Im afraid i cant help you.

wells wrote:

ITV Lover wrote:I'm trying to get my Netgear MA101 wireless network adaptor to work with Windows 2000. It is supposed to work with the Netgear ME102 access point downstairs providing me with internet access. However, when I set the software and everything up as instructed, the IP address is being assigned by the computer (i.e. 169.254.12.231), and therefore I cannot connect to the internet. All of my settings are configured correctly, and something it works fine on the XP computer next door, with identical hardware (i.e. the same model of MA101 connecting to the same ME102 downstairs, but when I had XP on the computer in question it still didn't work). I have also tried the 'netsh' command, which successfully gets the IP address from DHCP, but still offers no internet connection. When I tried ipconfig /release, I got the message "Adapter Local Area Connection 2 was automatically configured and does not currently have a DHCP address. The IP address for this adapter cannot be released." and "The following error occured when renewing adapter Local Area Connection 2: DHCP Server unavailable) when I tried ipconfig /renew.

Anyone have any ideas?

Im afraid i cant help you.

Then why did you reply?

PS - learn how to use punctuation and capital letters.

ITV Lover wrote:I'm trying to get my Netgear MA101 wireless network adaptor to work with Windows 2000. It is supposed to work with the Netgear ME102 access point downstairs providing me with internet access. However, when I set the software and everything up as instructed, the IP address is being assigned by the computer (i.e. 169.254.12.231), and therefore I cannot connect to the internet.

A 169 address is usually given as an IP address when the system is expecting an IP address from somewhere else, typically a router, but for whatever reason doesn't get an address, most often because the router isn't switched on or the computer isn't wired to it.

You'll have no connectivity at all with your router with a 169 address. It's usually a good idea where possible to set these things up wired as opposed to wireless.

All of my settings are configured correctly, and something it works fine on the XP computer next door, with identical hardware (i.e. the same model of MA101 connecting to the same ME102 downstairs, but when I had XP on the computer in question it still didn't work).

This points to an issue between the router and your computer. There's nothing in Windows XP that will cause this sort of behaviour out of the box. Have you set any security that may have inadvertedly locked your system out?

I have also tried the 'netsh' command, which successfully gets the IP address from DHCP, but still offers no internet connection. When I tried ipconfig /release, I got the message "Adapter Local Area Connection 2 was automatically configured and does not currently have a DHCP address. The IP address for this adapter cannot be released." and "The following error occured when renewing adapter Local Area Connection 2: DHCP Server unavailable) when I tried ipconfig /renew.

This is pointing to a router problem in this area, or again an issue between the router and your computer at least.

the man who can wrote:More to the point y has this been draged up from march of last year?

Good point, only just noticed.

Just had a peek at "Wellsey Online."

TV and Radio Presenter
The Greatest Thing To Hit Radio Since Music

Maybe tone down the ego a tad there, Steve Wright.

the man who can wrote:Maybe wells noticed it and has a similar problem or something but couldnt be botherd to start a new thread, but then y did he no just say so?

Hmm.