Page 1 of 1
Forum

Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!

Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.

Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!



Notifications
Clear all

Beta 4.0.27 with multiple accounts on same smb server

6 Posts
2 Users
0 Reactions
20 Views
(@marjue)
Active Member
Joined: 4 months ago
Posts: 7
Topic starter   [#1581]

Hello

In the last stable version, there were no problems connecting to different shares with different accounts at the same SMB Server.

Now connecting to a share with another user then my normal on brings up the normal OS password requester. Typing in my different User/password is then working but the share is not routed with the special user but with my normal one.
Unmounting this wrong mount with the terminal brings up CoMeNow trying a reconnect. But the result is exactly the same.

The browse button at the "Server Address/Path:" input is not working until I input my "normal" user credentials.
I have tested the credentials of the "special" user in terminal with smbclient. Everything is fine.

Hope this helps you to bake this helpful tool even better :-)

Greetings
Marcus



   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 13 years ago
Posts: 3152
 

Hi Marcus,

thank you for reporting potential bugs/issues.

In the mount process nothing really changed in the past few version, and retrieving the list of shares hasn't changed since the first version 4 of ConnectMeNow.

The browse button for server path does require a proper username/password, otherwise the server will not release the list of shares.
Just yo make sure, I tested it with 2 accounts on my NAS (ConnectMeNow beta 4.0.27) and both accounts show the list of available shares correctly.

I'd be happy to see if I can reproduce your issue, to see if it is a bug and if I can fixe it.

What version of ConnectMeNow are you using?
What macOS version are you running?
Does the special user maybe have special characters in it?



   
ReplyQuote
(@marjue)
Active Member
Joined: 4 months ago
Posts: 7
Topic starter  

If you need it I can send you my CoMeNo config.



   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 13 years ago
Posts: 3152
 

Your config may not be helpful - thank you for offering though.

What may be helpful:

  • What version of ConnectMeNow are you using?
  • What macOS version are you running?
  • Does the special user username or password maybe have special characters in it?

 



   
ReplyQuote
(@marjue)
Active Member
Joined: 4 months ago
Posts: 7
Topic starter  

Hello Hans

Version 4.0.27 (last stable working was 2.0.18)
MacOS 27 Pub. Beta 4
The password uses a question mark.

I have to revert the statement that CoMeNow mounts the share with the wrong user. I was miss leaded with the "mounted by xyz" output from the "mount" command in MacOS.
Sorry for that.

But there is still the behavior with the macOS password request. For testing this out I installed the version 4.0.18 again. The requester does not come up with this version.
Back to version 4.0.27 the requester is back. I have to confirm my password in it. I have to confirm the volume to use. Then it's mounted. It comes up again. I have to cancel it. Then it does not come back.

I will try to get another MacBook to check it. Maybe there is something with stored passwords in the MacOS keystore or with MacOS 27 which CoMeNow beta does not like.

 

Greetings
Marcus



   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 13 years ago
Posts: 3152
 

Oh boy ... running a beta macOS version comes with challenges at times (which typically Apple fixes in the final release - which is why I no longer put much effort in fixing things for a beta macOS).

Just in case this is not related to that since it worked in 4.0.18:
Can you check if either of these options are checked (in v4.0.27)?

I did make some changes in how it behaves recently.
Maybe that is what you're seeing with the password requests (uncheck both - or toggle them on/off to make sure).



   
ReplyQuote
Share: