Error -6722

I have an airport extreme n that is running fine. But I wanted to check some settings so I ran Airport Utility [5.2.2 (522.3)] to get them. It discovered the base station just fine. It returned the name, IP, software version (7.2.1) and airport ID. But when I click either "continue" or "manual setup" I get this: "An error occurred while reading the configuration. Please make sure your AirPort base station is plugged in and in range of your computer or connected via Ethernet and try again (-6722)" My base station is plugged in, it is in range and it is connected via Ethernet; otherwise, you wouldn't be reading this. Anybody have any idea what's going on?

I forgot to update this. I ended up unplugging EVERYTHING. Apple TV, wireless router, etc.... When it all rebooted, it worked again.

Similar Messages

HT204291 at times error 6722 appears while connecting to airplay device "apple tv"

at times error 6722 appears while connecting to airplay device "apple tv". i have restarted the apple tv several times but it keeps doing the same thing, at times the pictures appears without sound from my sound system. what is the problem, my apple tv and macbook pro is new?

As an update, tried to connect from a Macbook Pro with an older ITunes and all devices show up, connect and work fine.

Error (-6722) occurred while trying to access the Apple Wireless device

I receive the following error when I press 'manual setup' or 'continue' from within the airport utility:
"An error ocurred while trying to access the Apple wireless device. Make sure your network connection is valid and try again
Error -6722"
Everything is working on the Airport express but I can't run the utility. Should I hazard a reset of the device to factory settings?

Aaaaaaand as I was writing that, I managed to fix it. Not sure how exactly. The variables that were used that worked:
On windows, running AU 5.5.2, right clicking upload firmware in the device list, choosing other, selecting a random firmware other than 7.3 (I think i ended up using 7.4.2) and clicking upload. Instead of trying to communicate with the APExpress, it directly uploaded the firmware and then it restarted, I got a crazy amber blink cycle I have never seen before (Three fast long blinks, and the three short fast blinks, repeat). Then it restarted and it was back to normal. Woohoo! There goes 5 hours of my life.

Error -6722 occurred while updating

Time Machine needed an update. While updating fimware, an error -6722 occurred. Time Machine light is green and seems to be working fine. Backing up ok. Do I need to worry about this?

On your Mac....
Open Macintosh HD > Applications > Utilities > AirPort Utility
Click on the Time Capsule icon
Check to see which version of firmware that you have installed
The most up to date version is 7.6.4
If you need to update, temporarily connect your Mac to one of the LAN <-> ports on the Time Capsule using an Ethernet cable and try the update that way.
Once the Time Capsule has been updated, you can disconnect the Ethernet cable

What is error -6722

I am recieving message that states
An error occured while updating the firmware. -6722

Try power off the AirPort and wait a minute or two, then power it back up.

APE & iTunes "Unknown Error" when trying to connect to remote speakers.

This is a new setup using a pre-existing windows PC and Netgrear router.
The APE appears to be set-up correctly per the instructions to set up as a client. It appears in iTunes and I can selet it. When I do, the progress bar reads "connectinfg to.." for about 30 seconds, then: " An error occurred when connecting ..." ending with "An unknown error occurred (-15000)"
The log in the AirPort Utility reads like this:
AirTunes stream from 192.168.1.11 started.
AirTunes time sync receive error:-6722
AirTunes too many time sync negotiate failures: 64/0/0/64
AirTunes stream from 192/168.1.11 stopped
Any ideas?
Bob

edit: try again
see if this article helps.

AirPlay Screen Mirroring (Mavericks) disconnects frequently with "Feedback taking too long to send" message

