Benches Networking

8

Loss of connectivity through AFP with Tim…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hello guys,

I am notice a strange behaviour with my old 2TB AirPort Time Capsule in last month and a half, where sometimes I receive a warning message in the only MacOS who is using it, that is unable to connect to it.

I try to access it through AFP and nothing, but it reponds through ping. To solve this problem, I simply take power off and on again, and it solves. This issue have already happened 2 times.

My MacOS version is 10.9.5 and is in a different network(VPN site to site) of time capsule, but have been working without problem like this for 6 months, and there is no problems related with network connections.

There are at least two users who use Time Capsule WIFI dailly, dont know if it can be relevant with this issue.

Do you know what its happening?

If you need more info fell free to ask.

8 replies

Sign in or join Beachball Help to reply.

  1. 0

    cyberfec

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    So I have finaly discovered that the issue is with AFP service, when Time Machine is unable to connect to the target Backup disk, I tried to connect through AFP an it hangs trying to connect, this still doenst happen under SMB. Seems like I will have to use another Backup disk to do the job in a must reliable way...

    Thanks everyone for the help!

  2. 0

    Tesserax

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    A few questions, if you don't mind:

    1. What exact model is this Time Capsule (TC) and what version of firmware is it running?
    2. Can users on the same local network as the TC use AFP to access the TC file shares?
    3. What VPN appliances are used from both site locations to make the connection?
    4. Can you access the TC across the VPN using a SMB connection instead of AFP?
    5. Is the reason for using AFP for Time Machine backups?

  3. 0

    Tesserax

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Interesting on two points:

    1. Time Machine only uses AFP to communicate with the Time Capsule for backups ... not SMB. You can verify this with a data dump of the traffic between the devices. However, Time Machine can use SMB when backing up to a NAS ... for example, to a Synology NAS. In this case it will use SMB 3.x for the file sharing protocol.
    2. Although the Time Capsule supports SMB, it only supports SMB 1.0

  4. 0

    cyberfec

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    1.

    TC model is A1470 and how can I confirm TC firmware version, being in a different network?

    2.

    I tried from a Windows 10 but without sucess, I will try from a MacOS, who is much more reliable in SMB connections.

    3.

    OpenVPN

    4.

    Yes, I can access with both protocols. (I have not tested with SMB when I had this issue, because I didnt knew that there was a SMB service running in TC)

    5

    Half of the response is in 4. and because of compatibility between Apple devices.

    I have not mentioned about uplinks from both sides, but one is a dedicated connection with 100/100 Mbps bandwidth and the other is a shared connection with 100/100 Mbps (where TC is). In shared connection I got at least 80% of the connection from granted. Usually the bandwidth usage vary between 5 to 20% in both sides during production time.

  5. 0

    Tesserax

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    TC model is A1470 and how can I confirm TC firmware version, being in a different network?

    The AirPort Utility's host must be on the same network subnet in order for it to access the base station. That is because, it relies on Bonjour (Apple's implementation of Zero Configuration Networking) which is not easily routable. You would need to use this utility in order to ascertain what version of firmware that the base station is running ... but this is not critical at this juncture.

    I tried from a Windows 10 but without sucess, I will try from a MacOS, who is much more reliable in SMB connections.

    The Apple base stations only support SMB v1.0. Due to it being highly non-secure (AFP over the Internet, is as well), Microsoft no longer supports it and defaults Win10 devices to using SMB v2.0+. There is a workaround to still allow a Win10 device to use v1.0, but I would highly recommend against it. You are left with using a macOS device for this ... and you should not be using either protocol outside of a VPN.

    OpenVPN

    Although I am familiar with OpenVPN, I've not been involved with any of their site-to-site solutions, only their peer-to-site ones ... so I'm not going to be able to address any potential issues around this service type.

    However, if you can establish a SMB connection between sites, but not AFP, then that would indicate to me that AFP is being blocked somewhere between locations and may be due to the VPN server (or router) configuration at either or both ends.

  6. 0

    cyberfec

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I know AirPort Utility is not designed for interprise networks.

    I dont thing that I could be a problem related with the network or VPN.

    When I had again that problem I will do port scans and test login in openned ports to see if there is an issue with login directory or services in this TC. At least to come with more info about this issue.

    Thanks for the help Tesserax.

  7. 0

    LaPastenague

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I am notice a strange behaviour with my old 2TB AirPort Time Capsule in last month and a half, where sometimes I receive a warning message in the only MacOS who is using it, that is unable to connect to it.

    I am not surprised you are having trouble.. I am actually much more surprised it worked ok for 6 months.. Possibly this is only possible because you are using a much earlier Mac OS. 10.9.5 is excellent (from network point of view) if no where near as secure as later versions.

    I try to access it through AFP and nothing, but it reponds through ping. To solve this problem, I simply take power off and on again, and it solves. This issue have already happened 2 times.

    In one way your problem is not that serious.. twice in 6 weeks is really amazingly good for how reliable Time Machine is lately.

    What is the actual error message in Time Machine?

    So your fix is to reboot the Mac..??

    When you think about it maybe the issue is the Mac.. rather than the TC on the other end. Especially when you are doing this backup over VPN the details it can be picking up would be fairly limited.. as Tesserax commented due to Bonjour not working across the VPN.

    Does the TC have a static IP on the other side?

    I am guessing it is configured bridged to the main router.. and you set DHCP reservation in the main router so it is always at the same IP.. this is always worth while.

    In the airport utility.. under file.. configure other.. put in the TC IP address and password and see if you cannot open it remotely.

    Can you mount the TC in Finder by IP?

    ie using Go, Connect to server.. AFP://TCIPaddress (insert your TC actual IP address).

    Once mounted can you copy files to it using Finder even when Time Machine cannot do its backup?

  8. 0

    cyberfec

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, I know, I have created a Time Machine in a QNAP NAS as alternative, who have a buildin for Time Machine purposes, through AFP.