802.11N Frustration!
So i configured about 47 Access points 2 years ago
AIR-LAP1141N-A-K9
WLC 7.0.98
Its all working fine, using channel extension. Then my company bought a small office and i got 4
AIR-LAP1141N-A-K9 (awesome deal i pulled) then ok, plugged in, downloaded the image, DNS is config, all took about 10 minutes, AP up and running
NOw the FRUSTRATION!!!!
I have spent 5 HOURS! trying to create the CHANNEL EXTENSION! how did i do that? I remember something about 40Mhz but the controller wont allow me.
All APs says, current channel XX (Extension: XX)
1- disable the radio
2- select 40 Mhz custom
then magically it would assign a extension to the channel and work at 300mbps
I CANNOT DO THIS! HOW?!!! PLEASEEEEEEEEEEE HELP!!! I GIVE UP!!!!!!!!
the worst! I have google this for like 4 hours, i cant fix it, i got tired now im stuck need second set of eyes!
found this:
https://supportforums.cisco.com/thread/335229
no help at all!
Vinay Saini said "
Jun 9, 2009 9:28 PM (in response to geetsingh22)
Re: client are not connected through 802.11n (AP 1140, WLC 5.2.178)
Hii ,
1. you need to configure WPA2+AES for the WLAN with WMM enabled on Qos page.
2. AFter doing this you will be able to connect at 144
3. For making 300 Mbps , Enable 40 Mhz operation for the AP
1. Go to AP radio setting page , disable radio
2. Make channel and power assignment as custom
3. Change the channel width to 40 Mhz
4. Enable radio
to make sure 40 mhz is enabled , go to AP console and issue "show controller d1"
you will see both primary and extended channel in use."
However the drop down only shows me 20MHZ. What the heck man! Maybe the controller is acting up and needs a reboot?
Similar Messages
-
802.11n not working.....6hrs of frustration!!!!!!!!!!!
I've spent basically all day yesterday on the phone with Apple tech support and even took my unit to an Apple store with no conclusion yet. Here's the deal...
I have a PC laptop (Windows XP SP2, non wireless)....D-Link cable modem running to my 802.11n base station.....then my base station running to my PC laptop. I get service fine on the laptop. In the same room (10 feet away) is my Powermac G5 (OSX 10.4.8 and all current software updates) with a airport card. I'm in an appt building so I know my airport card is working because I'm picking up other networks from other tenents. I have a green light on the base station but I can't connect for the life of me on my G5. I even connected the modem/base station to my mac and it recognizes it through the airport utility and I was able to name it and give it a password but even directly connected to my G5 my wireless card isn't picking up the signal..........PLEASE HELP!!!!!! Forgot to add....I took the base station to the apple store and it worked there! Do you think it's the D-Link modem?The Airport Extreme defaults to a 10.1.1.x address.
Most PC-Based Wireless hubs distribute 192.168.1.x
addresses. Set your Airport Extreme to redistribute
192.168.1.x addresses, and you will be able to
connect.
MacBook T2700
2gHz, 12GB, 160G Windows XP Pro Dual
Boot with latest OSX
ummm...no..that should not matter at all -
How can I make by MB Pro work on 802.11n wireless?
A month ago we bought a new MacBook and in conjunction with that purchase we upgraded from a Linksys 802.11g to the AirPort Extreme 802.11n Wi-Fi Wireless Base Station. We wanted to have the 802.11n access for the new MacBook and for our other laptop (mine) - a MacBook Pro 1.83 GHz Intel Core Duo 15" purchased in March 2006.
I just figured there would be some downloadable upgrade to take my MacBook Pro from 802.11g to 802.11n ... but that does not appear to be the case. (Boy, do I feel stupid.)
So - the question: What do i need to do to get my MacBook Pro to work fully on the 802.11n standard? Do I need something new physically installed in the laptop? Is there a downloadable upgrade or something on the CD that came with the Airport Extreme unit that I can install? Help!
I really hope I didn't buy a $200 router that I can never fully utilize - there has to be some way to upgrade from a/b/g to a/b/g/n, right?
Thanks to any and all who can provide guidance on this.
MacBook Pro 1.83 GHz Intel Core Duo Mac OS X (10.4.10) puchased in March 2006Thanks for the tip on the upgrade. I upgraded to Airport Utility 5.1 (I had 5.0) and then did the firmware upgrade at the link you provided. So, all is installed, and I restarted the MB Pro, but my Network Utility still shows that I have only 802.11 a/b/g capability.
Do I need to take other steps? Do I need to anything like turn my cable modem or Airport Extreme unit on or off or something like that?
I am really frustrated and confused on this. Is it possible that my MB Pro that is all of 15 months old can't upgrade to 802.11n? I know that the new Inel Core 2 Duo MB Pros have the 802.11n built in. My MB Pro is the older Intel Core Duo (not "Core 2 Duo").
Anyone else have ideas? Thanks!
MacBook Pro 1.83 GHz Intel Core Duo Mac OS X (10.4.10) puchased in March 2006 -
I have been using Apple technology for about 10 years starting with 1st generation iPods and our house now includes a 5 year old iMac, all versions of iPods and touches, Apple TVs (both generations) and most recently an iPad 2. I have always told family and friends that Apple technology just works. Unfortunately that stopped today. I bought a new Airport Express 802.11n to use for AirTunes around my new pool. I set it up from my iMac and accidentally used it to connect my iMac to the network for a short time. Now I can no longer connect the iMac to the network using a hard wired Ethernet cable. I have tried resetting everything possible, from hubs to routers to the Mac itself and it just will not connect to the network through Ethernet any longer. I am now a very frustrated Apple user especially when the support site says I can't use the fast path support because my product was manufactured 5 years ago...I just bought it at BestBuy yesterday. All other computers and itechnology in the house are connecting via wifi and Ethernet without any issue except from my new iMac boat anchor. Anybody who can help me??? Thanks
John, thanks for the email so quickly.
I too hope I haven't tried "everything" either but I am reasonably technical. I had done what you suggested to do before but I did both again.
Ethernet is yellow in the left side bar. In the right pane it's status says Connected but then below it says "Ethernet has a self-assigned IP address and will not be able to connect to the Internet."
I have tried the assist me menu and Network Status has Ethernet Green, Network settings Yellow, ISP Green, and Internet and Server Red and Failed for both. I have turned things off and on, checked cables, deleted all locations and tried restting them up but to no avail. I even disconnected everything and connected the mac directly into the cable modem itself and the thing still will not connect.
Thoughts??? -
Mac Mini (2007 model) Ethernet and 802.11N dead
Wow, talk about frustrating...my 13 month old 2007-model Mac Mini just crapped out with a couple of issues. The Ethernet networking reports the cable is unplugged, even though it's not, and the 802.11 wireless networking won't connect at N speeds. Of my four Macs, this was the only one without AppleCare, so no warranty help to be had.
Anyways, to troubleshoot the system, I've verified that the Ethernet cable I am using provides connectivity on another machine, and that other machines in the same workspace can connect to the 802.11n router via "n" speeds. So it's not anything external to the Mac Mini.
I also booted from a different OS X version via external USB drive, and the Ethernet and Wireless "n" still display the same symptoms. So it sounds like hardware, since a software glitch shouldn't appear with a different boot drive, right?
Verify disk and repair permissions also performed, with no anomalies noted.
System Profiler shows the Ethernet port is there, but in following troubleshooting "cable unplugged" errors tips in another thread I tried removing it from the networking pref pane, and re-adding it, but Ethernet doesn't show as an addable option anymore.
I am able to connect via 802.11g, so the machine's not totally dead connectivity-wise, but as home theater media server, I am sure going to miss the rapid file transfer rates of Ethernet or "n" wireless.
So, before I write this machine off as crippled, can anyone think of anything else I might try to get Ethernet working again? I suppose a USB-to-ethernet dongle would be better than Wireless-"g", but it's still less than ideal.
On another note, oddly, several of my programs started complaining about not being registered, which is what lead me to try permissions and disk verifications. Pretty strange.
Any ideas appreciated.Ah, you're right about the N not being supported. Color me stupid on that one...silly me assumed that since I'd only had it a year, and N was around on my other Macs purchased around then, that it was there, but of course the design was a year old already. I'll update the thread post to drop that part.
As for the cable, I sort of tried two other cables already. My actual setup is to run the Mini to a gigabit switch, then the switch runs a CAT6 cable 50' to the router. I used two different cables out of the switch, and then plugged the long run directly into the Mini. No go. I guess not a big issue to unplug the Mini and move it to another room. I'll give it a go, but take note that it's been working fine on this same cable/switch/router set-up for a year. Odd that it would suddenly change.
Thanks for the tips, I'll post back with results when I get home and can check it out. -
USB 2 HD connected to AirMac 802.11n station
Since I got my AirMac 802.11n base station I had my external HD connected to it and felt it was sort of slow that way.
Today, when I had to copy like 20,000 files over I was getting frustrated and unmounted it wirelessly and connected it directly to the USB 2 port on my MBP.
As suspected, the direct connect transfer speed is approximately 1 jillion times as fast.
So unless you have multiple computers and absolutely need to mount your HD wirelessly I strongly recommend directly connecting it.
dougThis is quite normal. Since you're using a wireless interface, you'll probably get 1/5 the speed as a direct connection with USB.
My setup with a USB disk gets about 80-130mbs wirelessly vs. 350-380 through a direct USB connection.
For bulk file operations, video conversions and backups, I connect directly to the USB. If I'm watching videos or editing files wirelessly through an Airport Disk, it's always on the Airport Extreme.
I guess what I'm saying is that you're right and that what you're seeing is normal.
Best of luck!
Chris
Message was edited by: MegaJustice -
USB Printing AirPort Extreme 802.11n
I've upgraded to the new AirPort Extreme 802.11n base station and am having troubles printing to printers that worked fine with my previous AirPort Extreme 802.11g base station.
Both USB printers are detectable for set-up in the Print & Fax Preference tab and can be printed to when hooked directly to my computer. They are also detectable for set-up in the Print & Fax Preference tab when hooked via the base station.
So, all set-up and settings are fine. The issue I am having which never occurred before is that the file is sent to the queue but is immediately labeled as stopped and will not print no matter what I try.
I've configured, reconfigured, reset,you name it but with no luck.
does anyone have any answers out there. Please help...I have had the same issue repeatedly after upgrading to Leopard. I can no longer use my printer (Brother HL-2070N the "network ready one") with my airport extreme router. It used to show up before I updated to 10.5.2, now I can't even get it to show up at all. I reset the base station, unplugged, and then re-plugged in the printer, nothing worked. Then I tried to just delete it from my list of printers and re-add it, but now my computer can't find it! I didn't change anything on my network at all, and I had literally printed something just 10 minutes before I applied the update. Very frustrating for a $180 router.
-
Configuring WDS w/ Airport Extreme Dual-Band 802.11n & Express 802.11g
I currently have an Airport Extreme Dual-Band 802.11n Model: A1301 (located downstairs) and an older Airport Express 802.11g Model: A1084 (located upstairs) which I had been using to stream iTunes to my upstairs stereo (which worked flawlessly). Recently a friend of mine recommended that I reconfigure my network to a Wireless Distribution System setup which would allow me to create a remote wireless node which improves my wireless signal strength upstairs, allows an interface to Airplay to play our music from our iPod's/Pad's and also provides an hard-wired Ethernet connection for my newly delivered Network Extender for my cell phone. So I followed the URL: support.apple.com/kb/HT4262 to assist in this conversion and found that I was unable to configure my network as desired. While this documentation is very good, there is one snafu that I worked out that finally allowed a successful setup. Follow the instructions for:
- Connecting a WDS main base station to the Internet
- Configuring a WDS main base station
- Configuring a WDS remote base station (See last line of instructions for the correct WDS Main ID)
Ensure all Wi-Fi base stations are powered on and allow them time to appear in the AirPort Menu Extra.
From the AirPort Menu Extra, select an 802.11g Wi-Fi base station to configure as a WDS remote.
In AirPort Utility, select the WDS remote Wi-Fi base station in the Base Station Chooser, and click Manual Setup.
Select the AirPort icon from the Toolbar, and click on the Wireless tab.
From Wireless Mode select Participate in a WDS network.
Click on the WDS tab.
From WDS Mode, select WDS remote.
Enable Allow wireless clients (see the first note below).
If not already supplied, enter the 2.4Ghz AirPort ID of the WDS main, then click Update.
There are two Apple ID's for the dual-band Extreme (2.4 & 5.0Ghz). Be sure to use the 2.4Ghz ID which is listed under the "Summary Tab" of the utility. What is confusing is that in the AirPort Utility, when you position the mouse cursor over the graphic of the Extreme on the left-hand side of the GUI, you are presented with a yellow dialog box which displays the 5Ghz ID and this can be misleading especially when you are trying to connect to an older 2.4Ghz Express ...My Express is the A1264 802.11n model. My Extreme is the A1354 model.
The most crucial issue is the the Tivo, because the Premiere only works with Ethernet (I dont' have and wont' buy the upgraded wireless doohickey), but of course I would prefer that the Express also act to extend the signal, and I particularly want it do so using WEP access (or nothing, see below), since I have a second Tivo which ONLY works wirelessly and which ONLY works using WEP, not WPA.
Since there were so many different issues and needs going on, I was excited about the Dual Band because it meant I could potentially get 5G speeds for my iPad and perhaps the Tivo Premiere connection, while allowing a completely separate band for the OLD Tivo.
The other option I've been trying out (to accommodate the Tivo2 that can't handle WEP) is having no security, but making the networks hidden.
A third option I tried to make work was to create a "guest network" for just the Tivo2.
But what I'm finding out (it's what I always struggle with...networking is a nightmare.) is that if you take one from Column A, Column B disappears, so to speak.
The way it used to work on the non-dual band Extreme was as I mapped above, and the Tivo2 and my iPad used the wireless signal with no problem while the Express was Ethernet connected to the TivoPremiere, but it did so using WDS, which doesn't even seem to exist as a possibility, forget teh fact that it undermines the speed boost (so I read)
I've frankly never been able to understand the differences between the various modes and structures, and believe it or not I'm very smart and very comfortable with computers and Macs, having worked on them for 25 years.
And one of the biggest reasons I've had such a hard time is because of the many times that I have updated after making changes, Airport Utility tells me it worked, but nothing happens and then after too much frustration I end up unplugging and shutting down every single piece of equipment and rebooting everything and then it DOES work. Sometimes. But I can't be doing that every time I make one tweak, I'll go insane!
And the number of pin-resets I've done on the Express, the Dual band, and even the cable modem would make your head spin!
So there's my story. Kinda. Does it make any sense? At least in terms of my goals?
Your help is more appreciated than you can imagine. -
AEBS 802.11n, TC and APXn with 7.3.1 is very flaky indeed - cant connect -
HI Guys I think many of you on these forums have posted because you are having joyless experiences with the new APX 802.11n, the AEBSn and the TC not able to be managed via the AIRPORT UTILITY.app v5.3.2 with firmware 7.3.1 in the former devices. After a search there's many of these posts with people with the same issues.
I have these devices in my place so I have had lost of experience configuring these over the years:
1 x 802.11n AEBS, 1 x TC, 1 xUFO white AEBS, 2 x APXg's and lastly the problematic 1 x APX802.11n (one subnet and 2 x networks 2.4Ghz and 5 Ghz)
I am at my wits ends trying to get the new APXn regularly responding to the AP utility.app (error reading configuration).
I have tried most of the remedies on these forums but they do not consistently solve the problems of the APX not responding to the AP utility.None of these have consistently worked:
• trying to factory reset it using the POWER ON+RESET and waiting for the amber flashes then green - butt this procedure NEVER WORKS to factory reset!
• using the reset button in any form (it doesn't do anything)
• connection through ethernet (sometimes works ).
• takes long to power up (than the older 802.11g)
• rest APXn back to factory defaults through the AP utility then ...
• downloaded 7.3 firmware - worse and wont work
• lastly I found that RESET+POWER ON then wait for 20 secs as as it powers up DEPRESS the RESET again and then it becomes readable.
Additionally, I have been unsuccessful in getting PORT FORWARDINg to work at all for the AEBS 802.11n with and without the TC in the mix. I had this working for several years with the White UFO AEBS ... It beats me.
I think the firmware is very very flaky and i have no resolutions for these recent problems.
Hope for a fix soon.
I will be polling these forums for any clues.
wHi Guys
REgarding the APXn's (802.11N Airport express) inability to consistently be seen by the Airport Utility.
this just worked finally for me now and have tested this 7 times and all seems ok now..
Simply: when APXN in list, save configs, reset to factordeafuts, downgrade to 7.3, upgrade to 7.3 and reinstate .configs.
UPdate: a probable work instruction that seems to consistently work.
Here is the work instruction i used.
(1) turn off all other WIFI base stations where you are that you can. (important I believe)
(2) turn off airport in your mac
(3) connect troublesome APXN to mac via ETHERNET cable. Set DHCP on your mac or some address in IPV4
(4) power off and on the APXn (yes again )
(5) whilst it is powering up, use a pen of toothpick to RESET the APXn again (i think this causes something to move around inside the magic-ware)
(6) the light will flash amber (no network to connect to)
(7) launch /utilities/airport utility.app
(8) the one and only APXn appears in the list
(8.5) optional: (cross fingers and legs :))
(9) when profile comes back, use FILE/SAVE a COPY AS to the ~/desktop to save the complete profiles and settings of what you have in there currently.
(10) select the one and only APXn and perform a airport utility.app/base station/ RESET TO FACTORY DEFAULTS - and wait for 30 secs and then it will restart
(11) when complete, quit and relaunch the /utilities/airport utility.app
(12) the APXN will be as when you bought it (pristine and no stuff in it from you)
(13) connect your mac back to internet via ethernet if possible. (avoid the wireless just to be sure but at this stage you could reinstate all your exiting wireless infrastructure)
(14) select the one and only APXn AGAIN and perform a airport utility/base station/ UPLOAD FIRMWARE and select version 7.3 (back level) . THe firmware will load into APXn 0%-100% guage and then it will restart.
(15) when complete, quit and relaunch the /utilities/airport utility.app and it will warn that one of the basestations (the only on the list - the APXN) has later FIRMWARE available for it. [This is 7.3.1].
(16) reply OK to UPLOAD NEW 7.3.1 firmware. (yes yes I realise ths sounds silly but it works ok ) 7.3.1 Firmware will up load into the APXN as above and restart will take place.. so say 120 seconds.
(17) quit and relaunch the /utilities/airport utility.app. THE APXN will appear as before as now with 7.3.1.
(18) just to make sure, (we're not quite finished), remove the ETHERNET cable. If not already done form previous optional step, ENABLE the AIRPORT (WIFI) on your mac.
(19) power OFF then power ON the APXn.. wait for the usual 70 secs..
(20) Again, to be sure, QUIT and RESTART the /utilities/airport utility.app, the APX as factory default with amber icon will appear in the list [along wit the rest of your apple airport base stations).
(21) Select it in the list fo MANUAL and the configuration will be read quickly.
(22) do this (steps 18-21) 3 or 4 times to see that it is consistent. (I this it 7 before posting this).
last step...
• select the APXN (default settings) and IMPORT the save configuration file (~/desktop/nnn.baseconfig) (all it) from the ~/desktop. Ignore any errors (untick them), add a password for the base station and UPDATE!
• wait for the usual 70 secs.
• without quitting the /utilities/airport utility.app, the UPDATED APXN with your configuration will be in the list.
NOw try and selectit for manual and it should respond in time without timing out.
Test by powering off and removing from wall socket and moving around too to make sure you can SEE it in the /utilities/airport utility.app and select it for MANUAL CONFIGURATION.
After many days of frustration on weekend and over night, this appears to have worked ok for me.
(now to work out the AEBSn port forwarding issue - it wont work).
HTH
w -
AEBS/802.11n@7.3.1= no port forwarding on port 21 (FTP) but 7.2.1 does!
HI guys, this is of interest to those of you with firmware 7.3.1 on your Airport Extreme Base Station 802.11n (AEBSn) that have been unsuccessful getting FTP port forwarding (port mapping) to work (that is with PORT 21 mainly.
After some frustrating days on weekend with issues with APXn and TC and this AEBSn, I have found that *_falling back to firmware 7.2.1 for the AEBSn allows the port forwarding for FTP (port 21) to work ok.*_
Note that at firmware 7.3.1, most uncommon ports are forwarded ok, For example Vuze random ports for BT incoming such as port 43434 or what ever you use are mapped ok at firmware 7.3.1.
However ports such as 20 and 21 (FTP) in ver7.3.1 are not forwarded at all. I don't know why.
So as a workaround for port forwarding, using AEBSn firmware ver7.2.1 works fine.
(use *airport utility/base station/upload firmware* while connected to the broadband and you get a list of available firmware for that airport device)
I have this working as the main router for ADSL on a 5Ghz 802.11n network with a time capsule (at firmware 7.3.1 ) and an airport express 802.11n (APXn) at firmware 7.3.1.
Please post if you have been able to get FTP port forwarding (port 21) aka port mapping working on an AEBSn at firmware 7.3.1.
I hope there is an update soon for the newer airports as they are not as reliable as the previous versions IMHO.
wHi,
I have the same problem. When I downgrade to 7.2.1 FTP and VPN works fine. But then I have a problem with stablility of the AEBS. I can not believe that Apple is not able to fix this problem. Have you guys any issues with stability problem running 7.2.1 I need a stable system as we running a kerio mailserver. Just in that moment I can not access the mail server as the internet is down again. Hope anybody has a solution for this. -
MacBook Pro - 802.11n, WPA2-Personal and Time Capsules
I recently moved to using 802.11n (5GHZ) mode on my Time Capsule using WPA2-Personal security. I am unable to connect to the wireless network which is extremely frustrating since this is all Apple hardware. I have no problem connecting to the 802.11n 5GZ network using one of my PCs.
My MacBook Pro has the latest software updates available and does have 802.11n enabled.
I have been looking for similar issues on the forum and have tried a few things that were suggested by others, but nothing works. I've reset the router. Reset the SMU. Haven't reset NVRAM yet.
I have a mix of Apple and PC hardware that is connecting to this network. My 24" Intel iMac (Core 2 Duo) connects just fine.
I'm hoping there is a GURU on this forum that can assist me.
Thanks,
J.d.I would try:
1. Examine your system.log for the error you are getting, if you cannot authenticate with the router it will say why. Go to the Apple icon, select "About this Mac", select "more info" button in the center, select "Log" under Software on the left panel side, select "system.log" then scroll to the bottom, look for errors in the log related to "airport" or 802.11...
2. Go to Finder/Utilities, pull up keychain access.app, click on System on the left, you should see an entry for your WIFI network, delete that entry, close Keychain access.
3. Try removing, reboot then re-add your Aiport entry. Go to System Parameters, Network, highlight "Airport" click on the minus button and remove it. Reboot your computer. When it comes back up go back to System Parameters, Network, then click on the button and re-add the Airport, when it says Airport 2, over write that with just "Airport", then click on Advanced, click on button to add the Preferred Network back in, type the name of the SSID on your router, then select WPA2 Personal from the drop down menu type. You can also display the password to confirm it matches what you input in the router for the password for WPA2 Personal.
Under TCP/IP, if you are getting a private IP address from the router via DHCP, then set IPv4 to DHCP. I would not use IPv6 for time being, set that to Off. Next click on your DNS and input your DNS if not automatically filled in by the router with DHCP, I always like to add a DNS not provided by the router that way if it fails or you go to Starbucks you will always have a DNS entry that works, I would input OpenDNS's entries, so those would be under IPv4:
208.67.222.222 and other is
208.67.220.220
So to connect, your computer needs to have an IP address, either DHCP or manually input (like 192.168.1.xxx) etc.
Next you need a DNS entry if not provided for by your router (should be if it is dishing out DHCP client addresses).
WINS and Proxies are only used in corporate environments where they are using a windows domain and/or proxy servers as a gateway to the WAN.
WPA2 Personal offers much better security than WPA or WEP shared, if you use a password make it at least 8 characters in length 10 is better. The longer you make it the higher the security, but it must match exactly what the password was set for WPA2 on the router.
TO make sure you are not having signal/noise problems get as close to your router as you can to establish the connection once that is done you can move farther away. -
AE 802.11n Keeps Dropping Security
I thought the recent AE update fixed this but this frustrating problem keeps happening. It seems that every time I restart my MPB my new AE ignores my setting for WPA2 and keeps defaulting to "no security" and leaving my base station wide open. Does anyone have a work-around for this? I've tried removing the plist file but the same problem arises. I've got my basestation set to 802.11n only so I'm probably OK in the near term but then again, who knows. Maybe it is ignoring that setting as well.
Christopher,
The problem does not come from your laptop. There is a bug on the base station. Many people are reporting that their WPA network is indeed a no security network. Even if the AirPort utility says your WPA is on, it is wrong. I've posted more details about my experience on a thread call "SECURITY BUG etc. etc..." in this forum. I'll go throught some tests tomorrow to (try) identify the source. But so far, no solution.
To be continued... -
802.11n card in an older MacBook Pro
I have looked around & it seems you can buy an Airport Extreme 802.11n card from the Fastmac online store. I watched the instructional video on Macworld of the guy installing it & it seems pretty easy & the performance improved greatly in his laptop. Before I follow through with this, I just wanted to check & see if anyone else has done this self-installed upgrade & how it worked out for them. I want to call Apple to see if they will do it for me, but I don't believe they will. My laptop is still under warranty (ends in mid 2009) & I would hate to void that warranty, but if Apple wont give me an upgrade that was available a year after I bought my laptop, then I will have to do it myself. I love Apple, but sometimes they just seem to zip by too fast & forget about their previous models & that customers still own them. So if anyone could shed some light on the matter, it would be really great. Thanks.
Well, I am not looking for a faster connection with file transfers within the house, what I am looking for is a solid, stable, consistent, connection. We just bought a new NetGear wireless router & the PC that is hard wired into it works fine, we were hoping that it would output a strong signal throughout the house for my laptop & the Wii & DS's. The Wii & the DS's work great, but for some reason my laptop can't keep the connection for more than 5 minutes at a time. It is VERY frustrating. I have read in several forums, where people have had the same problem, the MacBook Pro (older model) just can't hold onto a connection for more than a few minutes. I was in the same room as the router & my airport bars would go from 4, to 2, to 1 & then no signal & would have to search for an access point & then connect to it, only to have go through that same mess all over again. This is why I wanted to switch to a "n" card instead of "g". So that I would have a more stable connection. The router says that the "g" connection is supported up to a few hundred feet away from the router... I'm lucky if I keep a connection when I am sitting on a chair with the router underneath me.
-
AirPort Extreme 802.11n 4% Packet Loss
I have three laptops (Macbook, HP, and ThinkPad), an iPhone 4, iPad, and a Wii on my wireless network. I replaced an old Linksys 802.11g access point and router with a new Airport Extreme 802.11n.
Everything has been working fairly good except my ThinkPad. The TP has a ThinkPad 11b/g Wireless LAN Mini PCI Express Adapter III card and can connect to everything from coffee shop wireless to my Cisco WLAN using PEAP/WPA2 at work without skipping a beat.
But here at home, with my new Airport - I'm losing about 4% of the pings I run and it'll drop my connection without warning. Almost like the WPA key is rotating, then just dies.
The MacBook has an 802.11n card and can run extended ping tests without dropping a single one.
The HP has an Intel centrino abg card and runs 0% loss as well.
If I connect my old Linksys back up - I get 0% packet loss on WPA2 again, but to the AirPort - 4%.
It's making my wireless network exceptionally frustrating.This is what I get when I'm connected to the main wireless network using 802.11g WPA2 (AES or TKIP).
If you'd like to do this test, simply type this command from a command line (or terminal on an OS X computer)
ping -t 10.0.1.1
And when you're done, type CTRL+C to get the statistics. You can let it run for hours and come back.
ping -t 10.0.1.1
Request timed out.
Request timed out.
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Ping statistics for 10.0.1.1:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms</div>
Now, if I connect to the guest network or my Linksys WRT-G54, I get this:
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Reply from 10.0.1.1: bytes=32 time<1ms TTL=255
Ping statistics for 10.0.1.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms</div>
Not a single drop... and I'm still pinging the AirPort's IP address, so I know it's not the device itself dropping pings. It must be something funky with my T400's wireless card and the private network, nothing else makes sense. -
Airport Extreme (802.11n dual) breaks network HP photosmart 3210 scanning
I just "upgraded" from a Netgear to a new April 2009 Airport Extreme Base Station (802.11n dual). With the latest HP software etc the HP photosmart 3210 all-in-one scanner (connected via network to the router) works fine with my macs (a bunch of 10.5 machines), but when I swap out and use the new Apple Router the Scanning hanges and a message pops up on HP Scan Pro SW "Error (Sorry, scanner could not be initialized. An error has occurred communicating with the scanner.)" I reinstalled the HP SW and re-added the printer - no change.
Printing is fine - and scanning is fine when I go back to my old router. This looks like a router firmware issue, I'm probably going to have to return the router - bummer - anybody have this issue or can help?Thanks for the idea, but my printer is connected by ethernet to the router and desktop computers - (I haven't tried wireless scanning with my laptops). I wouldn't think that wireless settings would impact the wired part of the router - but you never know.
It is frustrating how many incompatibility there are from router to router I don't understand why there can't be a standard and everyone sticks to it. (another example, google maps detailed zooming in and out will always freeze my netgear router - which is one reason I went to the apple router!)
Maybe you are looking for
-
Item Usage in Item Category Determination?
What is Item Usage in Item Category Determiantion?
-
It's a recent problem. My default view now keeps coming up as "List", sorted z-a. And it returns to that even when I simply go up a directory level in the same transaction! I've deleted my Firefox prefs files as in the instructions for settings probl
-
Hi all, if you know any tables for contract data(For Contract report), please tell me..... Thanks, kishore.
-
Background noise with electric guitar
Hi, I'm playing my les paul into a cheap (like $100) m-audio fast track interface, and picking up the signal with the usb on my macbook pro. I am using the audio port to send the signal to my line 6 amp. I am quite sure i have set all the necessary s
-
Embed + compiler define works different with air 3.7+ comparing to 3.5
Hello. I've noticed that new compiler works differently when using construct Embed with conditional compilation (comoiler define option). It looks like new compiler always embeds files in output swf even if Embed construct is used in dead code. Here