My company has several TVs with AppleTVs (3rd generation units) connected in our conference rooms so we can "Screen Mirror" our Mac laptops via AirPlay during meetings. Many employees have complained that AirPlay Screen Mirroring drops frequently during meetings for no apparent reason.
In attempts to determine the cause of the issue, I removed the AppleTV units from Wi-Fi and hard-wired them all to the LAN (100Mbps/Full duplex, no switchport errors seen on the Cisco switch). I upgraded the AppleTVs to the latest firmware. I had our AppleTV users ensure they were running MacOS Mavericks with the latest software updates installed. I had the Mac laptops hard-wired into the LAN during meetings in the conference rooms. None of these changes resolved the AirPlay issue.
I reviewed the MacOS "/var/log/system.log" file from the laptops of several users that reported issues. I found a pattern that seemed to indicate that the "coreaudiod" process reported "Feedback taking too long to send" several times before the AppleTV connection was terminated. Also, from a network trace (using "tcpdump") taken during an unexpected AirPlay Screen Mirroring disconnection, I could see that the Mac laptop sent a TCP FIN packet to the AppleTV unit (this would indicate that the MacOS laptop initiated the closing of the AirPlay connection).
I have included the relevant log file entries below. Please note that the LAN internal to our company is "solid" and there have been no connectivity issues detected or reported during the times the AirPlay sessions were disconnected.
I believe I have found a workaround to this issue. By going into "System Preferences", "Sound" and then changing the "Output" device BACK to the "Internal Speakers" (rather than the AirPlay destination), the AirPlay Screen Monitoring connection seems to remain stable.
My questions are:
- is anyone else experiencing this type of problem? any other solutions recommended?
- is there a way to change the AirPlay defaults so that Screen Mirroring only sends the video (not audio)?
- does anyone know what the log file entries indicate (like, what does "Feedback taking too long to send...." mean)?
- any fix planned for this issue?
From: "/var/log/system.log":
Jan 16 10:50:16 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:16.454404 AM [AirPlay] ### Feedback taking too long to send (1 seconds, 1 total)
Jan 16 10:50:18 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:18.524517 AM [AirPlay] ### Feedback taking too long to send (4 seconds, 2 total)
Jan 16 10:50:20 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:20.533639 AM [AirPlay] ### Feedback taking too long to send (6 seconds, 3 total)
Jan 16 10:50:22 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:22.548168 AM [AirPlay] ### Feedback taking too long to send (8 seconds, 4 total)
Jan 16 10:50:24 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:24.554522 AM [AirPlay] ### Feedback taking too long to send (10 seconds, 5 total)
Jan 16 10:50:24 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:24.554809 AM [AirPlay] ### Report network status (3, en0) failed: 1/0x1 kCFHostErrorHostNotFound / kCFStreamErrorSOCKSSubDomainVersionCode / kCFStreamErrorSOCKS5BadResponseAddr / kCFStreamErrorDomainPOSIX / evtNotEnb / siInitSDTblErr / kUSBPending / dsBusError / kStatusIsError / kOTSerialSwOverRunErr / cdevResErr / EPERM
Jan 16 10:50:26 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:26.545531 AM [AirPlay] ### Feedback taking too long to send (12 seconds, 6 total)
Jan 16 10:50:28 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:28.559050 AM [AirPlay] ### Feedback taking too long to send (14 seconds, 7 total)
Jan 16 10:50:30 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:30.628868 AM [AirPlay] ### Feedback taking too long to send (16 seconds, 8 total)
Jan 16 10:50:32 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:32.655638 AM [AirPlay] ### Feedback taking too long to send (18 seconds, 9 total)
Jan 16 10:50:34 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:34.641952 AM [AirPlay] ### Feedback taking too long to send (20 seconds, 10 total)
Jan 16 10:50:36 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:36.659854 AM [AirPlay] ### Feedback taking too long to send (22 seconds, 11 total)
Jan 16 10:50:38 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:38.653594 AM [AirPlay] ### Feedback taking too long to send (24 seconds, 12 total)
Jan 16 10:50:40 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:40.659279 AM [AirPlay] ### Feedback taking too long to send (26 seconds, 13 total)
Jan 16 10:50:42 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:42.745549 AM [AirPlay] ### Feedback taking too long to send (28 seconds, 14 total)
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.532853 AM [AirPlay] ### Endpoint "AppleTV" feedback error: -6722/0xFFFFE5BE kTimeoutErr
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.533151 AM [AirPlay] ### Feedback failed: -6722/0xFFFFE5BE kTimeoutErr
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.533273 AM [AirPlay] ### Error with endpoint "AppleTV": -6722/0xFFFFE5BE kTimeoutErr
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.533427 AM [BonjourBrowser] Reconfirming PTR for AppleTV._airplay._tcp.local. on en0
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.533588 AM [BonjourBrowser] Reconfirming PTR for 9C207BBD8EA1@AppleTV._raop._tcp.local. on en0
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.533839 AM [AirPlay] ### AirPlay report: Network dead for 10+ seconds after 159 seconds, screen, nm "AppleTV", tp WiFi, md AppleTV3,1, sv 190.9, rt 0, fu 0, rssi -54
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.534104 AM [AirPlay] ### Report network status (5, en0) failed: 1/0x1 kCFHostErrorHostNotFound / kCFStreamErrorSOCKSSubDomainVersionCode / kCFStreamErrorSOCKS5BadResponseAddr / kCFStreamErrorDomainPOSIX / evtNotEnb / siInitSDTblErr / kUSBPending / dsBusError / kStatusIsError / kOTSerialSwOverRunErr / cdevResErr / EPERM
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.534315 AM [AirPlay] Deactivating virtual display stream for quiesce
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.543682 AM [AirPlayScreenClient] Stopping session
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.543815 AM [AirPlay] Quiescing endpoint 'AppleTV'
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.543907 AM [AirPlayScreenClient] Stopping session internal
Jan 16 10:50:44 My-MacBook-Pro.local coreaudiod[161]: 2014-01-16 10:50:44.544218 AM [AirPlayScreenClient] Stopped session internal
Jan 16 10:50:44 My-MacBook-Pro.local AirPlayUIAgent[985]: 2014-01-16 10:50:44.544266 AM [AirPlayAVSys] ### Quiesce AirPlay
Jan 16 10:50:44 My-MacBook-Pro.local SystemUIServer[159]: 2014-01-16 10:50:44.544297 AM [AirPlayAVSys] ### Quiesce AirPlay
Jan 16 10:50:44 My-MacBook-Pro.local SystemUIServer[159]: 2014-01-16 10:50:44.553084 AM [AirPlayAVSys] ### Quiesce AirPlay
Jan 16 10:50:44 My-MacBook-Pro.local AirPlayUIAgent[985]: 2014-01-16 10:50:44.554904 AM [AirPlayAVSys] ### Quiesce AirPlay
Jan 16 10:50:44 My-MacBook-Pro.local SystemUIServer[159]: 2014-01-16 10:50:44.557604 AM [AirPlayAVSys] Ignoring route away when AirPlay not current
Jan 16 10:50:44 My-MacBook-Pro.local AirPlayUIAgent[985]: 2014-01-16 10:50:44.560307 AM [AirPlayAVSys] Ignoring route away when AirPlay not current
Jan 16 10:50:44 My-MacBook-Pro.local WindowServer[89]: Display 0x04280880: GL mask 0x21; bounds (0, 0)[1920 x 1080], 62 modes available
Jan 16 10:50:44 My-MacBook-Pro.local WindowServer[89]: GLCompositor: GL renderer id 0x01022727, GL mask 0x0000001f, accelerator 0x00004ccb, unit 0, caps QEX|MIPMAP, vram 2048 MB
I am happy to provide more information if needed.
Thank you.
-Tim

