limited access wireless network

I'm sure that AEM wants you to plug your laptop directly into a port on the router, not your modem. You should get connectivity directly to the network in that manner.

I noticed that you mentioned getting onto the router's website. I assume this means you used another computer and went to http://192.168.1.1 and accessed the router's internal webpage? I'm glad you did, because all that silly talk about DNS and such will solve itself once your situation with getting the laptop onto the network is wrapped up.

Now, I'm going to suggest that we take this right back to the beginning. Go back to the Network and Sharing Center, delete any and all references to past network connections, and start from scratch. Be sure that you're using the latest network card drivers and that the device is working correctly in your device manager. Sit down next to the router and try to create a new connection to the network. Let everything happen automatically. Let the router assign you an IP number, let it handle DNS, let it handle all the other protocols, just remember the security type (WEP, WPA, etc) and the passphrase when the time comes.

Keep us updated.

Original post:PeaB4youGo
I could be wrong, but, while your router appears to be giving you an IP address (so, DHCP is working and so you're connecting to the router) you're not getting out to the internet (proven by the fact that you don't have a 'gateway' defined, and you're writing for help in our forum...lol).

I'd be interested in the results of ipconfig /all on any of the other wireless systems on the network. The things I'm looking for are the IP addresses that they have been assigned, as well as they're subnet masks, compared to these results.

This is incorrect, the address 169.254.x.x on the subnet 255.255.0.0 is referred to as APIPA, and it is assigned by the Network Interface Card (NIC) on the end user device when it cannot find a DHCP server. Therefore the computer "cannot" see the router's DHCP server.

Take a look at this link for further details: What is APIPA? - A Word Definition From the Webopedia Computer Dictionary

This sounds a lot like a NIC driver issue, see if you can get the drivers downloaded on your working computer and transfer them to the non-working computer, load them and try again.

Specific information on your NIC can be found in "Device Manager."

PeaB4YouGo said:

I'm sure that AEM wants you to plug your laptop directly into a port on the router, not your modem. You should get connectivity directly to the network in that manner.

I noticed that you mentioned getting onto the router's website. I assume this means you used another computer and went to http://192.168.1.1 and accessed the router's internal webpage? I'm glad you did, because all that silly talk about DNS and such will solve itself once your situation with getting the laptop onto the network is wrapped up.

Now, I'm going to suggest that we take this right back to the beginning. Go back to the Network and Sharing Center, delete any and all references to past network connections, and start from scratch. Be sure that you're using the latest network card drivers and that the device is working correctly in your device manager. Sit down next to the router and try to create a new connection to the network. Let everything happen automatically. Let the router assign you an IP number, let it handle DNS, let it handle all the other protocols, just remember the security type (WEP, WPA, etc) and the passphrase when the time comes.

Keep us updated.

I did it several times but still get the same message

RyanGEI said:

Original post:PeaB4youGo
I could be wrong, but, while your router appears to be giving you an IP address (so, DHCP is working and so you're connecting to the router) you're not getting out to the internet (proven by the fact that you don't have a 'gateway' defined, and you're writing for help in our forum...lol).

I'd be interested in the results of ipconfig /all on any of the other wireless systems on the network. The things I'm looking for are the IP addresses that they have been assigned, as well as they're subnet masks, compared to these results.

This is incorrect, the address 169.254.x.x on the subnet 255.255.0.0 is referred to as APIPA, and it is assigned by the Network Interface Card (NIC) on the end user device when it cannot find a DHCP server. Therefore the computer "cannot" see the router's DHCP server.

Take a look at this link for further details: What is APIPA? - A Word Definition From the Webopedia Computer Dictionary

This sounds a lot like a NIC driver issue, see if you can get the drivers downloaded on your working computer and transfer them to the non-working computer, load them and try again.

Specific information on your NIC can be found in "Device Manager."

I havevthe latest network card driver

Yeah, then I'm betting you have a NIC card issue. Time to replace that.

aem said:

Have you tried putting in the laptop's MAC address manually on both model webpage and router?

No, i have not. Can you explain how to do that?

I am getting the following message when I attempted to reset ipconfig (through command):
'ipconfig' is not recognized as an internal or external command, operable program or batch file.
I dont know uf this msg is related to the wireless problem or not.