Benches Networking

6

error -6753

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I have an Airport Express G connected directly to an Airport Extreme N Gigabit. I have been having all kinds of problems with signal dropping, including the widely posted problem with wide channels on Apple TV 2.0.1. Anyway, I changed my channel on my Express to 11 trying to avoid interference; there is one other person on 11, but there are a half-dozen folks on 6 and a couple on 1, so none of the lower channels worked right. I figured 11 might be better since other devices typically use 1-10. As far as dropouts go, I am much more stable. However, I have lost the ability to administer my Express from my mac mini - I get error -6753, and every time I launch Airport Utility, the airport connection drops. I went to my old iMac that I gave to my 5-year old to play educational games, and was able to administer the Express fine, but I cannot figure out why my mini can no longer connect with it. I have rebuilt my keychain, and I ran Onyx automations thinking something might be cached or permissions might need rebuilding, but alas, to no avail. Any ideas?

6 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Did you try the middle channels, channels 1,6, and 11 are never good choices if there are more than 3-4 networks in your area. Keep in mind you can only see wireless networks, there are probably 50 different wireless devices that operate on those frequeency ranges including cordlesss phones. I like to assume that for every base station I see there is at least one cordless phone I can't see because this is generally the case. Try channels 3 and 9 and see what you get.

    Edit: Forgot to mention, almost all wireless networks come on channel 1,6, or 11. Channel 11 is actually the most problematic channel I've seen.

    Message was edited by: jseg2005

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Unfortunately, my problem is not the interference anymore. My question is about not being able to administer my Airport Express anymore and getting the error -6753 message. Can anyone help me out?

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I had hoped for answers here on the boards, but none of my questions seem to warrant much attention. In any event, I fixed this problem by turning IPv6 back on in Network Preferences under the Advanced section. I don't really know what that does, but someone had recommended turning it off to maintain better connections, and I did have fewer drops with it turned off. Since I turned it back on, though, I am able to connect my mini to the Airport Express G.

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Shane, I'm having the exact same problem with my new AX 802.11n used as main base on my network. I can't get back into the configuration, and the firmware update starts but fails to complete. I always get error message after a long wait period.
    Where do you turn ipv6 on or off?
    I also can't extend my network as I used to with my 2 AX 802.11g stations. They keep on flashing amber although I set them up using Airport Utility.
    Any idea anyone?
    Thanks

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Go under your Airport menu at the top right of your screen and open Network Preferences. Click on the Advanced button, then the TCP/IP tab, and there is a box called "Configure IPv6." I changed it back to "Automatically" and I can again control my Airport Express from my Mac mini. Woo hoo!

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If only it were that easy! I have tried that and still no joy. I have the same problem - I can't get back in to even reconfigure it.