I'm currently still experiencing this as well. I've confirmed it occurs on 10.9.1, 10.9.2, and 10.9.3 on MacBook Pro Retina's, Mid-2012 and 2013 MacBooks. It happens on multiple ATV's not just one, all are updated to 6.1.1 and a simple reboot seems to fix it temporarily but it does come back. All the ATV's are connecting to the network via Wireless not Ethernet. These are 3rd Gen ATV's but I checked the serial number and these do not match the bad batch of Apple TV's from 2013 that were offered up for Replacement for Apple due to the bad firmware update. None of the computers have the Firewall turned on. Here's the two logs that we always find after the issue occurs (logs are recent, happened this morning):
5/30/14 8:57:36.017 AM coreaudiod[183]: 2014-05-30 08:57:36.016946 AM [AirPlay] ### Feedback taking too long to send (30 seconds, 17 total)
5/30/14 8:57:36.332 AM coreaudiod[183]: 2014-05-30 08:57:36.331492 AM [AirPlay] ### Feedback failed: -6723/0xFFFFE5BD kCanceledErr
The user will get disconnected from Airplay anywhere between 30 seconds to 3 minutes after logging on and can reconnect but then once again get disconnected after the same time period. One interesting thing to note is that when the Feedback Taking Too Long to send error starts occuring and the countdown to disconnect start ticking down to 30, its solely referring to Audio not being sent over the network and Video is working just fine. If I try to play sound I get another log and the sound doesn't play through the speakers. After a reboot, sound works fine and the Feedback Error's do not show up. I've also tried switching to Internal Speakers (since it defaultly switches to Airplay Speakers) after connecting to Airplay and seeing the Feedback timer start in the Console Logs but even after that the log continues to saw its taking too long to send and disconnects in 30 seconds.
This issue has been ongoing for months, I've got a ticket logged as far back as January with this occuring but its infrequent enough that we've just restarted and moved on. I'd say its an issue that occurs to about 5%-10% of meetings but that's an entire meeting that doesn't have the ability to Airplay until someone comes down and reboots it.
I don't often post in this forum but its still an active issue with no resolution, proof that its occuring on other people's systems, and no firmware updates having been released to correct it. It'd be nice to know of any workarounds other than having to buy some lamp timers for each conference room just to get a functional ATV or putting up a sign that says hey if you get disconnected every 3 minutes, reboot the ATV. The whole reason we're using Apple products is for ease of use otherwise I'd put together a much cheaper solution myself. Any help or recommended troubleshooting steps would be fantastic at this point.

