(1)
Your rating: Now say why...
Bonjour Mounter 3.0.13
Mount your AFP or SMB share points silently in the background. Commercial ($15)
- Download Now
2.8 MB -
Visit Developer's Site
Sandro Noel
Bonjour Mounter will mount your AFP, SMB, CIFS, FTP, WebDAV(http/https) nerwork shares silently in the background without that annoying finder window popping up.
It will also automatically mount appearing bonjour enabled servers
It will also automatically mount appearing bonjour enabled servers
What's New
Version 3.0.13:
- Removed excessive logging.
Requirements
Intel, Mac OS X 10.6 or later.
Intel, Mac OS X 10.6 or later.
Bonjour Mounter User Discussion (Write a Review)
Overall:
(11)
(11)
Displaying 1-10 of 36
Displaying 1-10 of 17
-
-
-
Bonjour Mounter will mount your AFP, SMB, CIFS, FTP, WebDAV(http/https) nerwork shares silently in the background without that annoying finder window popping up.
It will also automatically mount appearing bonjour enabled servers
It will also automatically mount appearing bonjour enabled servers
Copyright © 2012 MacUpdate LLC
- -
+14
Also, the current version is 3.0.13
+63
+4
Use earlier
AutomountMaker
Just wondering how long it takes you to send out licence information after purchasing through Paypal?
Best
y
+1
+101
MacUpDate admins: Please change the "Requirements" section.
There are now separate versions for Mac OS X 10.5.x and Mac OS X 10.6.x.
+1
+1
James Strachan reviewed on 10 Jun 2009
The only downside is; Bonjour Mounter does not seem to auto-mount when my laptop wakes up from its sleep - it only auto mounts on startup
+2
I still have problem with Bonjour mounter when my MacBook Pro wakes up. It looses all mounts and sometimes is able to rediscover them but sometimes it does not. I will have to fiddle with going to the mount manually through finder and then BM will work again.
I also have a little request: It would be nice on some mounts to have an option for BM to send wakeUp (magic packets) signals so sleeping servers would wake up... (useful when trying to save energy)
Otherwise this app is going to the right direction and I love the frequency and speed of updates. Nice work!
Thx,
Max
Sorry your experiencing wake up problems.
I've been getting that feedback from some other users as well and i'm looking into the problem, but to be honest, i cant reproduce the problem here, i do not know why, all my computers wake up and connect properly, i also have a laptop roaming in 3 different networks and BM connects to the right server every time without fail. i'm puzzelled.
As far as the magic packets are concerned, i'll look into it, it's an interesting feature. :)
thanks for the feedback!
Sandro.
Let me know if the new version does it for you.
Thanks.
+1
+1
I would donate if the product worked, but it doesn't--not for me. All I want it to do is re-mount my specified mount points as they become available. I can add the mount point to my login items and manually reconnect using the Finder. The only functionality this app offers over the default OS is the ability to automatically detect and re-mount shares as they become available. Unfortunately, there is no Help system, no official web site (that I can find, anyway), and support (via email) is only for people who have donated.
I can't in good conscience donate to this program, because it acts like a scam. It has purported functionality, but I can only assume it is broken--or is it a brilliant way to get money from "Donors" rather than "Customers"? Curious. Not sure about the legal distinctions between the two, but the programmer may be absolved of any responsibility for his product's alleged functionality.
+2
I have not had the time to bring up a help file, or setup a site for BM until now
because I've been busy implementing new features in the software.
But it is being designed. and will show up at some point in the future.
As far as support goes I have always payed close attention to my users request.
if you would of tried to send an email instead of jumping the guns, and complaining like a school girl you probably would of gotten a reply within the hour.
BM Detects bonjour broadcasting servers only.
if your FTP server is not bonjour enabled, BM will not detect it's presence.
now will it do it for SMB servers that are not bonjour enabled.
thus the name "bonjour mounter"
----------------
If the software was a scam like you say, do you really think I would waste my time
begging for 10$ donations? PLEASE. I have better things to do.
I would charge 50$ for it and have you use the software only after you payed me, without a trail, or a preview like most software vendors do.
Donations are a way for people who enjoy the software to show the developer appreciation for it's work that is all, and honestly, I've gotten quite a bit of donations, to my greatest amazement.
PLEASE PLEASE by all means, if you do not like the software DELETE IT and move on.
I really do not care for your personal petty cash.
I will not be insulted by being called a fraud.
-5
But there appears one problem:
If I set the check box to "Launch at login", that won't happen.
I logged out, logged in again, but Bonjour Mounter did not start up.
When I launched it manually then, and looked back into the preferences, the checkbox was still activated. Then I looked into the Login Items in System Preferences, where Bonjour Mounter was not included in the list. I dragged it to the list and now, of course, it launches after the user logs in, as expected. But trying to achieve this using the built in preferences seems not to work!
I see this as a bug
-5
-5
I mean, if the desired network share is on another computer that I forgot to turn on first,
will Bonjour Mounter mount that share automatically as soon as that computer is available?
That would be of huuuuuuge use!
Provided that the computer you are trying to connect to broadcasts it's presence with Bonjour, it will get mounted as soon as it is seen.
+1
+3
Would be nice if i didnt have an icon cluttering the menubar.
Please could you get in touch with me - it's been 48 hours since I paid for a licence and I haven't heard a thing. You'll have my details from PayPal, or leave me a message here.
Y
+19
+19
+20
Pretty weird since all other file browsers show the volume just fine.
Here's the console output:
2009-08-02 11:20:15.923 Bonjour Mounter[350:2f03] Wait Over for for :Host:Gizzie Mount:/
2009-08-02 11:20:15.932 Bonjour Mounter[350:2f03] mount failed for server afp://Gizzie:548//, error == -36
2009-08-02 11:20:29.980 Bonjour Mounter[350:2f03] mount failed for server afp://10.0.1.3:548//, error == -43
2009-08-02 11:20:29.981 Bonjour Mounter[350:2f03] Mount Operation Finished for :Host:Gizzie Mount:/
Any help appreciated.
+1
"/" is not a network share point name.
if you use finder and connect to your phone, folders should appear.
use the name of one of the folders in the add window's share point text box.
+20
My stupid bad mistake. "root" was quite obviosly the mount point: the 99% work on a Mac made me think it was "/". =/
As a side note: I'm using Bonjour Mounter for wirelessly syncing documents to my iPhone for road use with iStorage. ChronoSync's scheduler handles the job of automatically starting the sync-up as soon as my jailbroken iPhone mounts as a Bonjour network drive via Netatalk.
From this point of view, an option to "Mount All at Startup" (a delay would be necessary I guess) would be the most welcome added feature/option in BM's preferences, so that the phone sync-up would start as soon as I log in or start my Mac up without even a mouse-click! =)
You'd be my hero then, and would donate with the utmost pleasure (although, well, guess I will soon anyways if I keep on with this use of mine).
Love,
Francesco
+27
Note that everything else (Finder, ChronoSync) continues to mount my AFP disk OK.
Any helpful suggestions would be welcome. I loved the ability of BM to auto-mount my AFP disk.
i run OS X with all the latest updates and BM still works like a charm,
did you try restarting the application ?
can you send me the logs ?
thank you .
+27
one of them has lower access rights than the other one.
The way AFP works is that once you authenticate with the server it shows you only what you are allowed to see.
so let's say you log in with a guest account on the server first.
you will see only the public shares.
and the your full power user will not even see his shares. thus the directory not found message... what you have to do is use only one user per server.
if that is not your case, then it is something i have not encountered yet.
+27
I had been trying to manually mount the AFP disk, with:
mkdir /Volumes/RAID
mount_afp afp://xxx:pass@Snowflake/RAID /Volumes/RAID
and it timed out with error 1069 (no server). Yet the finder mounts OK!!! So I tried...
mount_afp afp://xxx:pass@Snowflake.local/RAID ...
And it works! *BUT* I tried setting server to "Snowflake.local" in BonjourMounter but no fix :-(
Any ideas??
+27
Bonjour sees the AirportExtreme as "Snowflake" (and so does BJMounter).
TCP/IP sees the Airport as "Snowflake.local" (not Snowflake). This is some strangeness of Leopard that I can't work out. My only thought is to add an alias into /etc/hosts.
And I have no idea why Leopard suddenly started doing this :-(
is the default local domain
by default every Mac host will add that to it's host Name
it's normal.
+1
Hope you can solve this problem- I appreciate the your effort with BM!
but it seems it does not receive notification when the computer goes to sleep.
I'm looking into it.
+1
+1
Upon further testing, it appears there is still a problem with BM203 detecting server wake up.
BM203 detects server wake up in my case the first day-e.g. when BM has been started some time during the day, and the remote server wakes up the following morning. However, the next morning, BM does not detect the remote serve wake up. I just started the remote server and BM still did not detect it. It's like BM is not active even though it appears in the menu bar and the mounter window is open. The console log shows activity the first day BM detects, but nothing after that. Let me know if you need further info.
Thanks
Jeff
for the first day and the second day.
please.
+1
I will be collecting logs during next few days.
jeff
+1
Here is a console log I just took. This is not the case of BM not detecting when the Cube wakes-but maybe they both have the same solution. In this case, I am using the Finder to manually connect and disconnect to my Cube with my Backup HD. Each time I connect, BM is not automatically mounting the Backup HD.
I still must manually click the Backup HD (after selecting the Cube under SHARED) in the finder window to activate it.
Let me know if you need further information or logs.
Regards,
Jeff
===================================
11/2/09 12:46:04 PM Bonjour Mounter[169] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 12:47:30 PM com.apple.launchd[101] ([0x0-0x1a01a].com.gestosoft.Bonjour_Mounter[169]) Stray process with PGID equal to this dead job: PID 181 PPID 1 check_afp
11/2/09 12:47:37 PM Bonjour Mounter[1960] Resolving [JeffsMacCube]
11/2/09 12:47:37 PM Bonjour Mounter[1960] Scaning for samba hosts Thread Started
11/2/09 12:47:37 PM Bonjour Mounter[1960] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
---------------
Here I click on the Backup HD in the Finder window (after clicking on the Shared Cube icon
-----------------
11/2/09 12:47:37 PM Bonjour Mounter[1960] Did Resolved [JeffsMacCube] notifying mounter
11/2/09 12:47:37 PM Bonjour Mounter[1960] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
11/2/09 12:47:37 PM Bonjour Mounter[1960] mounted server afp://192.168.1.103:548/Backup%20HD, user == jrowe, refNum == -109
11/2/09 12:47:37 PM Bonjour Mounter[1960] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 12:47:37 PM Bonjour Mounter[1960] Scaning for samba hosts Thread ended
11/2/09 12:48:02 PM Bonjour Mounter[1960] DiskDisappearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 12:49:37 PM Bonjour Mounter[1960] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 12:49:37 PM Bonjour Mounter[1960] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 12:49:55 PM Bonjour Mounter[1960] DiskDisappearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 12:49:55 PM Bonjour Mounter[1960] DiskDisappearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 12:51:33 PM Bonjour Mounter[1960] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
you see the disk appeared and disappeared notification in the logs ? that's bonjour mounter telling you it noticed that the drive was mounted/unmounted outside of it's interface
it is possible that in the sharepoint list the status did not get updated properly, i will look into it.
what i would like you to try is to stop the sharing on the cube, and hen start it up again and see if BM notices it and tries to remount it.
send me the logs about it... please
Then try putting the cube to sleep, and waking it up again see if BM tries to mount it's shares when it comes back up.
send me the logs please...
you might not notice any change if you look at the mounted volumes in finder because Leopard keeps them on the desktop for a while even if the server has gone to sleep.
when the services is shutdown you will get a notification from the finder that the service has disconnected you, short after BM will try to unmount the shares with no success because the finder already did just that, but it it will reset it's status to offline.
at least this is what happens on all my 5 machines.
let me know how it goes on yours.
gratefully thank you !
Sandro.
+1
Here's the log file for the first case you requested: I turned off personal file sharing on the Cube, BM detected that and dismounted the Backup HD. Restarted PFS and BM did notice and
remounted.
Second case will follow shortly.
Jeff
=========
11/2/09 12:59:53 PM Bonjour Mounter[1984] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 1:05:19 PM Bonjour Mounter[1984] JeffsMacCube Left
11/2/09 1:05:19 PM Bonjour Mounter[1984] unmounted of Backup HD failed error= -35
11/2/09 1:05:19 PM Bonjour Mounter[1984] Unmount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 1:07:58 PM Bonjour Mounter[1984] DiskDisappearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 3:04:13 PM Bonjour Mounter[1984] Resolving [JeffsMacCube]
11/2/09 3:04:13 PM Bonjour Mounter[1984] Did Resolved [JeffsMacCube] notifying mounter
11/2/09 3:04:13 PM Bonjour Mounter[1984] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
11/2/09 3:04:13 PM Bonjour Mounter[1984] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 3:04:13 PM Bonjour Mounter[1984] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 3:04:16 PM Bonjour Mounter[1984] Did Resolved [JeffsMacCube] notifying mounter
11/2/09 3:04:16 PM Bonjour Mounter[1984] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
11/2/09 3:04:17 PM Bonjour Mounter[1984] mounted server afp://192.168.1.103:548/Backup%20HD, user == jrowe, refNum == -113
11/2/09 3:04:17 PM Bonjour Mounter[1984] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 3:04:17 PM Bonjour Mounter[1984] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 3:11:58 PM Bonjour Mounter[1984] DiskDisappearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 3:11:59 PM Bonjour Mounter[1984] JeffsMacCube Left
11/2/09 3:11:59 PM Bonjour Mounter[1984] unmounted of Backup HD failed error= -35
11/2/09 3:11:59 PM Bonjour Mounter[1984] Unmount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 3:11:59 PM Bonjour Mounter[1984] Unmount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 3:13:33 PM Bonjour Mounter[1984] Resolving [JeffsMacCube]
11/2/09 3:13:33 PM Bonjour Mounter[1984] Did Resolved [JeffsMacCube] notifying mounter
11/2/09 3:13:33 PM Bonjour Mounter[1984] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
11/2/09 3:13:33 PM Bonjour Mounter[1984] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
11/2/09 3:13:34 PM Bonjour Mounter[1984] mounted server afp://192.168.1.103:548/Backup%20HD, user == jrowe, refNum == -114
11/2/09 3:13:34 PM Bonjour Mounter[1984] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 3:13:34 PM Bonjour Mounter[1984] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
thank you Jeff
so service discovery is working properly.
+1
Here's the second case you requested: I put the Cube to sleep, BM dismounted BackHD. I waited about 5min until Leopard disconnected from the Cube, woke the Cube and BM did
remount the BackupHD. I will now wait until tomorrow morning when both machines wake
(cube at 0545, mini at 0600). That is when BM seems to be stalled and not notice the Cube
waking (maybe OK the first time after starting BM, but second day it fails). Will post logs to you tomorrow. Thanks for you help.
Jeff
==================11/2/09 3:13:34 PM Bonjour Mounter[1984] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 3:21:46 PM Bonjour Mounter[1984] JeffsMacCube Left
11/2/09 3:21:46 PM Bonjour Mounter[1984] JeffsMacCube Left
11/2/09 3:24:02 PM Bonjour Mounter[1984] unmounted of Backup HD failed error= -35
11/2/09 3:24:02 PM Bonjour Mounter[1984] Unmount operation Finished for :Host:JeffsMacCube Mount:Backup HD
11/2/09 3:24:02 PM Bonjour Mounter[1984] DiskDisappearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 3:24:02 PM Bonjour Mounter[1984] DiskDisappearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
11/2/09 3:27:00 PM Bonjour Mounter[1984] Resolving [JeffsMacCube]
11/2/09 3:27:00 PM Bonjour Mounter[1984] Did Resolved [JeffsMacCube] notifying mounter
11/2/09 3:27:00 PM Bonjour Mounter[1984] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
11/2/09 3:27:00 PM Bonjour Mounter[1984] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
it is very appreciated!!!
+1
No change in the console log from yesterday while I was away. The Mini has been in sleep mode until this morning (Friday ). I just woke the cube this morning and BM is still not responding on my Mini I plan to have the Mini wake before the Cube tomorrow morning to see if that makes a difference.
jeff
================
there should at least be some bonjour notifications in the logs.
If there is no notifications in the logs, there can be only 2 problems
1: BM froze up... never saw it do that but hey... it's possible.
2: something in your system is not reacting as it's supposed to.
Question : do you see the cube show up after your mini wakes from sleep?
to see this for real you would need to:
1: put the cube to sleep, and then wait for the cube to disappear from the mini's finder,
2: and then put the mini to sleep.
3: wake the cube, wait a bit for the first notifications to pass like 15 minutes.
4: wake the mini.
One thing you should not forget is that the bonjour protocol is constructed in a way that at first it will advertise itself often, but as time passes, it will wait longer and longer before sending a new advertise, to avoid unnecessary network traffic. So if the cube has been up for a long while before the mini comes up, it "might" be possible that it can take a while before the mini receives notifications from the cube.
as i remember the computer is supposed to ask the network who's around when it starts up, but I'm not totally sure if this happens when it wakes or just when the system is started.
Thank you very much for your help Jeff, it's really appreciated.
+1
sorry I did not report back lately, we had two power outages, so the computers had to restart.
Anyway, I now have the Mini and BM waking at 0530, the Cube at 0545. Did not make any difference after the first day (15/2/09), BM still not responding to the Cube wake up. I just manually woke the Cube and BM failed again. Here's the log file from 15/2/09.
(Note there is a network error reported on 16/2 at 0530?? Maybe that is a problem?)
================
15/2/09 5:30:33 AM ScreenSaverEngine[4183] Screen saver is running in blackout mode.
15/2/09 5:40:02 AM kernel Stealth Mode connection attempt to UDP 192.168.1.106:62005 from 68.87.76.178:53
15/2/09 5:44:49 AM Bonjour Mounter[265] Resolving [JeffsMacCube]
15/2/09 5:44:49 AM Bonjour Mounter[265] Did Resolved [JeffsMacCube] notifying mounter
15/2/09 5:44:50 AM Bonjour Mounter[265] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
15/2/09 5:44:50 AM Bonjour Mounter[265] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
15/2/09 5:44:53 AM Bonjour Mounter[265] Did Resolved [JeffsMacCube] notifying mounter
15/2/09 5:44:53 AM Bonjour Mounter[265] mount failed for server afp://JeffsMacCube:548/Backup%20HD, error == -36
15/2/09 5:44:53 AM kernel AFP_VFS afpfs_mount: /Volumes/Backup HD, pid 265
15/2/09 5:44:53 AM Bonjour Mounter[265] DiskAppearedCallback diskDescription = {
DAVolumeKind = afpfs;
DAVolumeMountable = 1;
DAVolumeName = "Backup HD";
DAVolumeNetwork = 1;
DAVolumePath = file://localhost/Volumes/Backup%20HD/;
}
15/2/09 5:44:53 AM Bonjour Mounter[265] mounted server afp://192.168.1.102:548/Backup%20HD, user == jrowe, refNum == -108
15/2/09 5:44:53 AM Bonjour Mounter[265] Mount operation Finished for :Host:JeffsMacCube Mount:Backup HD
15/2/09 5:50:20 AM kernel Stealth Mode connection attempt to UDP 192.168.1.106:55210 from 68.87.76.178:53
15/2/09 5:50:29 AM kernel Stealth Mode connection attempt to UDP 192.168.1.106:60558 from 68.87.76.178:53
15/2/09 6:00:05 AM /usr/sbin/ocspd[4270] starting
15/2/09 6:00:54 AM /System/Library/CoreServices/backupd[4278] Starting standard backup
15/2/09 9:32:52 PM kernel System Sleep
16/2/09 5:30:00 AM kernel Wake reason = RTC
16/2/09 5:30:00 AM kernel System Wake
16/2/09 5:30:00 AM kernel EIR is not supported.
16/2/09 5:30:03 AM mDNSResponder[17] ERROR: mDNSPlatformTCPConnect - connect failed: socket 47: Error 50 Network is down
16/2/09 5:30:03 AM mDNSResponder[17] ERROR: mDNSPlatformTCPConnect - connect failed: socket 47: Error 51 Network is unreachable
16/2/09 5:30:03 AM mDNSResponder[17] ERROR: mDNSPlatformTCPConnect - connect failed: socket 47: Error 51 Network is unreachable
16/2/09 5:30:03 AM mDNSResponder[17] ERROR: mDNSPlatformTCPConnect - connect failed: socket 47: Error 51 Network is unreachable
16/2/09 5:30:03 AM mDNSResponder[17] ERROR: mDNSPlatformTCPConnect - connect failed: socket 47: Error 51 Network is unreachable
16/2/09 5:30:03 AM mDNSResponder[17] ERROR: mDNSPlatformTCPConnect - connect failed: socket 47: Error 51 Network is unreachable
16/2/09 5:30:04 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 5 seconds
16/2/09 5:30:07 AM configd[14] rtmsg: error writing to routing socket
16/2/09 5:30:07 AM kernel AirPort: Link Up on en1
16/2/09 5:30:07 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 2 seconds
16/2/09 5:30:08 AM kernel AFPSleepWakeHandler: waking up
16/2/09 5:30:43 AM ScreenSaverEngine[7060] Screen saver is running in blackout mode.
Cube wakes at 0545
16/2/09 5:58:02 AM /System/Library/CoreServices/backupd[7128] Starting standard backup
16/2/09 5:58:02 AM /System/Library/CoreServices/backupd[7128] Backing up to: /Volumes/External HD/Backups.backupdb
16/2/09 5:58:09 AM /System/Library/CoreServices/backupd[7128] No pre-backup thinning needed: 340.2 MB requested (including padding), 130.50 GB available
16/2/09 5:59:17 AM /System/Library/CoreServices/backupd[7128] Copied 4754 files (21.0 MB) from volume JeffsMacMini HD.
16/2/09 5:59:17 AM /System/Library/CoreServices/backupd[7128] No pre-backup thinning needed: 315.0 MB requested (including padding), 130.48 GB available
16/2/09 5:59:25 AM /System/Library/CoreServices/backupd[7128] Copied 112 files (110 bytes) from volume JeffsMacMini HD.
16/2/09 5:59:27 AM /System/Library/CoreServices/backupd[7128] Starting post-backup thinning
BM Detects that then network has come online but it get's excited before the ip is actually assigned. i'll implement a detection and see if that fixes things.
+1
glad to hear you may have a solution. Let me know how to test a beta version if needed.
I will be around off and on for the next week.
Regards,
jeff
bonjour.mounter@gmail.com
+2
+6
Just tested BM 1.9.2 and it seems to work much better for me.
But I think that you've put too much work into BM...
It shouldn't be necessary to create your own username/password dialog-box when prompting for password - the system (Finder) will do that for you.
please try the following command from your terminal.app:
open smb://your-username-here@server-name/share-point-name
This way the system will also (automatiaclly) remember the password - and reuse it for every mount against the same server - no need for you to do any additional programming.
Using the system for prompting is not only more os-compatible - but it also makes your application much more thrustworthy.
Users are somewhat suspicious towards applications that prompts for username/password (fear of username/password theft)
kind regards Uffe
There is not much many ways for me to control the system dialogue from the API that is available.
If you know of a way to do it, you should let me know.
Thanks.
+6
What I saw with BM 1.9 was the correct username/password dialog box - but the wrong username filled out. In parallel with that background threads seemed to be attempting to login with the correct username but an empty password - after 3 attempts in less than a second my account was blocked before I could fillout the username/password dialog.
(I admit) without knowing your code I'm just guessing :-)
Kind regards Uffe
The only thing that has changed and the reason why you do not see the threads asking for a password is that before the mounting threads get launched, BM will check if any of the mounts require a password.
It will ask for that password and then pass it along to the mounting procedure as needed.
The password will remain in RAM for the duration of the execution of the program. once BM is closed the passwords are lost they are not saved to disk.
This procedure allows me to mount multiple shares from the same host with the same username/password.
as opposed to asking the system to validate it against the server and THEN ask the user for the password.
Since BM is a multi threaded application, up to 4 mounts can happen at the same time
thus causing the system to ask to 4 passwords at once even if they are for the same host. witch is not a desired situation for the users.
NOTE: This password scheme, was developed expressly for you, since no one else has mentioned the need for it. If you have now lost trust in BM because the password dialogue is a custom dialogue, I do not know what to say else than, do what you think is best, even if it means discontinuing the use of BM.
Best Regards.
+6
Kind regards Uffe :-)
+6
Tried BM 1.9 - deleted all my mounts from BM and recreated them again with username filled in - but with empty passwords.
But things are still not working.
BM gave me a auth-dialog box - but the username from BM is not transferred into it - instead it defaulted to my mac-logon name.
Also it still seems to perform repeating logon attempts in the background (before I've entered my password in the auth-dialog-box)
Last (a a consequence of the last problem) it is pestering me with an "invalid username or password ok-dialog-box" that I cannot get rid of - pressing OK just makes it reappear.
BM 1.9 is by no means a succesful release ;-)
and well, you are the trail :)
+6
BTW: I'll send you an email - I'd be happy to do some testing for you :-)
I run a g4 with tiger server 10.4.11 with all my music an movies on it.
It has 3 different shares running afp only across a wired network.
All the shares will mount through the finder and the server shows in the sidebar too.
BM says it cannot connect to the server even though finder can?
I have tried lots of variations on the sharepoint and server but still no dice :(
Any ideas?
BTW do you have an email address so I could send logs or whatever you need to fix this.
Thanks
I check this site many times a day.
it seems that BM does not like having empty name and password fields.
As I have my server sharing through the guest account to my household this is a problem.
BM works fine and mounts ok when username and password is entered.
Can you please add a checkbox on the edit share panel to use guest login for the particular share.
Thanks for the great work.
Apologies if I was ranting before.
but that procedure is left to the Operating system, it is not past of BM.
There is nothing in my keychain for the server.
When I mount the share at login with the finder there is no username/password dialog.
Also when presented with a username/password dialog I can choose guest which then mounts the share.
Why cant BM do this if the finder can?
Thanks
Michal Král rated on 27 Dec 2010