[SOLVED] Nt_status_no_such_domain

[norland]

I am using samba 4 in ubuntu linux 10.0.4 and when I run sudo smbclient -L 127.0.0.1 or sudo smbclient -L 192.168.0.13 I get the above error code NT_STATUS_NO_SUCH_DOMAIN. I can't view samba shares from my Windows machines. I even copied your above samba configuration and nothing seems to work. It seems like it would be easy to share a folder from directions I've seen on the Internet. Is there anything else I need to set up. I also get:

sudo samba restart
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Unknown parameter encountered: "guest only"
Ignoring unknown parameter "guest only"
Unknown parameter encountered: "writable"
Ignoring unknown parameter "writable"

when restarting Samba.

[rcgreen]

Post your /etc/samba/smb.conf file and we will give it a shot.

[norland]

I replaced my smb.conf with the backup original configuration and now I got it running again with IP access from my windows computers. But the catch is I some how got Samba 3.47 and Samba4 running on the same machine. I wonder what happens if both are running. Is Samba 4 better? I see the samba process and the smbd process but I don't see the nmbd process running. I don't know if that is the reason I can't view my linux machine from the windows network neighborhood or linux neighborhood for that matter. Now my task is to get WINS to work properly. I have attached my smb.conf file.

[rcgreen]

Configure your Windows clients to use this server as
their WINS server. Also on all machines, create an LMHOSTS
file. The syntax is the same as the /etc/hosts file.

192.168.1.103    stacy
192.168.1.106    ocean
192.168.1.101    kirby
192.168.1.104    blue
192.168.1.102    shelly
192.168.1.100    lisa

Those are netbios names, which may not necessarily
the same as the host names in /etc/hosts. (It does make
life simpler if you use the same name as the host name though)

The Windows lmhosts file is usually in C:\Windows\
system32\drivers\etc\, the same place as the hosts
file. Both hosts and lmhosts are there as sample files
with a .sam file extension. Edit the file and remove
the extension to activate it.

The lmhosts file for the samba server should be created and
put in the same directory as your smb.conf file,
usually /etc/samba.

Maybe I am superstitious, but I thought I had trouble with
mine until I renamed it in all caps, LMHOSTS.
Somebody tell me I am crazy.

[norland]

Well, I uninstalled Samba 4. It appears that Samba 3.47 was listening on the port to begin with, so the command samba restart didn't appear to have any effect. I couldn't figure out why changes weren't being updated on the Samba server via smb.conf unless I restarted. So, Rather than type: smbd restart and get no feedback information (these "scripts" had no effect) I typed: service smbd restart and service nmbd restart. These commands gave the feedback that Samba had restarted and what process ID it was. In the smb.conf file I removed the lines:
local master=Yes
domain master=Yes ' These are only necessary to be a wins server
Preferred Master = Yes
and changed the line:
wins support = no ' This makes it so you aren't a wins server
I restarted Samba and only intermittently (say after 15 minutes) would my computer show up on the network.

So what I noticed was that the firewall program Firestarter was blocking netbios calls even though I had opened the incoming ports for Samba. I would disable the firewall and notice that I could see my own computer in the Network Neighborhood browser. So I uninstalled Firestarter and checked with iptables that there were no rules in effect, and miraculously I was able to browse the network, and other computers were able to browse my file share and printers. Apparently the program 'UFW' might have a netbios setting that will allow netbios through the firewall.
Problem Solved! WINS resolution with out having to modify the hosts file.