Unable to connect to SMB share

evilkiksass · 01-13-2011, 12:52 PM

In finder if I try to connect to a specific SMB share I get an error message which says "There was an error connecting to hostname.tld. Check the server name or ip address and try again." I have verified that the hostname is correct.
I have verified that I can connect to a different smb share on the same network via the same gui. I have verified that I can connect to the desired smb share via command line. And I can ping and ssh to the host as well. This smb share has been accessed from this system, on this network many times.

So what else could it be?

evilkiksass · 01-13-2011, 01:37 PM

Sorry for the bump, I was not able to subscribe to the thread through the link above, and forgot to do it when I made my original post.

trevor · 01-13-2011, 05:45 PM

Quote:

Originally Posted by evilkiksass


	which says "There was an error connecting to hostname.tld.

Just to be clear, does it actually say "hostname.tld", or does it say a hostname, a dot, and the top level domain of that hostname, for example "macworld.com"?

Is that hostname and TLD the actual name of the SMB share? It's not typical to name SMB shares that way.

What happens if you try to connect to the IP address of that SMB share instead of the hostname?

Trevor

agentx · 01-14-2011, 06:12 AM

In terminal enter these commands to see if the hostname resolves to an IP address. Could be DNS is not resolving the hostname. Also try and connect using IP adddress. What SMB server are you connecting to a NAS, Linux server, Mac Server running SMB, Windows machine ?

dig hostname.tld
nslookup hostname.tld

Maybe post back output.

evilkiksass · 01-14-2011, 12:08 PM

Trevor: It gives the fqdn of the smb server. not hostname.tld.
The hostname is correct (as I said, I have accessed this server via the gui many times previously with no problems). The smb server has multiple shares, generally I provide just the hostname and then OSX will prompt me which share I want to connect to. I have tried adding the sharename to the path so that it is smb://hostname.tld/share but the problem remains. I have also tried to use the IP of the server and the result was the same error message, except the hostname.tld was replaced with the ip address.

agentx: This is a linux server. I am able to connect to the machine and mount the share via command line as I said in the first post. Thus I am fairly sure that it is not a DNS issue. Also connecting via IP also fails. Both dig and nslookup returned the correct IP for the server.

Also for what it is worth. I use TotalFinder (I have uninstalled it and tried without it and still run into the same problem).
I also use LittleSnitch but there are no restrict rules which would apply here.

trevor · 01-14-2011, 01:47 PM

Thanks for the additional information. As a test (most definitely not as a solution) if you turn off both Little Snitch and your firewall, can you connect to the SMB share with the GUI?

If that succeeds, please let us know all of your firewall settings. If you are using Apple's built-in firewall, especially tell us if you have "Enable stealth mode: Don't respond to or acknowledge attempts to access this computer from the network by test applications using ICMP, such as Ping." checked or unchecked.

Trevor

evilkiksass · 01-14-2011, 04:22 PM

My standard firewall is disabled. I also tried disabling littlesnitch and making the connection. It still failed. I don't think it is anything at the network level since I am able to set up the connection successfully in the terminal.

evilkiksass · 01-18-2011, 12:52 PM

I am not sure if this is pertinent, but I can also mount it with no problem from within Windows 7 running in Fusion. This makes me think that the problem is specific to finder trying to access this one specific server. I am pretty new to macs, but does rebooting make sense here? I have been keeping my MBP just running and sleeping / hibernating since I bought it.

agentx · 01-18-2011, 12:56 PM

Open keychain access and delete all references to connection to share from keychains. Start windows sharing on your machine. I know this sounds odd but worth a shot.

And Yes a reboot is always worth ago too ;-)

evilkiksass · 01-18-2011, 01:25 PM

There is nothing in the Keychain which relates to any kind of SMB access. This server requires no authentication. I looked in the sharing portion of system configuration and see "File Sharing" but not windows sharing. Is this what I should start? And I will try and reboot my laptop today after work. Thank you for all your help with this.

agentx · 01-18-2011, 02:09 PM

Ok it would be a "network password" if you did have authentication.

"Have you tried to turn it off and on again".....blatant tech support speciality ;-)

Would not bother with turning windows file sharing on which for reference is done in
system prefs > sharing > file sharing > options.
Also in some environments it is good to set workgroup or domain info for SMB on the mac side. which is done in
system prefs > Network > network_interface in use > advanced WINS or search domains.

evilkiksass · 01-19-2011, 11:48 AM

Agentx I went ahead and rebooted my mbp before trying anything in your last post. This seems to have temporarily resolved the problem. Or at least hidden the symptom in this case. Hopefully the issue does not reappear. Thank you very much for your help with this.