AirPort Extreme (5th Gen) WiFi access point disappears but wired ethernet is ok

My AirPort Extreme SSID and access point "disappear" randomly from available WiFi networks. I had a 1st gen AirPort Extreme and never had this problem until earlier this year. I thought it might be a failing radio in the 1st gen unit so I used it as a good excuse to get a 5th gen AirPort extreme about 3 months ago. Same problem has been occuring; unfortunately it is random and I cannot get a handle on what/when/why it is happening.
For example, my iPhone 4S was connected to the network at about 1700 today and when I next checked the phone around 2115, no wifi connection and my network was not listed in the WiFi connections. The base station is away from other wireless devices (mouse, keyboard) and is about 10 feet from the nearest PC and monitor. Both printers are accessed via ethernet, not wifi. The strange and puzzling thing is that the PC, which is connected by ethernet to the AirPort Extreme, is still connected to the internet (I can browse, check email, newsgroups, etc.).
When I run the AirPort Utility, the base station is identified (AirPort Extreme 802.11n 5th Generation), there is an appropriate IP address, Version 7.6 firmware, and MAC address is listed. However, when I attempt to Continue or do a Manual Setup, I'm prompted for the admin password, the progress bar moves during 'reading from the Apple wireless device. Please wait...,' and then the utility reports "An error occured while tryong to access the Apple wireless device. Make sure your network connection is valid and try again. Error -6722.
If I unplug, wait, and reattach the power to the base station, WiFi becomes available again. When the WiFi connection "disappears", the LED light is solid green.
Any insights are appreciated; please let me know other helpful information I can provide.
Scott

I have the exact same problem and it's driving me nuts.
I bought an airport extreme n last week and plugged it in, hooked it up to my adsl router by Ethernet, configured it to set up a new wifi network and got the green light. I use an iPhone 4, iPad 2, and Windows 7 PC with an N wifi adaptor.
The airport works fine for about 2 hours before the wireless network disappears without a trace. Green light remains on the base station and I can connect fine by Ethernet.
"it just don't make sense"
I hope it's not a windows-7-only thing, Apple.
PS. Updated firmware to the newest version, no difference.
Airport is near to a wireless phone so I set a specific wireless channel and frequency to prevent a clash. No change.

My mac book pro wont connect via airplay

My mac book pro will not connect to apple tv, the error is -6722... any ideas

https://discussions.apple.com/thread/4137079?start=0&tstart=0
http://www.amacgeek.com/blog/2012/8/3/airplay-mirroring-in-osx-mountain-lion.htm l
http://www.ehmac.ca/mac-iphone-ipad-ipod-help-troubleshooting/102118-airplay-mir roring-will-not-work-bluetooth-turned.html
from this goole search
https://www.google.dk/search?client=opera&q=airplay+error+6722&sourceid=opera&ie =utf-8&oe=utf-8&channel=suggest

AEpress Completely Stuck Due to Firmware Rollback

Right off the bat, the symptoms I am having is an Airport Express (wireless-N) that is completely stuck in one state. I can't change any settings on it. When I try to access the Airport Express from the Airport Utility, I get error -6722 ("An error occurred while trying to access the apple wireless device"). It happens on wireless, and directly connected with Ethernet. It happens on windows, and on macs, and across all Airport utilities staring with 5.3.1. When I try to perform a hard reset (Hold down reset button while plugging in, leaving it plugged in, waiting for the rapid amber light and then letting go), the Airport Express restarts, but then comes back to its previously configured state.
In brief:
I can't log in to the manual setup to change any settings
Hard resetting appears to work, but then on restart all settings are retained.
The airport works as configured before it was put in this state.
I was troubleshooting some network issues (which turned out to be completely unrelated) when I tried reverting the APExpress back to firmware 7.3 from 7.5.2. After this completed, I lost my ability to configure the device, hard reset it, or re-update the firmware.
So as a warning to you all, do not revert back to 7.3 from 7.5.2 or else you may find your self in the situation I am in. It still works as I had it configured before the revert, but I cant update it in any way. Totally frustrating!

