MacOS – Tracing the source of “There was a problem connecting to the server” alerts

afpmacosmdstime-machine

After upgrading from MacOS 10.6 to 10.8, I keep getting alerts on my MBP saying "There was a problem connecting to the server xyz". The thing is, there is no longer a machine called "xyz" on my network (I've renamed it to something else in hopes of eliminating/diagnosing this problem).

After googling around a bit, I suspect that the culprit is an association of a file type with an application that is on the xyz machine (that I have previously run on my MBP after mounting xyz:/Applications). When these alerts pop out, I see (via top) that a time-machine-induced mdworker is active (seemingly confirming that it's trying to use the remote application to extract information from a local file).

Is there some way that I can confirm what process is actually generating the alerts? Is there a better way of diagnosing their source?

Update: I was never able to figure out what was actually generating the alert, but I was able to abate it by doing a complete re-install of 10.8 (via the recovery boot option). To my surprise — in addition to eliminating the alerts — this didn't even require any recovery of my apps/files from backup (not that you should try this without having everything backed up!)

Best Answer

I am getting this as well. The only way to remove it is to re-install OSX, and then it re-appears if I try to install software. Odd ...