Backing up to Airport Disk

Hi,
First post. I'm sorry if this has been covered but I couldn't find an answer out there.
I have an Airport Extreme Base station and successfully attach my WD My Book to it via USB and use Time Machine.
I did some mucking around with things and to make a long story short: I re-formatted the My Book and want to start Time Machine from scratch.
Now I can attach the My Book using Firewire 800 and it really rips along with the backup. I want to do this to make the initial (large) Time Machine image and then connect the My Book via USB to the Base Station and continue to do incremental backups from there.
However, Time Machine doesn't seem to recognise the fresh sparsebundle on the My Book as being from this machine and wants to start a new backup using USB (and I don't have three days to wait!).
Can I connect Time machine to this sparsebundle and continue the backup process from there?
Thanks
Mike

Hi again everyone,
For those of you out there facing this same problem. For me the above way of operating has fixed it! It has been over 24 hours now and I have a set of fully browseable Time Machine backups to show for it. I have not tried a restore but I'm confident that that would work as well.
This is a great way to get up and running when using Time Capsule/Airport Extreme Base Station with a USB disk. It only takes a couple or three hours to back up 150Gb of data using Firewire 800 (If you're lucky enough to have it) and then continue the backups from there using Wifi and USB.
It also makes me feel a bit better about forking over the extra cash to get a Firewire 800 disk.
I followed the instructions exactly. There may be room for shortcuts but don't blame me if they don't work.
Good luck.
Mike

Similar Messages

  • Time Machine backing up an Airport Disk

    I've read that Time Machine will back up mac journaled formated external drives, unless you exclude them. That's all well and good, but my situation is a little different. Here's my setup.
    15" MBP, 120GB HDD
    AEBS
    RAID 0 1TB WD My Book Pro II drive on the network as an airport disk.
    500 GB WD Pro drive on firewire 800.
    The 500 gig is going to be used as my *time machine* drive. The *1TB Airport Disk* drive is mostly media. The only thing I want backed up is some important document folders as well as my music folder. But when I go to exclude the folders I don't want backedup on my 1TB airport disk drive, I find that the entire contents of the drive isn't selectable to be excluded. I don't really have any space on my internal drive to store these files. All drives are mac journal extended formatted.

    UPDATE
    I tried using iTimeMachine to see if it will allow Time Machine to access my AP Disk. I believe it just runs the terminal command that activates the default setting for Time Machine and network compatibility. Either way, when opening up Time Machine's preferences, I now see my 1TB drive as a drive I can back up to. However, unlike the thousands of threads out there, I don't want to back up to it, I want to back up some folder from it. As usual, when opening up the exclusion options, all of the folders on my AP Disk are greyed out, which tells me that Time Machine won't back up that disk.
    Thoughts?

  • Backing up with Time Machine via "Personal File Sharing" and Airport Disk

    I've been using Time Machine on my own Mac at home and want to use it to backup other Macs in my house as well. Right now I'm just backing up over FireWire, but plugging my disk into each of the other Macs one at a time doesn't seem to make much sense.
    Besides going out and buying a Time Capsule, Leopard Server, or Xsan, what are my options for backing up multiple Macs to one disk? I've read that using an Airport disk is somewhat risky because of some "premature file transfer confirmation." Has anyone ever used Time Machine w/ Airport Disk and had problems?
    I've also noticed that you can back up to shared drives, like if I share my current FireWire disk so people can back up to it, but wouldn't that require for people to connect to the host Mac manually via Finder? And wouldn't that in turn defeat the purpose of automatic scheduled backups?
    Any advice or suggestions would be appreciated.

    the only supported option besides Time Capsule is to back up to a hard drive directly connected to a mac running leopard on the same local network. as you mention it would indeed require that this drive be mounted first. you can automate mounting this drive on login and simply keep it mounted at all times. to do that mount the drive of the host Mac on a remote mac and while it's mounted there add it to the login items in system preferences->accounts.
    You can also use drives directly attached to an airport extreme base station. that works in the same way as backups to a Time capsule.
    Message was edited by: V.K.

  • Has Anyone resolved a directory error when backing up to an Airport Disk?

    Beginning on 16 April, Time Machine stopped backing up to my Airport Disk. It still attempts but is unable to get past "Preparing" I can see the Airport Disk in the available disks in TM and I can get to the backups on the disk (oldest is 23 March). The error message says "Error occurred while creating the backup directory" I have seen mention of needing to remove characters frm the name of the disk and other hints. Nothing works so far. It seems strange that it would work for 3 weeks and then stop.
    Thoughts?
    sgtbill

    I'm getting a similar message approximately every second time I try to update the vault. I've rebooted the computer but still the same issue. Seems a bit of a problem if you can't trust it to backup to the vault, can you trust it to restore if needed?
    david

  • Extremely slow speed when backing up onto Airport Extreme disk

    I have a wireless network set up with the Network Extreme basestation. The basestation has a 500 GB iomega drive attached via the USB 2.0 port. The disk comes up just fine, but when I try to use it as a backup disk from my iMac using SuperDuper!, I get an effective peak copy speed of 1.9 MB/s, and it takes multiple hours to perform a ~30 GB backup. The disk is Mac formatted.
    For comparison, if I plug the disk directly into the USB port on my iMac, the peak effective speed is ~15 MB/s and the backup takes 35 min.
    The iMac and the basestation are both running 802.11n, with an effective speed of 130 MB/s.
    On the off chance that it was the disk imaging process that was slowing things down, I have run SuperDuper! with disk imaging back to the iMac's HD rather than the Airport Extreme HD and it runs at ~20 MB/s.
    To review:
    - Trying to backup to the Airport disk runs really, really slowly and takes forever
    - It's not the network speed, the HD speed or the software.
    What's up? Anyone else have this problem? One of the reasons I bought the Airport Extreme was to use it as a network back-up HD. If it going to take a day to copy a full iMac disk, then this is clearly unsatisfactory.

    I would echo Glyn's assessment. One needs to keep in mind that Apple designed this product as a low cost device to meet the typical requirements of a home user (ie streaming of music, sharing of a few files, and backups without time constraints). If one needs the performance levels typical of a network file server, then this is the wrong product to use. Perhaps Apple's marketing information for this device should make that a bit clearer.

  • AirPort Disk works on Vista but is ULTRA SLOW on MacBook Pro...please help.

    This is nuts, huh? Please help.
    I can copy files using Window's Vista at about 7MBps so it takes around 2min 40secs to copy a previously bought 1.3GB iTunes TV show from the AirPort Disk (connected via USB 2.0)to my Vista machine. I understand this is a reasonable speed, if you think it should go faster let me know. When I try to play it with iTunes directly from the Airport Disk(by control clicking it and telling it to play with iTunes, not sure this is the best way, advice appreciated) it plays okay but I get a fair amount of stutters where it will skip a 1-4 seconds. Any way to fix this? Or should I just download it to my computer and play it from there. I was trying to save space and confusion on my computers and just play via the Airport Extreme Disk.
    NOW THE WEIRD STUFF! It takes 4 hours to download the same TV file mentioned above from the Airport Disk to my MacBook Pro! And to stream the movie from the Airport Disk is impossible. Can anyone offer suggestions? I searched online and could not find any help.
    Additional Info that might be helpful:
    -AirPort Extreme 340ll/a, Version 7.5(I assume that's the firmware version).
    -I erased with 0s and formatted an external 7200RPM 8MB Western Digital drive to "Mac OS Extended Journaled" via my MacBook Pro's USB port, using Disk Utility.
    -My wi-fi connections seems fine: for web surfing it is fast with my Macbook and Windows computers, so that's not a problem. FYI, I did some internet download speed tests and got like 15,000-20,000kbps, which is pretty good, right?
    -I hooked the drive up directly to my MacBook Pro's USB 2.0 port and copied the same HD TV show file to the computer, and Apple's "Activity Monitor" utility showed it is reading and writing at 30MBps which I understand is quite good. So it does not appear to be a hard drive problem either.
    Any help would be appreciated. Thanks!

    Cause of problem:
    I found out that the problem was that in the "Airport Utility" under "Internet Connection" tab, the "Connection Sharing" had been set to "Off(Bridge Mode)". This stopped my MacBook Pro from accessing the AirPort Disk(an external hard drive connected to the AirPort Extreme Base Station). I still find it weird that My HP computer could access the AirPort Disk just fine and my MacBook Pro was so ultra slow(i.e. 4 hours to copy a 1.3GB file!) accessing files on the hard drive.
    So, how did the default setting get changed to cause the problem to being with? I got some error pop-up box that said there were 2 NAT tables causing a conflict of some sort, so I followed it's instructions which put it in bridge mode which caused the problems. The reset of the wireless router put the "Connection Sharing" back into "Share a Public IP address" mode which is the default.
    So anyway, this appears to be the end of this story, and I hope this post saves some people out there from some headaches and lost time!
    Peace!

  • Connect to airport disk when through internet

    Hello,
    I have a mac book running 10.6.8  At home I have an apple "airport extreme" router with a WD external hard drive connected via USB, the disk works fine at home.   I know it is possible to connect to the external hard drive(airport disk)   via the internet when I'm not at home.  But I can't seem to find any guidance to my situation.  I also have a mobileme account and I thought I should be able to do it with "back to my mac"  but I can't get either method to work.
    Any help, advice or links would be appreciated!!

    You have at least two routes to be able to access the AirPort Disk from the Internet: 1) Back to My Mac (BTMM) / MobileMe (easiest), or 2) Configure the AirPort for Port Mapping.
    I suggest trying the BTMM method first.
    As you already know BTMM is tied to an individual's MobileMe account.
    Let's go over your BTMM setup, just to make sure something wasn't missed.
    BTMM - General Requirements
    OS X Leopard 10.5.4+
    Active MobileMe account. Each Mac & the AirPort router, that will be relying on BTMM, needs to be configured with the same account.
    A publicly reachable IP address for your AirPort router.
    A router that supports either NAT-PMP or UPnP. Note: All AirPorts supports NAT-PMP.
    BTMM - Basic Communication Flow
    For a computer connected to the Internet via a router, BTMM "asks" the router for its configuration information. For a router, like your AirPort, that uses NAT-PMP, BTMM will ask the router to assign arbitrary public ports. In turn, the router will provide these port assignments (& the router's Public IP address) back to BTMM.
    BTMM then sends this information to the MobileMe account. In background MobileMe updates a special set of DNS entries to be used by BTMM. These entries are then made available to all BTMM clients using your MobileMe account. When a computer, with BTMM enabled, uses your MobileMe credentials, it automatically retrieves a list of all other computers/routers that are registered with the same account. All these devices should then appear under the SHARED section of the Finder.
    When attempting to connect to a remote computer (or router), BTMM creates a secure connection to that remote device using the information from the MobleMe account.
    Once the connection is established, the devices can then communicate with each other.
    For a router, the key is that if the ISP doesn't offer you a publicly reachable IP address then BTMM won't work. You will then have to look for an alternative solution, like BackToMyPC or LogmeIn.
    On both routers (Apple Only)
    Using the AirPort Utility, verify the following:
    AirPort Utility > Select the AirPort > Manual Setup > Internet > NAT
    Enable NAT Port Mapping Protocol (enabled)
    AirPort Utility > Select the AirPort > Manual Setup > Advanced > MobileMe
    Click the plus button to add your MobileMe account information. Any HDDs attached to the AirPort (or both the Time Capsule's internal HDD and attached USB HDD) will now appear in the SHARED section of the Finder on BTMM-enabled computers using the same MobileMe account.

  • 10.5.1 and Airport disks

    Airport disk under 10.5 was flaky at best. Now under 10.5.1 I can't open the disk attached to my AEBS at all. I can see the disk but clicking on it fails to open it.
    I've rebooted everything. I reset the AirPort base station. I've turned the firewall off. File sharing on, off. It did work under 10.5 with an occasional dropout. And under 10.4 it "Just Works"

    Same problem at my end. No problems at all with 10.4. But since 10.5 and 10.5.1 sometimes I see the disks, sometimes I can open one. But most of the times after opening, I loose connection with all of them. They do not show on the desktop either, only in finder. This is very annoying and I am considering to go back to 10.4. I am lucky, my MacBook Pro is 1,5 weeks old. I have both 10.4 and a Leopard upgrade disk to work with . However going back will be a lot of work. And Leopard should work as a minimum with Apple products would be my standpoint. And that is all I am using.
    I am really curious when a solution will come. This seems a very systemic issue looking at all the discussions around this topic.

  • Airport Disk problems

    There seem to be a lot of threads going on about connectivity problems regarding disks connected to Airport Extreme base stations. This http://discussions.apple.com/thread.jspa?threadID=1155412 is probably the biggest. Since this really is a large issue, I thought I'll post a report of my findings.
    Today was the first time I encountered the fact that I couldn't connect from my iMac G5 to my Airport Disk anymore , Finder gave me the following message:
    +*Connection failed*+
    +The server may not exist or it is not operational at this time. Check the server name or IP address and your network connection and try again.+
    I went to my MacBook pro (waking from sleep) and it gave me the same message.
    Restarting the Airport Extreme brought my disk back on my Macs.
    I simulated this scenario, to see where it was failing:
    *Case 1: let macbook pro sleep*
    1. Fresh reboot of Airport
    2. Mount disk on all macs and one windows xp machine
    3. Put MacBook Pro to sleep (disk still working on other mac)
    4. Wake MacBook Pro
    5. Everything still works on all machines
    *Case 2: let imac sleep*
    1. Fresh reboot of Airport
    2. Mount disk on all macs
    3. Put iMac G5 to sleep
    4. Wake up iMac G5
    5. Disk doesn't work on Macs (AFP), but still works on windows machine (SMB)
    In last scenario it looks like the AFP service on the Airport Extreme Base Station crashed. You can manually check this by doing this in Finder menu: *Go -> Connect to server*.
    And type this:
    afp://ip.of.your.basestation/ (you can find the ip of your basestation via airport utility)
    You will get an "Connection failed", that means the server is not responding. At this point you can still connect to the Airport Disk via the SMB protocol. In the Finder menu: *Go -> Connect to server*
    And type this:
    smb://ip.of.your.basestation/
    Use your username and password and you'll be able to connect to the airport disk.
    Another way to check if the AFP service is still running on the airport, is to use an portscanner. You can use the one provided by apple in Network Utility. I used nmap.
    After a fresh restart the following ports were opened:
    21/tcp open ftp
    53/tcp open domain
    139/tcp open netbios-ssn
    445/tcp open microsoft-ds
    *548/tcp open afpovertcp*
    554/tcp open rtsp
    7070/tcp open realserver
    10000/tcp open snet-sensor-mgmt
    After waking the iMac from sleep the following ports were opened:
    21/tcp open ftp
    53/tcp open domain
    139/tcp open netbios-ssn
    445/tcp open microsoft-ds
    554/tcp open rtsp
    7070/tcp open realserver
    10000/tcp open snet-sensor-mgmt
    You can see that there is no AFP server (afpovertcp) listening on the Airport anymore.
    I have the following setup:
    MacBook Pro Core 2 Duo 2,33 Ghz
    Mac OS X 10.5.1 (fresh install)
    iMac G5 2,1Ghz
    Mac OS X 10.5.1 (upgraded from 10.4.11)
    Airport Extreme Basestation (fast ethernet)
    - 802.11n (802.11b/g compatible)
    - wpa2 personal
    - file sharing with accounts
    - no guest access allowed
    Currently the only workaround I found, is by using the SMB protocol. (Finder -> Go -> Connect to server). This works on all machines, even after waking from sleep.
    The problem as far as I can see is twofold:
    1. AFP service on Airport Extreme Basestation is buggy, it justs crashes after it recieves info it doesn't expect.
    2. Leopard sends stuff It shouldn't send.
    Tiger never had this problem.

    My AEBS network, internet connection and Airport Disk are all (finally) holding connections. It's been about a day now, so I guess it's going to be ok next week.
    Here's some of my story/thoughts in case this helps anyone else who is still struggling with the madness:
    First, I bought a TC and connected a USB disk. This was a cacophony of dropped connections, followed by the messages Frodo posted, lost internet connections, etc. A lot of resets, channel changes, restarts, two reformatting of the Airport Disk (via hardwire connection to one of my computers and then reconnecting it to the AEBS), etc. etc. later, I returned the TC for an exchange and bought a simple AEBS and connected that to the Airport Disk.
    Same sort of problems again, but this time I don't usually lose my internet or network connection. New problems enter - glacial speed on some/most computers and ok on others. The Airport Disk keeps disappearing and can't reconnect. More restarts.
    This is what seems to be working now:
    I have every single client computer set to never sleep and that includes turning off the "Put HD to sleep when possible" button. I also set my WPA2 Personal timeout to 500 days. The default is 1 hr. Also, I took the Airport Disk down and connected it to a computer and ran Disk Utility. Found a header problem and fixed it. Followed that with Disk Warrior. More problems, this time an assortment. DW fixed those. Then reconnected the Airport Disk to the AEBS. Now it all works.
    I did a bit of reading on WPA2 on Wikipedia and it turns out this scheme sends out some sort of key to the client computers and does it dynamically as the network is up. (This might explain the "unexpected ACL" message I was getting in Disk Utility when checking client computers - there are 3 of them. I assume these are an Access Control List generated by my AEBS; I certainly didn't put them there). Anyway, I got to wondering if the AEBS is trying to generate a new key for the 'group' that hat connected to it and since one or more of the 'group' has nodded off, it is unable to do so and this results in the lost connection followed by 'not operational' message. Maybe it thinks it was being hacked?
    Anyway, with both those settings my network is stable, internet is stable and the Airport Disk has been mounted on various desktops now since yesterday. I'll worry about faster speeds later. None o my computers will sleep until an update is released. They don't mind. I have no inclination to spend any more hours fighting with this thing.
    FYI, I have eight 10.5.2 computers and three 10.4.11. They are all happy this morning - although for a time yesterday the 10.4.11 client computers were real slow. I shut those down for a while last evening and concurrently changed to Channel 9. I'm using the 802.11n (b/g compatible) setting and I know that is in the 2.4 frequency, which is pretty crowded these days. I think the higher channels are probably less crowded. Anyway, the 10.4.11 computers were ok when restarted last evening and are still ok this morning. All connections held. Ditto for the 10.5.2 clients.
    I don't know where the faults came from with the Airport Disk (fixed as described above yesterday), but I do know I did not "Disconnect All Users" in Airport Utility before resetting/restarting the AEBS while the Airport Disk was connected and (perhaps) still shared despite the dropped connection messages. I'm not even sure that disconnect button was available since I never looked.
    Wheew!
    Not sure what I'm going to do when the replacement TC arrives. It's a heckuv'n idea and I hate to walk away without at least another trip into the twilight zone. I've lost files before and would have been SOOoooo happy to be able to fish back in time to find them.

  • Data corruption with Airport Disk file sharing

    There is another long thread on the Airport Disk, and I am not sure if this is the same problem. My situation is that my file server died recently, and I am looking for its replacement. Airport Disk with my new base station appears ideal because I have a 300GB disk from my dead file server and a USB disk enclosure. I connected the disk to my iMac and formatted it to HFS. While still connected to my iMac, I copied over my iTunes library. This was the second time trying out the airport disk, so I created /Shared and /Users/username to work with file sharing with accounts. I then ejected the disk and connected to my airport base station (gigE, 7.2.1 firmware). My first test was to run a recursive diff between the two iTunes libraries. There were some files that differed, so I ran the diff again and a different set of files were identified as differing! I disconnected all users and moved the disk back to my iMac. I ran the diff again, and there were no differing files!
    I haven't yet had time to investigate more, and I am wondering if others have seen similar symptoms.
    Dan

    I have the same issue.
    Plus, in my case, two disks appear on my desktop, even though I have no partition. One is named the same as my disk, the other is named the same as the user account for the disk on the Airport Extreme.

  • Can't copy large files to AirPort Disk Using Windows 7

    Hi Everyone,
    I'm positng because I'm unable to copy large files to an AirPort Disk using Windows 7.  I have the following setup.
    AirPort Extreme:
    - Firmware version: 7.6.1
    - Airport disks secured by password
    - No guest access allowed
    - Airport Disk Preferences:
      - Automatically discover airport disks is enabled
      - Show Airport Disks in the system tray is enabled
    External Drive:
    - Western Digital 500 GB MyBook External Drive connected to Airport Extreme thru USB
    - FAT32 Formated
    Computers:
    - 2 Toshiba Proteges, Both with 4GB RAM
    - Both have Windows 7 Home Premium with Service Pack 1, 64-bit version
    - (Sorry we have no MacBooks at home, just iPhones and iPods!)
    Airport Utility:
    - Version  5.6.1
    Airport Disk Preferences Utility:
    - Version  1.5.5.3
    A week ago, I was able to copy over large files (videos <4GB in size) to the drive.  Now, when I try to copy over these large files to the drive, the copy dialog box hangs.  I receive a message stating that Windows is calculating the size, but then it doesn't copy over.  Windows then gives me a message that it is unable to copy to the drive.  When I test the drive connection by copying a small text file over, it copies over quickly and seamlessly.  This problem occurs on both computers.
    I am able to do the following with the drive connection:
    - Read files
    - Change file names
    - Copy files from the drive to my computer
    - See the contents of drive
    I've tried all the combinations of the following with no success:
    - Turning off Windows Search
    - Downgrading the firmware
    - Reconfiguring wireless adapter
    - Rebooting computer
    - Rebooting wireless router
    - Rebooting external drive
    The drive seems to be working fine except for when I want to copy <2GB files over to the drive.  Does anyone have a solution that seems to work?
    Thanks!

    I'm happy to report that, after reformatting the drive to HFS+ (aka Mac OS Extended), there are no problems writing/copying large or small files to the AirDisk drive.  I'm also happy to report that I am copying to the drive at a rate of roughly 4MB/s.
    As I mentioned earlier, the only catch is that I am unable to plug the external drive directly into a Windows computer via the USB port as Windows is unable to read HFS+ formatted drives.  (I can, however, plug the drive into a Mac computer as they can read HFS+ formatted drives.  The only problem is that I don't own any Macs at this time!  LOL!)
    You're probably wondering how I formatted the external drive to HFS+ since I don't own any Macs.  (Windows only allows you to format drives in exFAT, FAT, NTFS and the like.)  That is a good question.  Basically, I downloaded an open source formatting tool called, Gparted, which allows you to format any USB drive to any major file format system.  Since Gparted is an open source tool, it is a little cumbersome to use. Once you figure out how to use it, it is a cinch to format the drive to HFS+.  (Of course, an easier method would be to borrow a friend's mac, plug the drive into their mac, and format it to HFS+ using their mac.)
    For a step-by-step guide on how to solve this problem, see the steps below:
    1) Backup all data from external drive
        a) Fortunately, I have a 1TB ultraportable USB drive which has enough space to backup all data on the drive
    2) Format the external drive to HFS+ using one of the methods below
        a) Plug it into a Mac and format it
         b) Use Gparted (free) to format it
    3) Plug the drive back into the Airport Extreme
    4) Start copying files over to your networked drive!
    I hope this helps you! Cheers!

  • BUG FOUND!! in Airport Disk programming

    I'm betting this is having a bigger issue then most poeple realize as it effects reconnecting to the Airport disk.
    Ok after lots of testing I've figured out a major bug in the Airport Disk Programming for Security.
    This has only been verified with the following settings:
    1. Airport Disk is configured with Accounts for access
    2. Formatted with HFS+ USB drive.
    Discription:
    1. When connecting to the Airport Disk you get the error:
    "Connection Failed
    Unknown user, incorrect password, or login is disabled. Please retype the login information or contact the disk's administrator."
    2. You retype the password and user name and it still says the same thing over and over and over.
    The Cause of problem:
    You connect to your Airport Disk the first time with no problem using your login and password. If you cause your connection to be interrupted for a small amount of time and you get that Warning about server disconnect and it shows your airport disk and personal disk with the disconnect button, and they disconnect!! Then you cannot reconnect to the Airport Disk till you reset the Airport Extreme.
    To get this Disconnect dialog, it can be caused by a number of common uses, here are a few of the common ones:
    1. you VPN into work (with Airport Disk shares mounted)
    2. you change from wireless to Hardwired connection (with Airport Disk shares mounted)
    3. You let your computer go to sleep when its on a wireless connection but are connected through another wireless access point hardwired to the network (with Airport Disk shares mounted)
    When getting your Airport Disk volumes disconnected in this way, The Airport Extreme I'm guessing is deactivating the account and not properly disconnecting the connection. So at this point you have to Reboot the Airport Extreme to let you use your account again on the Airport Disk.
    I hope some poeple from Apple actually read these. I've had to reset my Airport extreme about 24 times a day between my wife's 15" MBP and my 17" SR MBP getting this disconnect problem.
    And for those poeple out there who keep having Airport Disk connection problems, Lets make sure your not having this problem. To test, simply reboot the airport extreme router & see if you can connect to your Airport Disk Volumes, then once your volumes are mounted turn off your Airport wireless (on your MAC) or unplug your Hardwire till you get the disconnect message. Then try to reconnect to your Airport Volumes after restoring your network connection.
    This issue needs to be fixed ASAP!!!!
    Please reply to this message with your nominations to try and get this issues raised to a P1 or lvl 1 priority so it's in the next firmware upgrade as it's not an issue with OS x programming side, as a rebot of the computer still doesn't restore the connectivity with the AirPort Disk.

    HERES A SOLUTION I POSTED IN ANOTHER THREAD!
    Hi,
    I've been trying to work out the Hard Drive problems with the Airport Extreme for a few days and have had some success, so I'll share the info if its any use!
    First of all, your printer and both hard drives all run off their own power supply, therefore, you don't need to have a powered usb hub, or just take the plug out and keep using the hub, save yourself a plug!
    More importantly, I have had the same thing with the hard drive appearing in the Airport Utility yet whenever I try to connect, it comes up with an error and can't mount, although when I go to network and connect it appears but then goes wrong at the last part mounting, this is what I found...
    the first time I plugged hard drive in all worked nicely, however, any time I have unplugged the power to the Aiport Extreme and connected again it'll show but never connect. When I went to make a few partitions I realised that if you unplug the router and repower, whatever HD name its seen before doesn't work until the HD name was changed again. For example....
    I called my first HD to connect 'wifiHD', was working fine, next time i unplugged router was still showing in network but I couldn't mount it, I then plugged it to the mac and renamed it 'wifiDISK' for example and plugged it back into the router and it worked fine! Its very strange cos when I needed to unplug it last time I then had the same trouble and just renamed it back to 'wifiHD' it worked fine! Its a little flaw which is a right bugger to find so the bottom line is...
    RENAME THE HARD DRIVE EVERY TIME YOU UNPLUG THE ROUTER AND YOU CAN MOUNT IT AGAIN
    Another tip is format your HD in 'Mas OSX Extended' as it can be read by both mac and PC over the network. Then as windows isn't the best when you go to 'My Network Places' and 'Add Network Place' if you can't find the HD or even the router then enter
    \\routername\\hardrivename\
    in this format into the box, it'll take a mo but it'll then ask for the password! I personally have my hard drive guest access read + write so I entered
    user: guest
    password: base station password (or disk password as selected in airport utility)
    and it all worked!
    Sorry for the long explanation, hope this has helped!

  • Losing wireless when transferring files to an Airport Disk

    Here is my situation. I just purchased a 500gb Lacie usb drive to replace a nas and 160gb firewire drive. I am trying to transfer all my music, photos, etc. to the new drive that is connected as an airport disk via the usb port on the base station. When I try to transfer from the nas to the airport disk, after a few minutes it completely knocks out the wireless(I get the solid amber light on the base station) and it breaks the transfer. The wireless comes back up after a few minutes. I am doing this on my Dell pc (XP Pro) right now, I haven't tried it on my powerbook. If anyone has any thoughts I would appreciate it.

    To get the job done, try using an Ethernet cable instead of relying on a wireless connection.

  • Airport Disk Logon Problems with SyncbackSE

    Hei - looking for a little assistance with this...
    Essentially I am having trouble working out what username/password I should use to access my airport disk, and what settings need to be selected on Airport Utilities.
    I have an Airport Extreme setup with a Maxtor One touch USB drive.
    I have two PCs running XP/Vista - boh can access the disk through the Airport Base Station Agent. My problem is that I am attempting to use this drive for synchronised back up using SyncbackSE. Syncback is syncing "My Documents\Music" with "\\10.0.1.1\MaxtorOneTouch\Music". This gives an 'invalid password' error...
    Syncback offers the option to enter a username/password for network drives, but i am unsure what this should be. Under Airport Utils -> Disks -> File Sharing I have ticked Enable File Sharing, Secued shared disks with device password and chosen read/wite acess for guest access. Should this be enough to access my drive with username: \\10.0.1.1\guest, password: <default ax password>?
    Do i need to use username: \\10.0.1.1\MaxtorOneTouch\guest?
    Am I going about this the wrong way entirely?
    Any advice? Many thanks in advance.
    Neil

    I am having the same problem authenticating an acronis backup to an airport disk. What should populate the fields of username/password? I can't find this information anywhere.

  • Airport Disk with Bonjour

    I have a Western Digital "MyBook" Tb drive that I used to have connected on my AirPort Extreme. I have a MacPro as well as 2 PC's that were sharing this MyBook disk just fine using Bonjour. The Bonjour app used AirPort Disks to automatically "offer" the disk as a resource when the computer restarts, or whenever it becomes available. I was sharing using accounts. i.e. the username and password had to be entered to access the shared resource.
    Recently, the MyBook began to disconnect from the Bonjour for no apparent reason. I would log the disk back on and connectivity would be there, but then it would just disconnect again after 10 minutes or so.
    So I connected the MyBook directly to the MacPro using firewire and just used the 'Sharing' utility and now access my files "\\MacPro\MyBook".
    It doesn't disconnect anymore.
    But I do notice a file write delay every once in awhile.
    Can someone tell me which method is preferred and what pieces need to be ironed out for most efficiency?

    Does the new Airport Express N (I acquired one recently) have Airport Disk functionality? I tried to connect an external USB hard drive to my Airport Express but nothing shows up within Airport Utility.
    Sorry, but no. The new 802.11n AirPort Express Base Station (AXn), like its predecessor, will only support a single USB printer on its USB port.

Maybe you are looking for