I have just replaced my old wireless router/modem with a new belkin model F7d1401 for better security. works fine with two computers, but my Acer netbook will not connect on wireless. Fine with ethernet, but on wireless it connects to router, but will not access the web. I've never had a problem with this machine connecting elsewhere. Belkin says it must be network adapter aftrer they'd walked me through everything they could think of. - but I don't believe it's the computer at all. It just hooks straight on to hot-spots etc. Any ideas?.
The model number and operating system of your problem Acer might be helpful.
My guess(tm) is that you haven't sucessfully connected to your new Belkin wireless router because you're trying to use the same SSID as the old router. That's fine, but your unspecified model Acer still has the old configuration file for that SSID, and is trying to login using the old security rules and MAC address. Dive into the wireless config for your unspecified operating system, and DELETE the entry for the SSID of your systems. Then, re-create the connection and it should work.
One more. I just wasted about 15 minutes trying to figure out why my Toshiblah laptop wi-fi would connect, but not route. Running various diagnostics, didn't show anything odd. I eventually found that I had to unplug the ethernet cable before the wireless could be used to shovel packets to the router. No clue why as it didn't do this in the past. I'll play with the "route print" command later to see if the route metric is the problem.
Anyway, unplug the ethernet cable from the Acer laptop when testing the wireless and see if that helps.
Apologies - XP. Tried all the above - no luck.. Found a suggestion on web to uninstall driver and install a different specified oe which has apparantely worked for some - but no luck there. Am in New Zealand. Model is sold here.
Ok, XP. You might want to read my previous rant to see what other info you didn't supply. Just look for the question marks.
Did you check if you have the latest firmware? See my previous rant. If you did do an update, some firmware makes a mess that requires a hard reset (stomp on the reset button). If you don't have the Belkin stuffed full of non-default settings, you might want to punch reset and start over.
What encryption (WEP, WPA, WPA, none)? See my previous rant.
Did you try it without any wireless encryption? See my previous rant.
Unplug the ethernet cable, open an MSDOS window, and run: ipconfig Belkin defaults to a gateway IP of 192.168.2.1. Is this what ipconfig is showing or something else? (Incidentally, I trashed about 30 minutes last week troubleshooting an HP wireless inkjet printer, only to find that it was connecting to the neighbors wide open wireless router). If ipconfig says 169.254.xxx.xxx, you're not getting a DHCP assigned IP address from the Belkin router.
XP has some connection progress diagnostics which can be enabled. Warning... they're verbose and ugly, but if you do enough digging, you can get a clue where it's screwing up. netsh ras set tracing * enabled netsh ras set tracing * disabled
Note that this only works with WZC running, and not some other connection manager. Ummm.... are you using WZC (Wireless Zero Config)?
You haven't supplied enough info to determine at what point the connection is failing. Basically, it's at one of these; 1. finding the driver 2. finding the adapter 3. association with the AP 4. negotiating a common encryption key 5. 802.1x authentication. 6. DHCP assigned IP address. The above verbose trace will show these in sequence. You can also get a rough idea by looking at the WZC connection status. If it says "Connected" under "View Available Networks", that really only means that you have successfully associated with the wireless access point. It does NOT mean that you have successfully negotiated a common encryption key, authenticated, or received a DHCP address. If it says connected, then try: ipconfig (did you get an IP other than 169.254.xxx.xxx)?? arp -a (is there an IP address associated with the MAC address of the wireless adapter)?
It's an Acer Aspire one - netbook model AOA 150 I believe I have done all the above (other than run ipconfig) - with WPA enabled and again disabled. With ethernet in and out - Says connected and light on router shows solid green - which it should if connected to internet, but won't access any web pages, outlook express or skype. Have looked for driver updates - none. ipconfig window flashes on then off before I can note anything. Have run cmd with belkin help desk talking me through. I can access internet with a plug in usb net connector as well as the ethernet. Just not with the built in wireless, yet it seems to access every other router I have tried. Belkin says it's an Acer problem, but so far I have had no response from Acer using their online help service. I have deleted all previous connections and reset router several times. In New Zealand.Think I've answered all you question marks.
Ok, I'll guess that this is an Intel 3945ABG MiniPCI card. If so (please verify even if you have open the cover and look at the card), I suggest you install the Intel Proset drivers instead of whatever Acer has to offer.
Suit yourself. I won't ask you to perform any un-natural acts, such as supplying what happens when you run the commands and tests I've suggested. See the question marks in my previous rants.
Again, connected only means that the wireless has associated with the SSID of your access point. It does NOT mean that it has successfully negotiated an encryption key, or authenticated with 802.1x.
See above URL if my guess as to your wireless card is correct.
I assumed that you knew how to run an MSDOS command. Try: Start -> Run -> cmd ifconfig
Belkin seems quite good at helping with problem running their hardware. They're useless at fixing problems that do NOT involve their hardware, such as the current problem with your Acer.
What's a USB net connector? Is that a wired USB to ethernet adapter?
Nope, but that's now your problem. The quality of my help will depend upon the clarity of your description and your ability to answer my questions. Sorry, but it's 1AM here, I'm dead tired, and am too lazy to repeat all the questions. You're not going to get anywhere unless you actually run some diagnostics and inspect your settings. I'm not going to be much help unless you supply the results.
For example, did you turn on creating an error log file with: netsh ras set tracing * enabled netsh ras set tracing * disabled and look at the log to see where the connection fails? Nope. (Note that you have to check "Let Windoze run the wireless settings" for this to work. Using Proset will clobber the logging, but Proset has it's own built in diagnostics.
Did you check if the wireless connection properties: Control Panel -> Network -> right click on the wireless device and select properties and check the TCP/IP settings to make sure they both say something like: "Get settings from server..."? What you're describing seems to suggest a DCHP failure of some sort.
Yes I have done above and everything else my limited technical ability will allow. USB connector is a wireless connector which I use to connect my old non-wireless Dell laptop to internet. Sorry but vI am unable to provide more information.
Sigh. Try: netsh interface ip show It will list a collection of interesting IP diagnostic commands most of which are made for Server 2003. The one's that are interesting for XP are: netsh interface ip show config netsh interface ip show dns
Same problem. I think he wanted: arp -a
It's working. The above shows that you're using DHCP to get your IP address and DNS address. The IP addresses are all correct.
It's also working. This is what the route table should look like when you have made a successful wireless network connection. More simply, the wireless is working, the TCP/IP stack is working, but something else is apparently giving you the impression that you can't browse the net. How are you determining that you can't get online? Perhaps your browser is set to "work offline"?
You're learning. Wireless troubleshooting is NOT easy, so don't be so hard on yourself. So, let's do some really basic testing (without the browser).
You didn't, but it's good to know. I rather like Atheros products (mostly because they contribute open source drivers to Linux). However, note that not everyone is happy with the card:
For XP: Latest Atheros driver from Acer is 184.108.40.2064. Latest Atheros driver from Atheros is 220.127.116.113 but this is the best I could find:
Save it for later or look for a better driver.
Nothing on the NZ Acer site for a wireless driver:
However, wireless is working, so leave it alone for now.
Ok, some simple tests:
Start -> run -> cmd ping 192.168.2.1 (ping the Belkin) Does it work?
ping 18.104.22.168 (ping my palatial office) Does that work?
Does that work?
All of these should return 4 lines of techy gibberish and declare 0% loss. Any lost packets or errors?
If all the above work, then something might be wrong with the browser. I'll need to know what browser you're using (IE8, Firefox, Opera, Safari, etc) and how you're testing it. Make sure you don't have them set to "work offline".
and see if you can get to the Belkin router configuration pages. If it's not the browser, then the next step will be to dive into the Belkin router settings.
I just had a horrible thought. By any chance to you have Norton Internet Security or Norton 360 installed? These [deleted expletive] programs have a misfeature where the block access to networks that the machine has not previously seen. When you replaced the router with a new device, Norton thinks it's an "unknown network" and blocks it if you fail to answer its questions correctly.
First - Am currently using MS security essentials as are 2 other computers I've tried but that connect. Also still connects to other routers I have tried on this computer. Browser makes no difference have tried Chrome and Firefox. N Definitely ot working offline - just will not display web pages, or connect skype or access email. On trying to access homepage it just says connecting for a minute or so then 'cannot display web page' shows To recap - will still connect to old router. and others. Have tried four other computers on new router - no problem so failure is between this Acer and new router only. Light on router shows color green - not flashing - which should mean connected to router and router to internet according to manual. Also works wirelessly with usb plug in connector.
Here's latest result from cmd/netsh interface ip show.
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Tony>netsh interface ip show config
Configuration for interface "Local Area Connection" DHCP enabled: Yes InterfaceMetric: 0 DNS servers configured through DHCP: 192.168.2.1 WINS servers configured through DHCP: None Register with which suffix: Primary only
Configuration for interface "Wireless Network Connection " DHCP enabled: Yes InterfaceMetric: 0 DNS servers configured through DHCP: 192.168.2.1 WINS servers configured through DHCP: None Register with which suffix: Primary only
C:\Documents and Settings\Tony> netsh interface ip show dns
Also have tried driver 22.214.171.1244 but it says something like not for atheros
5007EG. Have had to revert to 126.96.36.199
Hope I'm getting there. If you were any closer, I'd buy you a beer about now.
Good choice of anti-virus. Works for me and I like the price.
Please try the 3 ping tests I suggested in my previous rant. That will hopefully show where things are screwing up. It might be something simple, like DNS.
Basically, that says that there's a problem on the Acer Aspire One.
Perfect. It's working. Please use either the wireless or the ethernet cable, but not both at the same time. You indicated in your first message that everything works normally using the ethernet interface, but fails with wireless. Therefore, it's something in the wireless configuration, IP stack, firewall, routing, or whatever.
Also, run: ipconfig /displaydns and tell me if you get a long list of resolved addresses, or a short list (which suggests that DNS is having a bad day). No need to post the output. If the list looks like garbage, run: ipconfig /flushdns and try again after trying to look at some web pages.
You can also test DNS with nslookup. It should look something like this: c:\>nslookup Default Server: DD-WRT-built-14896 Address: 192.168.1.1 > set type=ANY >
Ok. Leave the driver alone and run the 3 ping tests I suggested.
I don't drink beer. This week, I'm into green teas.
You're sloooooowly eliminating potential culprits and will eventually hit something that should be obvious. Besides, I like mysteries. None of the diagnostic output you posted show anything wrong. Better yet, they show that you have successfully made a wireless connection, received DHCP supplied IP and DNS addresses, and built a working routing table. The 3 ping tests will tell me more.