01-13-2011, 12:52 PM	#1
evilkiksass Prospect Join Date: Jan 2011 Posts: 13	Unable to connect to SMB share In finder if I try to connect to a specific SMB share I get an error message which says "There was an error connecting to hostname.tld. Check the server name or ip address and try again." I have verified that the hostname is correct. I have verified that I can connect to a different smb share on the same network via the same gui. I have verified that I can connect to the desired smb share via command line. And I can ping and ssh to the host as well. This smb share has been accessed from this system, on this network many times. So what else could it be?

01-14-2011, 12:08 PM	#5
evilkiksass Prospect Join Date: Jan 2011 Posts: 13	Trevor: It gives the fqdn of the smb server. not hostname.tld. The hostname is correct (as I said, I have accessed this server via the gui many times previously with no problems). The smb server has multiple shares, generally I provide just the hostname and then OSX will prompt me which share I want to connect to. I have tried adding the sharename to the path so that it is smb://hostname.tld/share but the problem remains. I have also tried to use the IP of the server and the result was the same error message, except the hostname.tld was replaced with the ip address. agentx: This is a linux server. I am able to connect to the machine and mount the share via command line as I said in the first post. Thus I am fairly sure that it is not a DNS issue. Also connecting via IP also fails. Both dig and nslookup returned the correct IP for the server. Also for what it is worth. I use TotalFinder (I have uninstalled it and tried without it and still run into the same problem). I also use LittleSnitch but there are no restrict rules which would apply here. Last edited by evilkiksass; 01-14-2011 at 12:42 PM.

01-14-2011, 01:47 PM	#6
trevor Moderator Join Date: Jun 2003 Location: Boulder, CO USA Posts: 19,550	Thanks for the additional information. As a test (most definitely not as a solution) if you turn off both Little Snitch and your firewall, can you connect to the SMB share with the GUI? If that succeeds, please let us know all of your firewall settings. If you are using Apple's built-in firewall, especially tell us if you have "Enable stealth mode: Don't respond to or acknowledge attempts to access this computer from the network by test applications using ICMP, such as Ping." checked or unchecked. Trevor __________________ How to ask questions the smart way

01-18-2011, 12:56 PM	#9
agentx Hall of Famer Join Date: Feb 2003 Location: Brighton, UK Posts: 3,809	Open keychain access and delete all references to connection to share from keychains. Start windows sharing on your machine. I know this sounds odd but worth a shot. And Yes a reboot is always worth ago too ;-) Last edited by agentx; 01-18-2011 at 01:03 PM.

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

01-13-2011, 01:37 PM	#2
evilkiksass Prospect Join Date: Jan 2011 Posts: 13	Sorry for the bump, I was not able to subscribe to the thread through the link above, and forgot to do it when I made my original post.

01-14-2011, 06:12 AM	#4
agentx Hall of Famer Join Date: Feb 2003 Location: Brighton, UK Posts: 3,809	In terminal enter these commands to see if the hostname resolves to an IP address. Could be DNS is not resolving the hostname. Also try and connect using IP adddress. What SMB server are you connecting to a NAS, Linux server, Mac Server running SMB, Windows machine ? dig hostname.tld nslookup hostname.tld Maybe post back output.

01-14-2011, 04:22 PM	#7
evilkiksass Prospect Join Date: Jan 2011 Posts: 13	My standard firewall is disabled. I also tried disabling littlesnitch and making the connection. It still failed. I don't think it is anything at the network level since I am able to set up the connection successfully in the terminal.

01-18-2011, 12:52 PM	#8
evilkiksass Prospect Join Date: Jan 2011 Posts: 13	I am not sure if this is pertinent, but I can also mount it with no problem from within Windows 7 running in Fusion. This makes me think that the problem is specific to finder trying to access this one specific server. I am pretty new to macs, but does rebooting make sense here? I have been keeping my MBP just running and sleeping / hibernating since I bought it.

01-18-2011, 01:25 PM	#10
evilkiksass Prospect Join Date: Jan 2011 Posts: 13	There is nothing in the Keychain which relates to any kind of SMB access. This server requires no authentication. I looked in the sharing portion of system configuration and see "File Sharing" but not windows sharing. Is this what I should start? And I will try and reboot my laptop today after work. Thank you for all your help with this.

01-18-2011, 02:09 PM	#11
agentx Hall of Famer Join Date: Feb 2003 Location: Brighton, UK Posts: 3,809	Ok it would be a "network password" if you did have authentication. "Have you tried to turn it off and on again".....blatant tech support speciality ;-) Would not bother with turning windows file sharing on which for reference is done in system prefs > sharing > file sharing > options. Also in some environments it is good to set workgroup or domain info for SMB on the mac side. which is done in system prefs > Network > network_interface in use > advanced WINS or search domains.

01-19-2011, 11:48 AM	#12
evilkiksass Prospect Join Date: Jan 2011 Posts: 13	Agentx I went ahead and rebooted my mbp before trying anything in your last post. This seems to have temporarily resolved the problem. Or at least hidden the symptom in this case. Hopefully the issue does not reappear. Thank you very much for your help with this.