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!



Share:
Notifications
Clear all

Doesn't connect to Mac shared folder

9 Posts
2 Users
2 Likes
649 Views
(@Anonymous)
Joined: 1 second ago
Posts: 0
Topic starter  

Hi Hans, I'm adding the log as requested. This is a continuation from my report here: https://www.tweaking4all.com/software/macosx-software/connectmenow-v4/#comment-595071

 

11:53:50 │ Mount requested for: "vurtPro"
11:53:50 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
11:53:50 │ - Doing default short mount delay (1 second)
11:53:51 │ - Starting mount background task
11:53:51 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
11:53:51 │ - Enabled timer for potential extra mount attempts
11:53:51 │ - Thread started

11:53:53 │ Mount status update:
         │ Mount/Open Networkshare feedback (SystemDefault): 
         │ Mount attempt with Calling Apple NetFS API:
         │ 
         │ - LOGIN: Username and Password known - User login with hidden window
         │   URL: smb://192.168.1.50/Volumes
         │   Mount directory: macOS will mount against a mount directory in "/Volumes"
         │ - Error - Unknown user or invalid password

11:53:53 │ Thread - Calling for forced status update (only shows results if something changed)

11:53:54 │ -- STATUS UPDATE - THREAD CALLBACK ------------------------------------------------
         │ 
11:53:54 │ Update type
         │  - Initial read     : -
         │  - Timed Interval   : -
         │  - Get Network info : -
         │  - Forced Update    : YES
         │ 
         │ Status Interval     : 10000 milliseconds
         │ Interval Interrupts : 500 milliseconds
         │ Failed mount after  : 30000 milliseconds
         │ 
         │ Default gateway     : 192.168.1.1 (MAC: D4:5D:64:34:65:88)
         │ 
11:53:54 │ - Mount Status Updated: Counted 0 active share(s)
11:53:54 │ - Matched 0 Network shares. (matched all)
11:53:54 │ 
         │ -- STATUS UPDATE - COMPLETED ------------------------------------------------------
11:53:54 │ - RETRY MOUNT TIMER: Stopping timer
11:53:54 │ - RETRY MOUNT TIMER: Quiting, nothing left to retry, and no Fallback servers left either
11:53:54 │ - Updating "Mount onAppear" list
11:53:54 │ - Updating "Mount onAppear" list

11:53:54 │ Updating Tray Menu

11:54:49 │ Updating Share Details

11:54:49 │ Updating Tray Menu

11:54:50 │ Updating Share Details

11:54:50 │ Updating Tray Menu

11:54:53 │ Updating Share Details

11:54:53 │ Updating Tray Menu

11:54:55 │ Updating Share Details

11:54:55 │ Updating Tray Menu

11:54:55 │ Updating Share Details

11:54:55 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:56 │ Updating Share Details

11:54:56 │ Updating Tray Menu

11:54:57 │ Updating Share Details

11:54:57 │ Updating Tray Menu

11:55:02 │ Mount requested for: "vurtPro"
11:55:02 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
11:55:02 │ - Doing default short mount delay (1 second)
11:55:03 │ - Starting mount background task
11:55:03 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
11:55:03 │ - Enabled timer for potential extra mount attempts
11:55:03 │ - Thread started

11:55:05 │ Mount status update:
         │ Mount/Open Networkshare feedback (SystemDefault): 
         │ Mount attempt with Calling Apple NetFS API:
         │ 
         │ - LOGIN: Username and Password known - User login with hidden window
         │   URL: smb://192.168.1.50/Volumes
         │   Mount directory: macOS will mount against a mount directory in "/Volumes"
         │ - Error - Mount failed (Error code: 2)

11:55:05 │ Thread - Calling for forced status update (only shows results if something changed)

11:55:05 │ -- STATUS UPDATE - THREAD CALLBACK ------------------------------------------------
         │ 
11:55:05 │ Update type
         │  - Initial read     : -
         │  - Timed Interval   : -
         │  - Get Network info : -
         │  - Forced Update    : YES
         │ 
         │ Status Interval     : 10000 milliseconds
         │ Interval Interrupts : 500 milliseconds
         │ Failed mount after  : 30000 milliseconds
         │ 
         │ Default gateway     : 192.168.1.1 (MAC: D4:5D:64:34:65:88)
         │ 
