Hi John,
Thank you very much for your wide explanation. I do appreciate.
Actually I suceed solving the problem yesterday evening, before your last answer was posted (I'll explain how later).
Just for you (and any other like me who might face the same issue) to understand what I did. Fisrt step, of course, following your recommendation:
My original recommendation was to first "connect the Time Capsule the way you would like it to be connected when it's in use" followed by the "hard reset" and then configuring it with AirPort Utility.
The point is, strangely, until yesterday, every time I did that, the internet signal from the router (feeding other devices and the depending-router upstairs) dissapeared, and the ATC couldn't work (PPoE, DNS, WAN issues) so no way to set up anything. Instead, yesterady, after an ATC disk eraseand a hard reset, I disconnected the ATC and the router. Then connected the ethernet cable between them; then booted the router until operational internet signal was on, and then booted the ATC. Since, I found the same connectivity issues, I started by "adding the ATC network to an existing Network" (the one provided by the router - let's call it Office Wifi Network OWN - , which was working fine, and didn't find itself "stolen" by the ATC as previously had occured). I changed a couple of things and went back to "Creating a new Netwok", I changed from WPA/WPA2 personal to WPA2 Personal, I included the DNS (putting the same adress as for the router (192.168.1.1), and the ATC created the new Network, which is working simultanieously with the OWN.
Even if you consider that
From that description, it seems as though you now have two networks at the office: one created by the office wireless router, and another created by the Time Capsule. Is that right? If so it's not ideal for a number of reasons: when you are connected to your office network's Wi-Fi, there will be no path to the TC, and TM backups won't work
I am forced to have both networks operating: the OWN is providing internet and wifi to the upstairs router for my employees computers, general backup PC server, wireless printers, etc; the ATC netwrok must work in order to provide access/path to my backups from my iMac. Let's say at this point that I'm living in Mauritania, and nobody in this country (no technician, no apple support agent, NOTHING-NO ONE) is able to create a network working for both, my employees (using windows PC) and I (using Mac). Also, I prefer to keep my things/information aside.
Well, then, once I had both Networks working fine, and the ATC reachable without trouble from the Aiport Utility App, I tried to backup with the aforementioned results (100001 error).
So, I digged in other forums, in the meantime your sure answer took to arrive, and I found this:
Boot to recovery holding CMD+R until you see the apple logo. You may have to select your Language on the next screen, or it may go straight to OS X Utilities. In OS X Utilities, at the top of the screen you have a black apple, OS X Utilities, File, Edit, Utilities. Click "Utilities" and click "Terminal". In Terminal, type out /usr/bin/chflags norestricted,nosunlink “/Volumes/drivename/Library/Keychains/System.keychain” but replace drivename with your disk name (I.E. Macintosh HD). If you see "Invalid Flag" you typed something wrong. After it finishes, you should see a bash# command. If so, click the black apple and click restart, then try backing up.
from the Keychain error 100001 when attempting to reconnect time machine. posted by Kaemaahl.
And it just worked fine.
Once I did that, I tried to backup from the ATC and it worked. Now I have my iMac brand new first backup in the ATC and I feel like heaven has opened to me.
Thank you again, John, for your time, patience and knowledge.
PS.You can't even imagine how hard/frustating is to live in Mauritania regarding technology issues. There is no one to be found if the issue is not a really conventional.