Setting up Samba, Unable to set hostname and domain on one machine.

Hello all!

I’ve recently set up a Samba server to run a small home file server, and everything with that seems to be working properly so far, and I can connect to it with all of my windows hosts, and my desktop running Opensuse 12.3. However, on my laptop that is also running 12.3, I’m not able to see the Samba server when I try to browse to it.

I think this problem may come from the fact that my hostname and domain name don’t appear to be set. When I open a terminal, I normally see the host name and domain name at the top of the window. However on my laptop this isn’t the case, it just says “myusername@:~” even thought he prompt is correct in the terminal which shows “myusername@myhostname:”

I’ve determined that my laptop is using networkmanager, and I’ve gone into the Network Settings in Yast and changed the host and domain names, as well as set the domain in Windows Domain Membership.

I can get a list of the server shares using smbclient -N -L “IP address to server” but if I try to run the same command using the servers name, it doesn’t seem to work. Using the server name on my desktop with Opensuse 12.3 does work, though.


smbclient -N -L servername 

gives me


Connection to servername failed (Error NT_STATUS_BAD_NETWORK_NAME)

does anyone have suggestions on how I can fix this? This is only a problem on one machine.

Thanks a lot!

I ask that you look at my Samba bash script tool and good blog info: S.A.C.T. - Samba Automated Configuration Tool - Version 1.06 - Blogs - openSUSE Forums

Thank You,

Thanks for taking the time to reply! I will definitely check this link out, but I’m not sure it will help with this specific problem. Samba is up and running fine on the server machine. Its one of my hosts that are having an issue connecting. On the same host, I can connect in Windows and Ubuntu, but when in Opensuse I’m not able to see the Samba server.

My bash script can check your smb.conf file and create a working one from scratch. Please read the blog and double check your config file.

Thank You,

On 2013-10-19 23:46, oapeter wrote:
>
> Thanks for taking the time to reply! I will definitely check this link
> out, but I’m not sure it will help with this specific problem. Samba is
> up and running fine on the server machine. Its one of my hosts that are
> having an issue connecting. On the same host, I can connect in Windows
> and Ubuntu, but when in Opensuse I’m not able to see the Samba server.

Is the domain named “.local”? It will not work.
In that case you have to change the domain or disable avahi.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

On 10/19/2013 4:46 PM, oapeter wrote:
>
> Thanks for taking the time to reply! I will definitely check this link
> out, but I’m not sure it will help with this specific problem. Samba is
> up and running fine on the server machine. Its one of my hosts that are
> having an issue connecting. On the same host, I can connect in Windows
> and Ubuntu, but when in Opensuse I’m not able to see the Samba server.
>
>
oapeter;

Check the following items on the Laptop:

  1. The workgroup parameter in /etc/samba/smb.conf is set to the name of your workgroup.
  2. Set the “name resolve order” parameter in /etc/samba/smb.conf. Put bcast in first position:

name resolve order = bcast lmhosts host wins

  1. Make sure that the Netbios Server and Samba Client are both allowed services on the Firewall.
  2. The Netbios Server (nmbd) is set to start at boot.

The nmbd handles name resolution for Windows Networking and, unless you have set up some other method of name resolution
(e.g. wins), you will want the Samba Client to try to resolve names by Broadcast (bcast) before it tries the other methods.

P.V.
“We’re all in this together, I’m pulling for you” Red Green

This fixed it! It was the first of your suggestions I tried. After allowing these services through the firewall, I was able to connect to the server!

I went ahead and added that line to the .conf file anyway. I’m kind of ashamed of myself for not thinking to play around with the firewall.

Thanks a lot!

On 10/19/2013 10:36 PM, oapeter wrote:
>
> venzkep;2592357 Wrote:
>>
>> 3. Make sure that the Netbios Server and Samba Client are both allowed
>> services on the Firewall.
>>
>
> This fixed it! It was the first of your suggestions I tried. After
> allowing these services through the firewall, I was able to connect to
> the server!
>
> I went ahead and added that line to the .conf file anyway. I’m kind of
> ashamed of myself for not thinking to play around with the firewall.
>
> Thanks a lot!
>
>

It’s good to know you have it all sorted out. Glad to help.

“We’re all in this together, I’m pulling for you” Red Green