11:55:05 │ - Mount Status Updated: Counted 0 active share(s)
11:55:05 │ - Matched 0 Network shares. (matched all)
11:55:05 │ 
         │ -- STATUS UPDATE - COMPLETED ------------------------------------------------------
11:55:05 │ - RETRY MOUNT TIMER: Stopping timer
11:55:05 │ - RETRY MOUNT TIMER: Quiting, nothing left to retry, and no Fallback servers left either
11:55:05 │ - Updating "Mount onAppear" list
11:55:05 │ - Updating "Mount onAppear" list

11:55:05 │ Updating Tray Menu

11:57:03 │ Updating Share Details

11:57:03 │ Updating Tray Menu

11:57:03 │ Updating Share Details

11:57:03 │ Updating Tray Menu

11:57:12 │ Mount requested for: "vurtPro"
11:57:12 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
11:57:12 │ - Doing default short mount delay (1 second)
11:57:13 │ - Starting mount background task
11:57:13 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
11:57:13 │ - Enabled timer for potential extra mount attempts
11:57:13 │ - Thread started

11:57:16 │ Mount status update:
         │ Mount/Open Networkshare feedback (Commandline): 
         │ Mount attempt through Commandline:
         │ 
         │ - Mount path: /Users/raylam/MountPoints/Volumes (192.168.1.50)
         │ - CMD: mount_smbfs "//username:password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Volumes (192.168.1.50)"- Error - Possible error occured. Shell may have returned a fail code
         │ - Result: Mount request did not return an error (not a guarantee that it worked though!)

11:57:16 │ Thread - Calling for forced status update (only shows results if something changed)

11:57:17 │ -- STATUS UPDATE - THREAD CALLBACK ------------------------------------------------
         │ 
11:57:17 │ Update type
         │  - Initial read     : -
         │  - Timed Interval   : -
         │  - Get Network info : -
         │  - Forced Update    : YES
         │ 
         │ Status Interval     : 10000 milliseconds
         │ Interval Interrupts : 500 milliseconds
         │ Failed mount after  : 30000 milliseconds
         │ 
         │ Default gateway     : 192.168.1.1 (MAC: D4:5D:64:34:65:88)
         │ 
11:57:17 │ - Mount Status Updated: Counted 0 active share(s)
11:57:17 │ - Matched 0 Network shares. (matched all)
11:57:17 │ 
         │ -- STATUS UPDATE - COMPLETED ------------------------------------------------------
11:57:17 │ - RETRY MOUNT TIMER: Stopping timer
11:57:17 │ - RETRY MOUNT TIMER: Quiting, nothing left to retry, and no Fallback servers left either
11:57:17 │ - Updating "Mount onAppear" list
11:57:17 │ - Updating "Mount onAppear" list

11:57:17 │ Updating Tray Menu

11:57:51 │ - Processing Auto mounts that should mount at Startup
11:57:51 │ - Quick network check: Network available

11:57:51 │ Mount requested for: "vurtPro"
11:57:51 │ - Max Attempts  = 1
         │   Attempts Left = 0
         │   Last Attempt  = 11:57:12
11:57:51 │ - Request denied: No mount attempts left
11:57:51 │ - Auto mounts requested for 1 defined share

11:58:15 │ Mount requested for: "vurtPro"
11:58:15 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
11:58:15 │ - Doing default short mount delay (1 second)
11:58:16 │ - Starting mount background task
11:58:16 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
11:58:16 │ - Enabled timer for potential extra mount attempts
11:58:16 │ - Thread started

11:58:16 │ Mount status update:
         │ Mount/Open Networkshare feedback (Commandline): 
         │ Mount attempt through Commandline:
         │ 
         │ - Mount path: /Users/raylam/MountPoints/Volumes (192.168.1.50)
         │ - CMD: mount_smbfs "//username:password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Volumes (192.168.1.50)"- Error - Possible error occured. Shell may have returned a fail code
         │ - Result: Mount request did not return an error (not a guarantee that it worked though!)

11:58:16 │ Thread - Calling for forced status update (only shows results if something changed)

11:58:16 │ -- STATUS UPDATE - THREAD CALLBACK ------------------------------------------------
         │ 
11:58:16 │ Update type
         │  - Initial read     : -
         │  - Timed Interval   : -
         │  - Get Network info : -
         │  - Forced Update    : YES
         │ 
         │ Status Interval     : 10000 milliseconds
         │ Interval Interrupts : 500 milliseconds
         │ Failed mount after  : 30000 milliseconds
         │ 
         │ Default gateway     : 192.168.1.1 (MAC: D4:5D:64:34:65:88)
         │ 
