You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

network folder access from internal mac computers changes?

Hello!

My employer is experiencing issues on El Capitan, High Sierra, and Mojave where a user tried to access the network shares as normally have, But when they try use these steps: "Go", "Network", then they select the folder they usually access such as "Primary" Network Share folder. When they click on the Network folder they only get the Blue Folder icon. To solve this problem 99% of our users are now relying on Command+K to open their specific network folder containing files.


My question is...has Apple changed how we now can access Network folders and failed to let its customers know?


If someone knows or has had his issue I am curious what has changed?


Thanks,


Kenneth

Posted on Sep 10, 2019 3:21 PM

Reply
Question marked as Top-ranking reply

Posted on Sep 10, 2019 10:03 PM

I'm not familiar with Command + K.


Have the computers been rebooted? Is macOS up to date (fully patched) on them?


What type of network share are you trying to connect?


Are AD credentials used to connect to the share?


Can you connect with "Go --> Connect to Server" and manually enter the protocol and server DNS name/IP address like "smb://ourserver.ourdomain.org" or "smb://ourserver.ourdomain.org/name-of-share"? Can you connect with credentials known to connect reliably?


If security software is installed, then check its settings. You may also need to look at the network configuration of switches, vlans, firewalls, server, AD privileges, etc. It would be best to test a known working laptop at the locations where a user is experiencing issues connecting to see if the issue is related to their computer/credentials or their physical location/connection. If a user is using WiFi, try a wired connection.


If it is an SMB share, then perhaps the server is using an outdated or incompatible SMB version. Most operating systems are deprecating support for older versions of SMB due to security vulnerabilities.

Similar questions

2 replies
Question marked as Top-ranking reply

Sep 10, 2019 10:03 PM in response to FisherIT1

I'm not familiar with Command + K.


Have the computers been rebooted? Is macOS up to date (fully patched) on them?


What type of network share are you trying to connect?


Are AD credentials used to connect to the share?


Can you connect with "Go --> Connect to Server" and manually enter the protocol and server DNS name/IP address like "smb://ourserver.ourdomain.org" or "smb://ourserver.ourdomain.org/name-of-share"? Can you connect with credentials known to connect reliably?


If security software is installed, then check its settings. You may also need to look at the network configuration of switches, vlans, firewalls, server, AD privileges, etc. It would be best to test a known working laptop at the locations where a user is experiencing issues connecting to see if the issue is related to their computer/credentials or their physical location/connection. If a user is using WiFi, try a wired connection.


If it is an SMB share, then perhaps the server is using an outdated or incompatible SMB version. Most operating systems are deprecating support for older versions of SMB due to security vulnerabilities.

network folder access from internal mac computers changes?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.