Creates

Q: OSX Yosemite Can't connect to Samba Server suddenly

Hi Guys,

 

I know there are alot of questions regarding this but none had the exact problem as i had. I have tried all other suggestion from some of the closest ones from mine but none seem to work. So lets start with what i have.

 

Im currently using Mac Pro 2008, with Raid 10 Connected OS X Yosemite 10.10.5

I also have These Servers : 3x 14.04 Ubuntu Server which are on Raid Setup as well.

I have 10 Windows Computers Running.

 

Now the problem is :

It all worked well last week. Now over the weekend it started getting weird.

 

I can connect to all windows network, I can Ping all 3 servers, I have internet. But I could not connect to the servers.

I keep Getting the error "Connection Failed" and "There was a problem connecting to the server "Servername"

 

I have tried this following work arounds :

*Update all I can update from store

*Connect using "Connect to server"

*Disable Wake on lan

*Flush all DNS/Cache via Terminal

*Add server ip & Hostname to mac's Host file via terminal

*Replace network cable

*connect using wifi

*Change IP

*Change Computer/Netbios Name

*Disabled Firewall

*Restarted Several Times

*ping server ip all success.

 

Nothing worked.

 

I still cant gain access to my server using my mac.

Using my windows computers however is working just fine when connecting to the servers.

 

 

Any suggestions regarding this matter?

Mac Pro 2008, OS X Yosemite (10.10.5)

Posted on Apr 20, 2016 6:54 AM

Close

Q: OSX Yosemite Can't connect to Samba Server suddenly

  • All replies
  • Helpful answers

  • by Flier_High,

    Flier_High Flier_High May 4, 2016 10:33 AM in response to Creates
    Level 1 (4 points)
    May 4, 2016 10:33 AM in response to Creates

    I was having the exact same issue. It turned out to be a bad configuration in the Ubuntu Samba settings.

     

    Running 'testparm' in the Ubuntu terminal showed there was an error in my /etc/samba/smb.conf file, once I fixed that it was working fine again. No idea why or how, but there was an extra '=' after a line that was causing the problem.