Mac - Connect to Server - "There was a problem connecting to the server"

Mac - Connect to Server - "There was a problem connecting to the server The file server is available on your computer. Access the volumes and files locally."

I am attempting to connect via SMB, though I have attempted via AFP only to get the same message.

The end user is connecting via VPN and can ping the IP of the server and obviously has an IP assigned to it that is on the same network.
The end user is running OS X 10.9.2

I was not able to recreate the issue on another Mac using the same user credentials, server address, etc...

Other forums suggested renaming the Mac's Computer Name in Sharing, but this has not helped.
I have listed the volumes, but only the local hard drive populates.
Who is Participating?
schapsConnect With a Mentor Commented:
I think strung is on the right track, but there's a bit more to it in this case.

First of all, it is apparent that the user's home network also uses the IP subnet 192.168.1.x/24. Furthermore, on the user's home network, his Mac has the same IP address as the server in question,
When your user pings what you think is the server, it's actually hitting the Mac's own network adapter (you can confirm this by having him ping in the Terminal and then type "arp -n" - the MAC address shown will be the Mac's own NIC MAC address).
When the user connects to the VPN, he gets another IP address in the 192.168.1.x subnet for the VPN connection, but an outgoing ping will hit its own NIC first before coming over the VPN connection and return the ping response.

Strung's suggestion to have the user change the IP subnet used at home to something different is technically correct, and it would help in this one case, but you will keep on running into this kind of problem with VPN users until you change the subnet on your network.

192.168.1.x and 192.168.0.x are the most common subnets used by home/consumer routers. For the office environment, the best solution is to change the office network to an IP subnet which is unlikely to be used by any of your VPN users, such as 172.27.1.x/24. Just make sure the subnet you use is private IP space: through through through

Ask more about that, if you're not sure about IP ranges, subnet masks, etc.
strungConnect With a Mentor Commented:
The problem you describe is usually caused by having the Mac's local LAN use the same subnet as the office server. If, for instance the office server is and the Mac is on a local LAN on the subnet 192.168.1.x, the Mac VPN client will not know whether to direct to the local or remote LAN.

The solution is to change the subnet of the local LAN to something different, say 192.168.5.x.
webitservicesAuthor Commented:
Indeed it was the remote users home network subnet that was causing the issues.  We changed to a different subnet for her home for now and all is working now.

Thanks for the help!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.