Aaaaaaand as I was writing that, I managed to fix it. Not sure how exactly. The variables that were used that worked:
On windows, running AU 5.5.2, right clicking upload firmware in the device list, choosing other, selecting a random firmware other than 7.3 (I think i ended up using 7.4.2) and clicking upload. Instead of trying to communicate with the APExpress, it directly uploaded the firmware and then it restarted, I got a crazy amber blink cycle I have never seen before (Three fast long blinks, and the three short fast blinks, repeat). Then it restarted and it was back to normal. Woohoo! There goes 5 hours of my life.

Airplay between iPad and MacBook Pro

I am trying to reflect my iPad to my MacBook Pro. I have the 3rd Generation and I am running OS 10.8.2. When I try to connect using Reflector, I get "an error (-6722) while connecting to the AirPlay device “Sandy’s MacBook Pro”". What do I need to do?

Interesting question.. I don't think you can do this with vanilla Apple.
I'd suggest you might Google your request. I turned up a couple of apps that you might read about
http://www.macworld.com/article/1156423/airplayer.html
http://www.macworld.com/article/1158876/airframe_airplay_iphone_ipad.html
Cheers

More than one HD per AirPort Extreme (802.11n) / different access

If more than one HD is attached via a USB hub, is it possible to setup different access permissions for the HDs?
I would like to use one for the Time Machine, another to be used as a local video server but not accessible from the Internet and the third fully (read/write) accessible from the Internet.

Hi! I've formatted the 160GB USB drive to HFS+ and tried again. I saw that speed access to USB drive was a little bit faster than before.
I simultaneously saved data from 3 PC's. After 5 hours (37 GB transferred) the base station "crashed" without rebooting. The base answered to my pings and the LED was green, the "switch function" worked properly. I tried to reconnect the disk without success. So I tried to access the base via AirPort utility without success: error code 6722 was shown. I physically rebooted the base: same problem occurred (green led, ping ok, no disk access, error 6722). I tried again and waited 5 minutes before accessing the base and the disk: everything worked again
Did any of you already try to put lot of GB simultaneously from more than 1 MAC/PC to an USB drive? Did your airport crash as described? Thank in advance!

Conflict with Neighbour using another Airport (802.11n)

Hello
I noted recently some slow down in my home wi-fi network and discovered that my neighbour installed a new airport extreme that might be confilicting with mine. I have tried to change channel (automatically set to 7) to 2, 3, 4, 9 and others. It partially solved the problem but if it works for a while, then the problem keeps coming back. I will go to his place tonight, please could you tell me what I should check ?
Also while changing my configuration, I keep having the same error message coming back (on my airport extreme), that is error code -6722 or sometimes -32 or -6. Apparently this is a comon issue to many of you. Could you help me also on that one? Thanks a lot. Pascal

vador300 wrote:
Radio Channel selection: Manual 36(5GHz), 11(2,4GHz)
I have now turned mine to channel 11 and it seems to work.
I would expect that having both units assigned to the same channel would maximize the interference, not minimize it. But if it's working, I won't argue.
However, while applying the changes, I got the error message -(6722). Also sometimes, error -(32)
A Web search showed a number of reports of error -6722, but no one seemed to have an explanation. Sorry.

Windows 8.1 and most recent version of Airport Utility. Error message 6722 during connection.

New computer with Windows 8.1. I have downloaded most recent version of the Airport Utility. The utility finds by airport express but during connection I get error message -6722. I suspect Windows 8.1 is not compatible with my first generation Airport Express but before I buy a new one would like to know for sure.

More compatible than v2 of the Express which you cannot configure from windows.. all the later airport routers need v6 utility to configure them.. and this is not available for windows.
These issues arise due to all sorts of things.. the error message is very unclear in its meaning.
Plug the Express into the computer by ethernet. Do a factory reset on the Express and see if you can set it up by ethernet.
Wireless products can be a problem. Set the Express to fixed channel, 11, 6, 1 in that order.. with no security and a simply name, for both the express and wireless. No spaces and pure alphanumeric.
If the computer cannot connect under the most ideal situation nothing else will fix it.
If you have an ipad iphone with iOS v6 or later then you can use the apple version Airport utility which is much more likely to work than windows.

HT1595 An error occurred (-6722) while connecting to the AirPlay device "Apple TV"

An error occurred (-6722) while connecting to the AirPlay device “Apple TV”

I was trying to connect my macbook air to my apple tv when getting this error. It turned out to be the firewall on the macbook air blocking airplay. Try turning off the firewall to see if it works for you.

Error -6722

Similar Messages

Maybe you are looking for