11:58:16 │ - Mount Status Updated: Counted 0 active share(s)
11:58:16 │ - Matched 0 Network shares. (matched all)
11:58:16 │ 
         │ -- STATUS UPDATE - COMPLETED ------------------------------------------------------
11:58:17 │ - RETRY MOUNT TIMER: Stopping timer
11:58:17 │ - RETRY MOUNT TIMER: Quiting, nothing left to retry, and no Fallback servers left either
11:58:17 │ - Updating "Mount onAppear" list
11:58:17 │ - Updating "Mount onAppear" list

11:58:17 │ Updating Tray Menu

 

edit: removed username and password from log

This topic was modified 9 months ago by Anonymous

   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2641
 

Hi Ray,

When looking at the log, the first mount attempt (using the macOS API) looks like there is a username/password issue ...

11:53:50 │ Mount requested for: "vurtPro"
11:53:50 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
11:53:50 │ - Doing default short mount delay (1 second)
11:53:51 │ - Starting mount background task
11:53:51 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
11:53:51 │ - Enabled timer for potential extra mount attempts
11:53:51 │ - Thread started

11:53:53 │ Mount status update:
         │ Mount/Open Networkshare feedback (SystemDefault): 
         │ Mount attempt with Calling Apple NetFS API:
         │ 
         │ - LOGIN: Username and Password known - User login with hidden window
         │   URL: smb://192.168.1.50/Volumes
         │   Mount directory: macOS will mount against a mount directory in "/Volumes"
         │ - Error - Unknown user or invalid password

 

The second mount attempt returns a mount error 2, which could mean "no such file or directory" (this is a pretty vague one).
This could mean a few things, the most common one being that the proper SMB version is not supported.

11:55:02 │ Mount requested for: "vurtPro"
11:55:02 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
11:55:02 │ - Doing default short mount delay (1 second)
11:55:03 │ - Starting mount background task
11:55:03 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
11:55:03 │ - Enabled timer for potential extra mount attempts
11:55:03 │ - Thread started

11:55:05 │ Mount status update:
         │ Mount/Open Networkshare feedback (SystemDefault): 
         │ Mount attempt with Calling Apple NetFS API:
         │ 
         │ - LOGIN: Username and Password known - User login with hidden window
         │   URL: smb://192.168.1.50/Volumes
         │   Mount directory: macOS will mount against a mount directory in "/Volumes"
         │ - Error - Mount failed (Error code: 2)

And the 3rd attempt shows that Terminal "mount" (command-line) is not returning an error code, which is unfortunately not a guarantee for anything. 😞 
I did notice the special characters in your password. Does it start with "7%21f ..."? Or "7!f ..."? (I removed it from your post).

11:57:12 │ Mount requested for: "vurtPro"
11:57:12 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
11:57:12 │ - Doing default short mount delay (1 second)
11:57:13 │ - Starting mount background task
11:57:13 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
11:57:13 │ - Enabled timer for potential extra mount attempts
11:57:13 │ - Thread started

11:57:16 │ Mount status update:
         │ Mount/Open Networkshare feedback (Commandline): 
         │ Mount attempt through Commandline:
         │ 
         │ - Mount path: /Users/raylam/MountPoints/Volumes (192.168.1.50)
         │ - CMD: mount_smbfs "//username:password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Volumes (192.168.1.50)"- Error - Possible error occured. Shell may have returned a fail code
         │ - Result: Mount request did not return an error (not a guarantee that it worked though!)

 

So from seeing this I can only guess one of these issues (caused by CMN or not):

  • Your share uses a SMB version that doesn't match up with the SMB version your other Mac is using.
    Unless the other machine runs a reasonably recent macOS version, then I wouldn't expect this to be na issue.
  • Your username or password has interfering characters in it. This may or may not be the case.
    For example "%21" in a password is pretty bad as it will be converted to an exclamation point. 
    I carefully assume you had "!' in your password and not "%21", so in that case this wouldn't be the issue either.

 

Two things to try:

1) Can you connect to the other share through Finder?

If yes, the let us see what the output of "mount" (in Terminal) looks like).

2) Can you try a manual mount in Terminal and see if that shows us some info?

Steps in Terminal:

