Forum Replies Created
-
AuthorPosts
-
May 5, 2009 at 11:01 pm in reply to: Automounting hidden shares via WG Manager w/ 10.5 clients acting weird #376121
Mr_Dennis
ParticipantBelieve it or not, it was a matter of trial and error. I’m happy I could help you out.
One last final thing. If you wanted to hide a SMB share point you’ll need a different URL E.g. “smb://ipaddress/Data/; ;”. i.e. a slash followed by a semicolon, a space and then another semicolon.
Dennis
May 5, 2009 at 1:26 am in reply to: Automounting hidden shares via WG Manager w/ 10.5 clients acting weird #376117Mr_Dennis
ParticipantI think I’ve found a suitable workaround solution!!! 😀
However, this only appears to work with login items, not group share points. You’ll need to modify the URL so it reads “afp://ipaddress/Data/ .” You basically need to put a slash after the share point name, then a space character followed by a full stop (period).
This worked for me. Let me know how you got on…
Dennis
May 4, 2009 at 11:46 pm in reply to: Automounting hidden shares via WG Manager w/ 10.5 clients acting weird #376116Mr_Dennis
ParticipantBasically I don’t have a solution for how to mount a share point without a space in the name. However if you add a space to the share point’s name, you should be able to have it mount as a hidden volume. So in your instance, if you rename your “Data” share point to “Date 1” it should work.
In my case, I’m putting the share point in as a login item and when the share point has a space in it, Workgroup Manager will automatically put a %20 to substitute the space character. I then need to remove the %20 and replace it with a space. This is only required if it’s a login item. So if I was to add your renamed share point as a login item, it would appear in Workgroup Manager as “afp://ipaddress/Data%201” and I’ll then need to remove the %20 so it’ll look like “afp://ipaddress/Data 1”.
Even though I’m adding my share point as a login item, I still get the same results as a group share point i.e. if the share point has a space in the name it will mount as a hidden volume. The only difference is you do not need to remove the %20 from the URL when it’s a group share point.
Dennis
May 4, 2009 at 6:58 am in reply to: Automounting hidden shares via WG Manager w/ 10.5 clients acting weird #376109Mr_Dennis
ParticipantI’ve posted this reply on another post but I think they are related….
I too am experiencing this issue. I did notice one unusual thing. If the share point has a space in the name e.g. “File Server” as long as you remove the “%20” from the login item URL, the share point will mount as a hidden volume. Well that’s what I’m experiencing and have been able to replicate. I’d be curious if you experience the same result.
It appears the NetAuthAgent is responsible for AFP & SMB requests, and as a result it is prompting the user to login again. If you issue a ‘killall NetAuthAgent’ from the terminal, it will kill this process along with the login dialog box. Not really a solution but hopefully this information will help in diagnosing this issue.
Dennis
Mr_Dennis
ParticipantI too am experiencing this issue. I did notice one unusual thing. If the share point has a space in the name e.g. “File Server” as long as you remove the “%20” from the login item URL, the share point will mount as a hidden volume. Well that’s what I’m experiencing and have been able to replicate. I’d be curious if you experience the same result.
Dennis
-
AuthorPosts
Recent Comments