AP Rogues 'On Network'

We see several Rogue APs in our network which are, according to WCS, not 'On Network'. However, most of them do turn out to be 'On Network': their MAC address appears as connected&active in a switch port. I wonder if this is because the 'On Network' status is never re-examined after first detection? Any suggestions?

A couple of questions
1) What LWAPs are you using
2) Have you enabled Rogue Location Discovery protocol
3) Have you configured dedicated Rogue detector LWAPs
4) Have you got legacy Autonomous APs on your network

Similar Messages

  • Machines losing connection to the Network

    We are experiencing some irregular network issues whereby we have 2 G4 Mirror Door Desktops acting at servers (10.3.9) and a variety of Powerbook G4s and Macbook Pro's (10.4.x) which are continually dropping off the network sporadically. Apart from these two desktop servers, all the machines affected are laptops strangely enough.
    Firewall is not enabled on the Macs.
    The Macs lose all network connectivity including printing, internet connection and server connection.
    I have tested pinging to and from the Macs and the results are always as though they are off the network. The Macs can however ping itself indicating it can see a network. Whe you remove the machine from the network and re-add it, the IP address range is 169.x.x.x. This is because by default, Apple allocates the user with an IP range so far off the network that its indicating it can see a connection (ie ethernet card and cable) but cannot see the network.
    To get the machine back on the network, you need to remove and re-add the network cable to get connection again. We looked into every possibility inclusing Firewall or DNS issues.
    We have compared the switches and vLANs and they are all the same; we have checked that Appletalk is broadcasting correctly through the switch; we have added the machines with a static IP address (servers have static IP addresses anyway)and the machines still drop off; we have altered DHCP lease renewal to a longer period and it still dropped off; removed Appletalk from a machine and it still dropped off.

    It may be a 'typo' by you, but forget about 'appletalk' - this is not relevant to your problem (and pretty well redundant now). This looks like a TCP/IP issue.
    What is doing your DHCP? Presumably you have checked to ensure that there is only the one dhcp server in your network, and another has not accidentally been enabled (on a server, router or airport). What is the dhcp range for the DHCP server?
    Your post suggested that the servers, with static IPs, also 'drop off' the network. So a server IP cannot be pinged from a lan machine which has a correct IP assigned to it (rather than one which has a 169 address which obviously will not be able to ping it) ?
    On your laptops, when connected via an ethernet cable, have a look at Network Prefs-> Show: Network Port Configurations. In what order are these? Specifically, I am wondering if Airport is getting prioritised above Built-in Ethernet and maybe there is a 'rogue' airport network which the laptops discover and attempt to join ahead of built-in ethernet.
    -david

  • TS3899 Our CEO has an iPhone and an iPad. Everytime he is at a specific airport (BWI) he is unable to send or recieve email over 4G or wifi. Everything else seems to work just fine over wifi or 4G LTE. Has anyone ever seen anything similar? is this malwar

    Our CEO has an iPhone and an iPad. Everytime he is at the Baltimore Washington Airport (BWI) he is unable to send or recieve email over 4G or wifi. Everything else seems to work just fine over wifi or 4G LTE. Has anyone ever seen anything similar? is this malware?
    Both devices are on Verizons 4G LTE network. Both devices do have some of the same APPS installed. Can this be a case of him connecting to a rogue wifi network of a hacker that may have installed malicious code on his devices when he connected? That would explain why only his devices have the same exact issue only at BWI airport.

    Something similar I've experienced. I was once having to use a AT&T hotspot and the iPad simply refused to access my mail via the mail app. But if I used safari I could get it.  So the internet was working, but my supposition is that something with the hotspot's firewall messes with mail exchange.
    next time your boss is at BWI, do you guys have a web interface? (for example if I wanted to access my work mail I could get them to set it up via the mail app and exchange, or I could go to a certain web address and access my mail that way via safari)
    He could try using safari and the web interface if you have it.
    If it's something in the hotspot's firewall I doubt it's anything that can be changed.

  • 8600 does not like enterprise wifi

    Hello HP,
    We Just deployed some Cisco Meraki Wifi access points and when we had only 1 SSID in range the Printers (we have many) worked perfectily but as more accesspoints came on line the printers disconnected from the wifi with the following error: No Filtering.  Mac address filtering is not used on our network.   According to the firmware update tool the printers are up to date.  
    Question 2:  One printer which is having issues is using firmware CKP1CN1322CR but the updater says it Up-To-Date dispite is having a different firmware then the other and not matching the updaters firmware of CLP1CN1322CR. 
    Any ideas why this would happen?  
    Thank you
    Alan

    I've been having the same problem all year, have googled this problem a hundred times, and have seen this same log message...but for some reason, seeing your post made it click for me: our Meraki network was quarnatining unrecognized or "rogue" wireless networks on our network....and it was considering, at random intervals, the "setup" wireless network on our printers as a "rogue" network and quarantining them - IP address filtering! The minute I whitelisted our printers in the "Air Marshal" settings in Meraki,  they were magically connecting again!

  • Client machines losing connection to Leopard Server

    I have a small office set up as follows: 20" iMac (Intel) running Leopard Server. 4 client machines, all Macs, All Intel, also running Leopard client. I have these machines connected to a Linksys 8 port 10/100 router...and then to a cable modem for Internet Access. The problem that I'm having is that the client machines lose connection to the server multiple times each day. A restart and reconnect seem to fix the problem...only temporarily. At first, I thought it might be the Linksys Router so I put a Gigabit switch in between the machines and the router with the same results. I have the router on a static IP of 192.168.1.2 and am not running DHCP, DNS, or any other services other than file sharing. If any of you have experienced this, I would greatly appreciate any direction you might have.
    Thanks in advance.
    Dan

    It may be a 'typo' by you, but forget about 'appletalk' - this is not relevant to your problem (and pretty well redundant now). This looks like a TCP/IP issue.
    What is doing your DHCP? Presumably you have checked to ensure that there is only the one dhcp server in your network, and another has not accidentally been enabled (on a server, router or airport). What is the dhcp range for the DHCP server?
    Your post suggested that the servers, with static IPs, also 'drop off' the network. So a server IP cannot be pinged from a lan machine which has a correct IP assigned to it (rather than one which has a 169 address which obviously will not be able to ping it) ?
    On your laptops, when connected via an ethernet cable, have a look at Network Prefs-> Show: Network Port Configurations. In what order are these? Specifically, I am wondering if Airport is getting prioritised above Built-in Ethernet and maybe there is a 'rogue' airport network which the laptops discover and attempt to join ahead of built-in ethernet.
    -david

  • Finding rogue APs that are on wired network

    I am beginning to think that there is no way to gaurantee that a rogue AP is connected to your wired network. I have read up on RLDP and "rogue detection". I was excited because I thought rogue detection would accomplish this. However, when I connect an autonomous AP to my wired network it does not get identified as being on my wired network despite the "rogue detector" being in place and connected to a trunk port with all network vlans on it. In thinking through this I believe this is because the radio mac and ethernet macs are different on the autonomous AP. The ethernet mac of the autonomous rogue AP is in the rogue detector dB, not the radio mac. So when the detecting APs sends the radio mac to the rogue detector it doesn't get flagged. Can anyone confirm this? And if so offer any insight to a workaround. I was able to get a "rogue client" flagged as a threat connecting via this AP, because it arp entry is in the rogue detectors dB. But I can't get the AP flagged. If this is the case then rogue detection is more or less useless to me because I care about rogues on my network (obvious security breach) not rogues in other businesses in my area. I rather now when the rogue AP goes in and not have to wait until a rogue client connects to it. Please advise....
    Regards Chuck

    Network Chemistry makes a free tool (as well as a more advanced product you can buy) that might fit the bill for you. It relies on people properly classifying the devices on their own network with the free tool to build a database of device types based on the vendor ID digits of mac addresses, as well as some snmp scanning (I think). A link is below. I don't have a lot of experience with the tool, only because I'm not entirely convinced of it's accuracy, but to be honest, I've never really used it in a production environment
    Good luck!
    -Chris
    http://www.networkchemistry.com/products/roguescanner.php

  • Finding a rogue WiFi router on local network

    This is likely a very odd and possibly complicated question, but I figure I'd throw it out there anyways.
    At my office, we have a couple wireless routers throughout the building. However, one in particular has started to act up. It used to work perfectly, but in the last month or so, it has stopped working. Connecting to it via the password that was set no longer works. Laptops can SEE the network in a list of wireless connections, but we can't log into anymore.
    Now, normally a easy solution would be to find the physical router and reset it manually. But here's the problem.
    We don't know where it actually is. It was installed before myself or the current IT specialist were hired. We were able to use a Macbook and iStumbler to detect its general location by walking around the building and guaging signal strength. But we still can't find it. It's likely up in the ceiling somewhere. Don't ask me why.
    So, I'm wondering if there's a way, be it through an app, Terminal, etc, to detect the router over the network. If we're able to get the IP of the device, maybe we can log into it and possibly fix the problem.
    If not, perhaps people know of a good device we could purchase to further locate the physical device it self? I've seen a handful of WiFi detectors, but they usually only show 1-5 bars - nothing more.
    Any insight?

    I assume you mean that you have several wireless access points, not wireless routers.
    Have your IT Dept disconnect the ethernet cable that connects the Access Point to the main switch or router, and then "tone" the wire to trace it.
    Use one of these:
    http://www.iautomate.com/kp100.html
    Another option is to flash the firwmare over the LAN, BUT that will probably default the Access Point to an address already in use and that may create a bigger problem.
    Peter

  • Two separate enterprise WiFi networks in the same building

    I work in a building that currently has Cisco controller based access points. The access points aren't managed by us and are actually part of another campus. We are given access to them but they don't work quite like we want them to. So we are wanting to bring in our own Cisco WLC 2504 with 3702 APs. But when we brought this up with the main campus they said we can't have two separate enterprise wireless networks in the same building. That their APs will mark our APs as rogues and try to shut them down. There was also mention that they can't share the same channel and that the radios will negotiate with each other to determine how much power they need for coverage. But from what I've read none of that is true. So maybe I misunderstanding something and hoping someone here with more experience can shed some light on this. The only reason we would want to keep their wireless in the building is so when their staff come to our office they can use it. 
    So can two separate WLC/AP systems on different subnets and broadcasting different SSIDs exist in the same building with out causing any issues?

    By default, the WLC code does not try to contain rogue AP's.  Just lots of alarm's and unclassified rogue's.
    In this case you hosts may have actually enabled containment but would have also received a screen full of warning about the public nature of the unlicensed wifi band.
    Here the Superior Court system is side by side with the County system even to the extent that the AP's are next to each other.  Gets fun.  Since each SSID constitutes a rogue, each unit represents a LOT of rogues to report.
    Good Luck

  • How to protect a PIM-SM network from unauthorized pim routers and multicast sources?

    Hi,
    we're using pim sparse mode in a customer network with catalyst 2/3/4/6K switches, all multicast routers are redundant with pim dr running for access subnets. RPs are configured with anycast rp.
    A) Is there any possiblity to prevent rogue pim routers/igmp queriers connected to host ports from getting connected to the legal pim routers and from getting involved in the local igmp traffic?
    Maybe like DHCP Snooping used with DHCP. I read that in the latest Sup2T ios (http://www.cisco.com/c/dam/en/us/td/docs/switches/lan/catalyst6500/ios/15-2SY/config_guide/sup2T/15_2_sy_swcg_2T.pdf) there is a feature called 'ipv4 router guard' which does exactly what we're looking for:
    'When configured, the Router Guard feature makes the specified port a host port only. The port is prevented from becoming a router port, even if a multicast router control packets are received. In addition, any control packets normally received from multicast routers, such as IGMP queries and PIM joins, will also be discarded by this filter.'
    Afaik, PIM authentication isn't supported in current catalyst ios versions.
    Using a normal port ACL is not an option in our case because of a management decision.
    B) Is there any possibility to prevent (on a per-subnet basis) rogue sources from sending multicast streams to legal multicast-groups?
    Maybe, can I configure a svi of a host subnet or a host port to drop any incoming multicast stream while still accepting IGMP and sending out legal multicast streams?
    Using 'ip pim accept-register' command on the rp is not an option because we've tons of legal sources which would end in an very huge error-prone acl
    Unfortunately, a normal ACL is not an option here, too.
    Best Regards
    Thorsten

    We use two pim routers in each host subnet for redundancy, they elect the PIM DR.
    Does pim passive mode work here?
    (Config Guide: If the ip pim passive command is configured on an interface enabled for IP multicast, the router will operate this interface in PIM passive mode, which means that the router will not send PIM messages on the interface nor will it accept PIM messages from other routers across this interface. The router will instead consider that it is the only PIM router on the network and thus act as the DR and also as the DF for all bidir-PIM group ranges. IGMP operations are unaffected by this command. ... The redundant PIM stub router topology is not supported. The redundant topology exists when there is more than one PIM router forwarding multicast traffic to a single access domain. PIM messages are blocked, and the PIM asset and designated router election mechanisms are not supported on the PIM passive interfaces.)
    ip pim neighbor-filter maybe would work to prevent rogue pim routers to connect to the legal pim routers but wouldn't rogue pim routers still be able to manipulate the layer2 switch to send all igmp traffic to them and not to the legal pim routers?

  • After ios 8 update I can no longer play music through my car. I have a 2012 Nissan Rogue - whihc has its own cable made to use with iPhone 4 - I use a apple adapter to converst to use with 5.

    After ios 8 update I can no longer play music through my car. I have a 2012 Nissan Rogue - which has its own cable made to use with iPhone 4 - I use a apple adapter to converst to use with 5. Has been working fine up until update. Is there a fix for this? The car does not have usb

    Here I come to save the daaaaaaaaaay!!!
    Had the same issue with my Nissan Rogue 2011.
    This listed below will fix it...
    Go to General > Restrictions > CarPlay -- Make sure Carplay is DISABLED. (The new IOS 8 enables this on default)
    Go to General > Reset > Reset Network Settings
    The Nissan Rogue radio system was never designed to work with CarPlay. By default, CarPlay feature comes enabled when you install IOS 8. Suckz, right?
    You're very welcome! Have a great day!
    Sincerely,
    The Superhero

  • Command line compiler (rhcl.exe) adds on rogue full pathways into [Merge Files] of .hhp

    I'm using RH 9 and generating chm outputs on my Win 7 64-bit computer.
    I have a core chm help file and several sub chm helps that get merged into it.
    I have a batch file that regularly compiles our help files locally and then copies them into a common local directory. It then copies them up to a mapped network drive where they are picked up by the nightly build of our installer.
    The problem I have, is that the command line compiler (rhcl.exe) is adding on a full pathway for all the sub helps listed in the [Merge Files] section of the core help's .hhp file, causing these problems:
    1) First of all, the pathways are wrong. The pathway it puts on is from the location of my .xpj file of my core help project. The output directory for the compiler is actually sending all the helps to a different local directory.
    2) These need to be relative, and should not have full pathways. The full pathways make it so that when I click on a subhelp TOC entry that subhelp's topic opens up in an entirely different window instead of merged into the core help's window. (See #13 on Peter's helpful site here about the problem with absolute paths: http://www.grainge.org/pages/authoring/rh9/using_rh9.htm)
    Here' what I want it to look like (the good):
    [MERGE FILES]
    pcdmisportable.chm
    pcdmistutor.chm
    pcdmisvision.chm
    pcdmislaser.chm
    pcdmiscmm.chm
    pcdmisUJB.chm
    pcdbasic.chm
    toolkitmodulesvwmp.chm
    pcdmisdci.chm
    toolkitmodules.chm
    pcdmisnc.chm
    pcdmisip.chm
    toolkitmodulesblade.chm
    pcdmisregistry.chm
    pcdmisfixturing.chm
    Here's what it looked like after the command line compile (the bad and the ugly):
    [MERGE FILES]
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisportable.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmistutor.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisvision.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmislaser.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmiscmm.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisUJB.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdbasic.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\toolkitmodulesvwmp.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisdci.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\toolkitmodules.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisnc.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisip.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\toolkitmodulesblade.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisregistry.chm
    d:\hg\pcdmisqa\pcdlrn\help\corehelp\pcdmisfixturing.chm
    I've done the following ....
    I've checked my .xpj file and they have relative paths only.
    I've deleted my .cpd file.
    I've removed chm references from my rhbag.apj.
    ... and the hhp file still gets modified with pathways to my core project
    directory tacked on:
    It's strange; because if I compile without the command line, by opening the project and running the generation inside of RH, I don't get the problem where it re-writes the [Merge Files] section with the pathnames.
    Any ideas on where are these rogue full pathways coming from and how I can fix it? Or is it just a bug with the command line version of the compiler that Adobe will need to fix?

    I don't use command line generation but to the best of my knowledge, this has not been fixed.
    Please follow this link.
    http://www.Adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Multiple iPods on a Windows XP Pro networked computer

    The school where I work is having a problem with multiple ipods on Windows networked computers.
    Several of our students have been given 5G ipods. Each student has a network logon with a fairly restrictive mandatory profile.
    The idea is that each student could log on, plug in their iPod and download the appropriate podcasts for their needs.
    Here is the issue. The first student to log in plugged the iPod in and did all the setup work.
    The next student logged in to that same computer and plugged in his iPod. The machine recognized it as teh iPod fom the first student.
    Anyone have ideas why this would be? I have read the Apple papers on using multiple ipods on one machine and one of their suggestions is to create multiple logons, so this whole issue should not even arise.
    Thanks

    The next student logged in to that same computer and plugged in his iPod. The machine recognized it as teh iPod fom the first student.
    those symptoms can be produced by the issue described in the following document:
    Windows confuses iPod with network drive or hard drive and may keep iPod from mounting or songs may seem to disappear
    (if that is what is going on, it would be a "doubled" version of the basic problem. you get an initial drive letter confusion. a copy of the ipod_control folder from the first ipod ends up on one of the drives as a result of the drive letter confusion. when the second ipod is plugged in, you get a second drive letter confusion, the PC sees the rogue ipod_control folder on the drive ... and it interprets the drive as the first ipod.)

  • Multiple Apple TV's on the same network with airplay issues.

    I work at a school with 37 Apple TV's.  They are all on the same network, some of them are wired while others are wireless.  The problem I am having is that airplay works and then doesn't work for some unknown reason.  The Apple TV's are connected to the network and internet when they are experiencing this and I believe that the issue is bonjour. Does anyone know any way of solving this issue.

    Yeah, I think wiring them is the only solution to this problem.
    We've only got three (well, had one and bought two more this summer - that's when the trouble started).
    The first one I got had trouble connecting with the wireless network, so Apple support said to reboot the main router. That is, shut down the entire network while we reboot for one Apple TV. So...OK, I get it, Apple is a CONSUMER company and we're trying to use their products in a school...in spite of that, so far, it has been worth the effort.
    But YESTERDAY I got that message about too many devices on the network and to "disconnect a device..." (you know the rest).
    So, I called Aruba, knowing that it was a wireless issue and that I've had issues with them and, particularly
    Bonjour. Aruba appears to be a Windows only network - would that I would have known that three years ago. But Aruba TAC has NO CLUE what the issue is. So I called Apple Tech Support and they have NO CLUE - weren't even aware of this posting, what, six months ago? (Shows you how much they read and value the forum - we're on our own, boys and girls!)
    So...I wired the front of the school Apple TV to a nearby wireless access point and now it's a steady as a rock. But prior to that I actually stood in front of the ATV and watched as it connected, then disconnected, then connected, then disconnected (ad nauseum). Interferrence? Well, maybe, there are only about 150 rogue networks detected in the immediate vicinity - but Aruba ASSURED ME that their WAPs were sophisticated enough to recongnize that and filter them out. (Maybe not?)
    So the ATV at the front of the building ocassionally just drops off the network. I can tell because we run a Flickr slideshow on it all day long with announcements and stuff. When I go by the TV and see the thumbnails and no slideshow, I know it has dropped off the network. Usually I can reconnect it. But that's not good enough.
    Finally, yesterday, a teacher called me who has an ATV (long story on how she got that) and said she was not longer connected to the network. A shudder ran through my body as I expected (and realized) the worst.
    So, my installer is coming tomorrow to wire her ATV into the WAP in her classroom. But TODAY, I have to call Aruba and enable the additional port since it's not enabled by default.
    I'll tell you, every day, I get this horrific feeling in the pit of my stomach that this whole world of technology we have built is held together with bailing wire and duct tape and that it just has to blow at some point.
    Then I watch Bob Ross do his paintings (and a NEW KID on the block - watch out for him - Kevin Hill - this kid takes Bob Ross to the next level and he's only 18 years old) and think - "What the heck am I doing here, anyway? Why am I not home painting?" But them I start feeling guilty that I'm leaving the school in the lurch. Who will stand up to these bozos who don't have a clue what's going on and, further, don't seem to care, yet, get this, think they are doing a GREAT JOB! I'm telling you, I'm living on Superman's Planet Bizarro!

  • Lion Server network accounts not working on some computers.

    Hello all -
    I'm currently having an issue with network accounts working on some Macs but not others. I have a Mac Mini and a MacBook Pro. The Mac Mini works fine and I can login and sync my network account with the server just fine. However, I cannot connect to it from my MBP.
    When I try and connect I get an error that says "You are unable to log in to the user account "xxxx" at this time. Logging in to the account failed because an error occurred."
    If I login through console (by typing in ">console" in the username field) I get an error that says the user does not have a home directory...
    I have searched numourous other forums but I have not found a solution that seems to solve this problem. I have unbound and re-bound my client to the open directory and I have restarted file sharing. Neither has solved the problem. I have a feeling the issue originates somewhere on the MBP since I can log in to the Mac Mini without any problems.
    Anymore suggestions?

    Thanks for your suggestion, SolidWood. Unfortunately it didn't help.
    After a 90 minute phone call with AppleCare, this issue has finally been resolved. Here is what the solution was. Turns out it was pretty simple but it took a while to find it.
    First we created a test user and left the home folder set to Local Only in the Server App. I was successfully able to login with the test user on both clients but since there were no mobility preferences set, it was pretty basic.
    Then, we removed the Users sharepoint from file sharing, turned off file sharing to disconnect any users, and restarted the server. Then we created a new folder on the Server HD with a random name. We chose Darron. We created a new sharepoint in file sharing (with it still turned off), and shared the new folder called Darron. Double click on the sharepoint and scroll to the bottom and check the box that says "Make available for home directories over AFP". Then we restarted file sharing.
    Then we opened Workgroup Manager, clicked on the problem user in the left sidebar, clicked on the Home option at the top, and there were three things listed:
         (None)
         afp://servername.com/Users
         afp://servername.com/Darron
    Then we removed the Darron sharepoint from file sharing, and found that it was still listed as a home directory under the problem user.
    This was the root of the problem. The system didn't know which path to use as the home directory.
    Sooooo...
    In the server app, we opened the Directory Utility (Tools in the menubar, Directory Utility). Clicked on Directory Editor. Authenticate to the directory using the diradmin login. Changed view settings to match this below:
    In the left column, there were two paths listed for home mounts. We deleted both of them, saved changes, and closed directory editor.
    Then, we restarted workgroup manager and both paths had been deleted from the users home listings. This was begining to solve the problem.
    In the Server App, we recreated the users sharepoint, made it available for home directories, and restarted file sharing and workgroup manager. Now only one path is listed for the home folder for all the users.
    This solved my problem of not being able to login on the MBP. The system synced the home folder and all was well. On the Mac Mini, I had to delete the problem account, un-bind from the network server, re-bind, and recreate the account. Now both clients are sycning perfectly and all is well.
    Thank God I bought AppleCare! Thanks to everyone else for their help and suggestions.
    As a recap, the problem of not being able to login to the MacBook Pro was caused by having multiple paths to the multiple home folders. These rogue paths were added somewhere in the troubleshooting process to try and recreate the home directories before I called AppleCare. To solve this, we had to remove the directory listings from accounts using Directory Editor, remove and recreate the users sharepoint in file sharing. The syncing problem on the Mac Mini was also created when multiple paths were introduced. The system didn't know which files to use.
    Taylor

  • Upgrade to 7.5.2 broke WDS network

    For the past 6 months I have used a Time Capsule and 2 Airport Express to configure a WDS network. The TC is the Main station and then I have one AE as a relay and one as a remote station. It has worked perfectly fine until I was prompted to upgrade.
    For what I can tell, both the TC and the Relay are now running on the firmware 7.5.2 but the Relay is no longer working. It no longer shows up in the Airport Utility and if I reset it and reconfigure it, the update ends up with the cryptic message "An error occurred while reading the configuration. Make sure your AirPort wireless device is plugged in and in range of your computer or connected via Ethernet and try again. (-6753)"
    I'm not sure what to do at this point. I tried to revert to the previous firmware but that didn't work either, I'm getting a similar error... Has anybody run into the same issue or has a suggestion on what to do to get it back working again?
    Thanks

    I came across the same issue.
    I have a simple set up: just have two AE, one main and the other relay. (I used to have four AEs previously, but got rid of those when N version came out, though configured them as WDS in case I needed to add an extra)
    Anyways, I read on another thread that one should update firmware to 7.5.2 of all relay(s) and remote(s) first, before updating the main station's firmware.
    Not sure if that's true, but if it is, it's a real shame AU doesn't just stop you from screwing it up, as it knows which base is doing what in the WDS you've set up.
    So.. I had just updated the main, and upon updating the relay, AU failed to "see it" appear again - never came back from reboot. And from that point onwards my WDS was dead.
    I tried a full reset, reconfigured everything from scratch, both AEs now being in 7.5.2, but WDS would refuse to work - checked the log file and found the main station complaining with the following line over and over (ie. kept on associating/disassociating):
    Dec 28 19:49:30 Severity:5 Deauthenticating with station XX:XX:XX:XX:XX:XX (reserved 2).
    So, after checking other threads, and googling some more, I just gave up (for now) and put the main AE as Wifi network creator, and the other AE set to join&extend the network.
    I really wish the team @ Apple could make some improvements on WDS... or check if something's wrong with latest firmware. I mean, it could be me goofing up somewhere, but I reset both boxes 3 times (ie. redid the whole steps for WDS creation from scratch thrice..) and I've set up WDS before — until this last "rogue" 7.5.2 update came along, it was working perfectly.. kinda wish I didn't update sometimes
    Anyways, for now I'm staying away from WDS, cuz for me it's broken

Maybe you are looking for