mkdir /Users/raylam/MountPoints/Test
mount_smbfs "//Ray%20Lam:password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"

(of course: replace "password" with your password) 

This should mount your share, or very maybe display an error message.
If nothing is shown, see if there is anything to be found in "/Users/raylam/MountPoints/Test", and/or check the output of "mount" to see if the share has been mounted.


   
ray reacted
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
Topic starter  

Thanks so much for helping to troubleshoot @hans.

 

Posted by: @hans

  • Your username or password has interfering characters in it. This may or may not be the case.
    For example "%21" in a password is pretty bad as it will be converted to an exclamation point. 
    I carefully assume you had "!' in your password and not "%21", so in that case this wouldn't be the issue either.

Yes indeed, I have "!" in my password.

 

Posted by: @hans

Two things to try:

1) Can you connect to the other share through Finder?

If yes, the let us see what the output of "mount" (in Terminal) looks like).

Here's the output:

raylam@raylam ~ % mount
/dev/disk3s1s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk3s6 on /System/Volumes/VM (apfs, local, noexec, journaled, noatime, nobrowse)
/dev/disk3s2 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
/dev/disk3s4 on /System/Volumes/Update (apfs, local, journaled, nobrowse)
/dev/disk1s2 on /System/Volumes/xarts (apfs, local, noexec, journaled, noatime, nobrowse)
/dev/disk1s1 on /System/Volumes/iSCPreboot (apfs, local, journaled, nobrowse)
/dev/disk1s3 on /System/Volumes/Hardware (apfs, local, journaled, nobrowse)
/dev/disk3s5 on /System/Volumes/Data (apfs, local, journaled, nobrowse, protect)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
/Applications/CARROTweather.app on /private/var/folders/jn/0jjl8phs3ss9n2bm5kcmwqtr0000gq/T/AppTranslocation/24AEBE8A-831F-46FC-82BE-666C00993B56 (nullfs, local, nodev, nosuid, read-only, nobrowse, mounted by raylam)
/Applications/Spark.app on /private/var/folders/jn/0jjl8phs3ss9n2bm5kcmwqtr0000gq/T/AppTranslocation/2F7D6965-6C05-4FC5-86C8-075C9AEFBA1F (nullfs, local, nodev, nosuid, read-only, nobrowse, mounted by raylam)
/Applications/Camera Settings.app on /private/var/folders/jn/0jjl8phs3ss9n2bm5kcmwqtr0000gq/T/AppTranslocation/4C495AC8-F5D3-4E24-8385-5DF1258F6B0D (nullfs, local, nodev, nosuid, read-only, nobrowse, mounted by raylam)
//Ray%20Lam@vurtPro._smb._tcp.local/Downloads on /Volumes/Downloads (smbfs, nodev, nosuid, mounted by raylam)

 

I recognize the last line indicates the share is mounted.

 

Posted by: @hans

2) Can you try a manual mount in Terminal and see if that shows us some info?

Steps in Terminal:

mkdir /Users/raylam/MountPoints/Test
mount_smbfs "//Ray%20Lam:password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"

(of course: replace "password" with your password) 

This should mount your share, or very maybe display an error message.
If nothing is shown, see if there is anything to be found in "/Users/raylam/MountPoints/Test", and/or check the output of "mount" to see if the share has been mounted.

Here's what I'm getting, quite odd:

raylam@raylam ~ % mkdir /Users/raylam/MountPoints/Test
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:!password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
zsh: event not found: f3athering67@192.168.1.50/Volumes
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:%21password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: server rejected the connection: Authentication error
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:!password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
zsh: event not found: f3athering67@192.168.1.50/Volumes
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:%21password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: mount error: /Users/raylam/MountPoints/Test: No such file or directory
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:%21password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: mount error: /Users/raylam/MountPoints/Test: No such file or directory
raylam@raylam ~ % mkdir /Users/raylam/MountPoints/Test                                                            
mkdir: /Users/raylam/MountPoints/Test: File exists
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:%21password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: mount error: /Users/raylam/MountPoints/Test: No such file or directory

 

"!" doesn't work, but "%21" is telling me /Test doesn't exist even though it does.

 

 

This post was modified 9 months ago 2 times by Anonymous

   
Hans reacted
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2641
 

Excellent testing! Well done! 👍 

Is it an option to change your password to a password without a "!"? Even if it is just to test. 😊 

