There was a problem connecting to server "SERVER NAME" error keeps appearing after install Sonoma

Question

Level 1

5 points

There was a problem connecting to server "SERVER NAME" error keeps appearing after install Sonoma

There was a problem connecting to server "SERVER NAME" error keeps appearing even though the server is not on my current network. I just recently moved my iMac to a different location and a different network and now it is constantly trying to connect to the old server. This message appears every 5 seconds This is extremely frustrating because it makes the machine practically unusable since I am constantly closing these out. No matter how many times I try to quit it in activity monitor it just keeps reappearing, and I have even tried some terminal commands that I found online, then restarted the computer, but still had no success. ps This message appears before I even login so I don't think that this is a user issue. I really appreciate the help

iMac (2017 – 2020)

Posted on Jan 5, 2024 1:59 AM

Reply

Answer 1

Top-ranking reply

Strontium90

Level 5

5,499 points

Jan 5, 2024 5:01 AM in response to Petje131

I can think of two possible ways to define a server automount.

You added a login item

1: Go to Apple menu > System Settings > General > Login Items. At the top, there is a section called "Open at Login". By any chance, is the server share in the list? If so, select it and press the – button to remove it. I suspect this is not the case as these usually prompt once per login session and stay quiet after dismissal. Also, if there is an item there but you can't remove it...

You MDM admin enforced a login item

2: Go to Apple menu > System Settings > Privacy & Security > Profiles (all the way at the bottom). Look through your profiles. If you have a corporate managed device, your MDM managers may have delivered a managed login item profile. This profile tells your machine to mount the server share. The behavior you describe is inline with this type of enforced behavior. Ah, but now that you are not on the same network, you are unable to access the server. But the profile keeps trying. In this case, you will need to reach out to your MDM admins and ask that the mount profile be excluded from your device.

There is a 3rd possible way to do this but I feel it is unlikely because it is too much effort. However, you can look in /Library/LaunchAgents, /Library/LauchDaemons, and ~/Library/LaunchAgents to see if there is a custom plist that is enforcing a server mount. A launchd item could also repeatedly force the attempt. Again, this would require creating the launch script and likely also an app to call. Decent amount of work but figured I would mention anyway.

Hope this helps resolve.

Reid

Reply