- I disabled Mionet at startup and then competely repowered down the actual network - modem, router, drive . After the restart, I put all the computers to sleep and went out for a half hour. Came back and it connected without the usualy headaches!
Note: It’s been about an hour now that has included 30+ minutes of all computers at least in stand by mode and a full reboots on the MPB with immediate reconnections. I’m won’t be fully convinced of my solution working untilleaving everything off overnight and sucessfully connecting without issue in the morning.
UPDATE: Been about 3 hours and all is normal. Most of this time has been with the cpus sleeping and the drive reconnects when needed.
UPDATE 2: Had the drive and cpus inactive form 6-11. Turned the MPB back on and it cant find the drive so my solution doesnt work for long periods. Can’t speak for Brownster’s solution below…
- From Brownster:
First make sure you can login to the admin pages of the NAS. To do this, I unplugged the ethernet for 10 minutes or so. Then I plugged it back in and power cycled (power cable out for 10 seconds then back in). After a couple of minutes I saw the drive in Finder and then logged in via Bonjour (default uid and pwd are both admin).
Clicked on Advanced Mode
Clicked on the Network tab
Clicked on Services
Unticked the AFP Service checkbox at the bottom
Immediately I noticed how much more quickly the menus refreshed and all connectivity seemed a lot more snappy.
Ok, so now I can’t use Time Machine since I have disabled the afp functionality. To access files on my NAS, I simply used an smb connection instead (Finder, Go, Connect To Server, smb://yourdrivename) and had to login as Guest rather than Admin.
I’m quite happy with this temporary fix since I managed to get a full backup in yesterday and I will wait until the AFP setting is fixed before I try again!!!
Hope this works for others. And hope this helps WD Support pinpoint the problem a little better.
If people try either of these please report back on success rates GL!!!