In case this still keeps failing: a space in a username is frowned upon as well and could possibly cause issues.
Even Microsoft recommends against using spaces in usernames. (MSDN documentation)

Quote:

    Logon names can contain all other special characters, including spaces, periods, dashes, and underscores.
    But it's generally not a good idea to use spaces in account names.

 

Note: These days Windows almost forces you to use your Microsoft account, and as I recall this is based on your email address (no spaces allowed there as well, and maybe it works in your setup).

Note: The %21 and %20 are automatic replacements for exclamation point and space (URL encoding).


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
Topic starter  

Hi @hans, I changed my password so it's alphabets and one numeral. I confirmed it works by connecting with Finder. In Terminal, still getting the same error.

 

raylam@raylam ~ % mkdir /Users/raylam/MountPoints/Test
mkdir: /Users/raylam/MountPoints/Test: File exists
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:f3athering@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: mount error: /Users/raylam/MountPoints/Test: No such file or directory
This post was modified 9 months ago by Anonymous

   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2641
 

The "No such file or directory" is probably the worst error message ever for mount commands, since its so very very vague 😜 

I assume "/Users/raylam/MountPoints/Test" exists (your mkdir statement confirms this) and is not mounted to anything.
The latter you can test with the "mount" statement in Terminal without any parameters, which shows something like this:

/dev/disk1s5s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk1s4 on /System/Volumes/VM (apfs, local, noexec, journaled, noatime, nobrowse)
... (lines removed)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
//username@192.168.1.100/AllShares on /Volumes/AllShares (smbfs, nodev, nosuid, mounted by username)

The lines that start with "//", at the beginning of the line, are the ones to look for.
In this example it shows in the last line, my NAS mounter to /Volumes/AllShares.
Just make sure "/Users/raylam/MountPoints/Test" is not listed here.
To be honest: I do not expect to see it listed.

Next thing to try is testing the mount with the system call (in Advanced Options) in CMN now that you have changed your password.
If this doesn't work, then I may need to "undo" the %-character (%20) as replacements for special characters.

Next; test if mount_smbfs works with a space:

mount_smbfs "//Ray Lam:password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"

And if that fails, and i know this can be cumbersome, please try with a username that does not have a space in it.
As mentioned before: per Microsoft recommendation, it is better to not have a space in your username anyway. But I'd be happy to see if we somehow get this to work.


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
Topic starter  

Posted by: @hans

Next thing to try is testing the mount with the system call (in Advanced Options) in CMN now that you have changed your password.
If this doesn't work, then I may need to "undo" the %-character (%20) as replacements for special characters.

Next; test if mount_smbfs works with a space:

mount_smbfs "//Ray Lam:password@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"

And if that fails, and i know this can be cumbersome, please try with a username that does not have a space in it.
As mentioned before: per Microsoft recommendation, it is better to not have a space in your username anyway. But I'd be happy to see if we somehow get this to work.

 

Hi @hans, here's my experiment:

raylam@raylam ~ % mount_smbfs "//Ray Lam:f3athering@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: URL parsing failed, please correct the URL and try again: Invalid argument
raylam@raylam ~ % mount_smbfs "//Ray Lam:f3athering@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: URL parsing failed, please correct the URL and try again: Invalid argument
raylam@raylam ~ % mount_smbfs "//Ray%20Lam:f3athering@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: server rejected the connection: Authentication error
raylam@raylam ~ % mount_smbfs "//ray:f3athering@192.168.1.50/Volumes" "/Users/raylam/MountPoints/Test"
mount_smbfs: server rejected the connection: Authentication error

 

I tried username with space, username with %20, and also a new username without space.

And I confirm the password is correct because I logged in via Finder.

 

This is very perplexing!

 

 


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2641
 

Apologies for the delay ... I'm in the middle of moving, so that takes quite a bit of time, not to mention exhausting with the current heat.

Definitely odd that mount_smbfs fails on all combo's. Never seen that.
Are you by any chance using a domain controller?
Or is your NAS/server dated (eg. running an old SMB version)?

(again apologies for the late reply, and when I overlooked something - just trying to answer on a few minutes "moving" break 😉 )


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
Topic starter  

The folder I'm connecting to is another MacBook Pro, running Monterey. The one I'm using to connect is on Ventura.

 

The odd thing is I can connect with Finder.

 

No need for apologies, I appreciate your time and help with this, moving sucks!


   
ReplyQuote
Share: