Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

mrjayviper

macrumors regular
Original poster
Jul 17, 2012
245
27
Setup information:

MacPro (10.11.6):
ethernet1 = DHCP (192.168.1.11)
ethernet2 = manually assigned (192.168.2.2)

FreeBSD (10.3 running Samba 4.4):
ethernet1 = DHCP (192.168.1.2)
ethernet2 = manually assigned (192.168.2.1)

Since both machines have dual gigabit Ethernet port, I decided to use a crossover cable to the FreeBSD server so I have a dedicated access to it.

The Samba server is used for serving video around the house and I thought using a dedicated connection would make MacPro<->Samba transfer much faster plus it wouldn't affect the the other people using it. I often transfer large files across the 2 devices.

I decided to reinstall OS X El Capitan 10.11.6 last night on the MacPro and that's when problem started.

Observations:
1. no problems with ping/ssh before/after OS X reinstall using 192.168.1.x and 192.168.2.x networks

2. before reinstall, I have no problems connecting to the Samba share using Finder (smb://192.168.2.1/share-name-here or smb://192.168.1.2/share-name-here)

3. after reinstall, I can still connect using 192.168.1.2 but I get the message below when using 192.168.2.1

Code:
This file server is available on your computer. Access the volumes and files locally.

I want to use 192.168.2.1 for reasons given above.

No change has happened on the FreeBSD side. I'm watching my samba logs (via tail) and looking at OS X console but nothing is showing up.

Any ideas? thanks
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.