0

I am attempting to connect to a Windows file share from macOS 11.3. The IP is 192.168.0.6, however my Mac will ask for username and password. When I enter them, it will shake in error and will not connect.

I know the credentials are correct because my iPad Pro connects to the file share without any issues.

This is what safari shows when I go to the IP:

192.168.0.6

Improve this question
6
  • 1
    I changed your text a little to signal more strongly this is about a file share. // When you connect from your iPad, do you enter the same credentials?
    – Daniel B
    Commented May 25, 2021 at 12:59
  • @DanielB Thank you! Yes, it is the same credentials. It works fine on iPad but not Mac
    – Willm132
    Commented May 25, 2021 at 17:55
  • @DanielB any ideas?
    – Willm132
    Commented Jun 2, 2021 at 15:56
  • No, sorry. I don't use SMB on my Apple devices.
    – Daniel B
    Commented Jun 2, 2021 at 18:20
  • Can anyone help me with this?
    – Willm132
    Commented Jun 18, 2021 at 20:47

2 Answers 2

Reset to default
0

Try the Microsoft RDP App. You would also need to enable RDP connectivity on the server by pressing Win + Pause then clicking Remote Settings on the left.

Improve this answer
4
  • The issue is that this is a company server and I have no access to it at all. Just weird how it works on iPad but not the iMac.
    – Willm132
    Commented May 25, 2021 at 12:30
  • Can you clarify how you're connecting from each device?
    – hunsbct
    Commented May 25, 2021 at 12:33
  • On the iPad I just open Files app and click connect to server, I type in 192.168.0.6, enter my credentials, and it connects just fine. I do the same steps for Mac but it does not work
    – Willm132
    Commented May 25, 2021 at 17:56
  • Do you have any ideas to get this resolved?
    – Willm132
    Commented Jun 2, 2021 at 15:56
0

According to the post Cannot connect to SMB share, this is a regression in macOS 11.3. This problem didn't exist in macOS 11.2.

The workaround as given in the post was to use SMB2, as the problem apparently only arrives when using SMB3.

Use the following in Console:

echo "[default]" | sudo tee -a /etc/nsmb.conf
echo "protocol_vers_map=2" | sudo tee -a /etc/nsmb.conf

Reboot is required.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .