Solved

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

Posted on 2014-10-28
3
2,465 Views
Last Modified: 2014-10-29
Mac - Connect to Server - "There was a problem connecting to the server 192.168.1.10. 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.
0
Comment
Question by:webitservices
3 Comments
 
LVL 53

Assisted Solution

by:strung
strung earned 250 total points
ID: 40410752
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 192.168.1.1 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 192.168.1.1 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.
0
 
LVL 10

Accepted Solution

by:
schaps earned 250 total points
ID: 40412075
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, 192.168.1.10.
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 192.168.1.10 in the Terminal and then type "arp -n 192.168.1.10" - 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:
10.0.0.0 through 10.255.255.255
172.16.0.0 through 172.31.255.255
192.168.0.0 through 192.168.255.255

Ask more about that, if you're not sure about IP ranges, subnet masks, etc.
0
 

Author Closing Comment

by:webitservices
ID: 40412125
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!
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Setting out for Cisco UCS 2 69
SSH setup on ASA 5505 17 52
Turning Verizon Fios Router into a Bridge? 28 66
Eset Smart Securties ARP poisoning attack 3 52
Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
Meet the world's only “Transparent Cloud™” from Superb Internet Corporation. Now, you can experience firsthand a cloud platform that consistently outperforms Amazon Web Services (AWS), IBM’s Softlayer, and Microsoft’s Azure when it comes to CPU and …
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question