Samba 2.0.6 (as distributed w/ FreeBSD 3.4 Walnut Creek CDs in ports collection) I'm trying to setup a samba server on my network. My network is not quite as simple as examples in documentation, because it has an NT server running as a PDC. I'm following the troubleshooting steps in book "teach yourself samba in 24 hrs" chapter 11 trouble shooting. I get to "step 7: Connecting to a share locally" where I enter the following command "smbclient '\\SAMBA01\tmp' -U <my_user_name>" (where <my_user_name> is replaced with my actual user name>. I get the following error return: (the ###s in ip addresses are actually the correct ip addresses) added interface ip=###.###.###.132 bcast=###.###.###.### nmask=###.###.###.### Got a positive name query response from ###.###.###.132 (###.###.###.132) session request to SAMBA01 failed (Not listening for calling name) Got a positive name query response from ###.###.###.132 (###.###.###.132) session request to *SMBSERVER failed (Not listening for calling name) I already searched the archive, and yes there is a "hosts allow =" line with "127." in it for the loop back. I even tried putting the machine's whole ip in, but got the same error. Is this windows domain / PDC problem, or something internal to the samba server? I get also get "Not listening" errors in the log if I try to browse it from Win98/WinNT workstations, which are also listed on the "hosts allow" line. Wins is disabled on all my machines. On a different note (this is probably a FreeBSD Ports question) I installed the Samba Port, and the directories are a bit different from the Samba Documentation, I can't find smbsh, and at least one of the commands in the default smb.conf file (domain controller =) cause unrecognized parameter errors if un-commented. Are the example/default smb.conf files distributed as part Samba, or just something thrown in by the person who configured the FreeBSD Samba Port? Does smbsh even work with FreeBSD? How can I get shares working in the other direction for my FreeBSD machine? Thanks, Cla.
Here's some more information on the not listening problem. I cut the smb.conf down to almost nothing for testing, using a test workgroup name instead of my existing NT domain: [global] netbios name = SAMBA01 workgroup = SAMBATEST security = user [tmp] path = /tmp writeable = no Then I tried to connect locally with "smbclient '\\SAMBA01\tmp' -U <my_user_name>" (where <my_user_name> is replaced with my actual user name>. I can connect locally.>From an external WinNT machine I tried to connect with a "net use j:\\samba01\tmp". It prompts for a password then I get an error 1240, user not authorized to login from this station. Without a "hosts allow" or "hosts deny", all external address should be allowed to connect right?? Next I tried adding the host of interest explicitly in hosts allow. Now I still can't connect from the external host, but I also can't connect from the local machine with smbclient either. that produces the following error output:I get the (the ###s in ip addresses are actually the correct ip addresses) added interface ip=###.###.###.132 bcast=###.###.###.### nmask=###.###.###.### Got a positive name query response from ###.###.###.132 (###.###.###.132) session request to SAMBA01 failed (Not listening for calling name) Got a positive name query response from ###.###.###.132 (###.###.###.132) session request to *SMBSERVER failed (Not listening for calling name) Next I tried adding "hosts allow = 127." as shown in some examples, but the local host still could not connect to itself. Finally I added the full ip for the local host, and then it could connect to itself. At this point I could also run swat from the allowed remote machines, but not connect them with a net use command, but I could connect from the local machine with the smbclient. Assuming that the swat help is correct, this seems to indicate a generic problem that might have some bearing on getting the same error while trying to integrate Samba into my NT Domain. It may be something wrong with my basic machine configuration, not involving Samba at all? Any suggestions appreciated. Thanks, Cla.
On Wed, 2 Feb 2000 17:30:21 +1100, hai scritto: keep using this simple smb.conf, without any interfaces, hosts allow... but with the guest account explicitly set.>[global] > netbios name = SAMBA01 > workgroup = SAMBATEST > security = userguest account = ftp> >[tmp]guest ok = yes> path = /tmp > writeable = noWhat do the samba logs say when samba starts and while you do "smbclient -L SAMBA01"? -- giulioo@pobox.com
Sorry for the delay in replying. I got swat running, and looked at the config file that way. This seemed to correct some of the not listening problems. Next I manually edited the smb.conf, to what you suggested, -HUP'ed inetd, and the not listening problem was "solved". Next, and this is where it gets WIERD... I put back my old simple test smb.conf that was giving me the "not listening" problem. However, it had no not listening problem anymore. I'm pretty sure I didn't change anything else, the problem just went away?? Now I can't duplicate it?? Next step, I want to integrated samba into the existing NT Domain... Even though samba's workgroup = SAMBATEST, it shows up in network neighborhood in my NT Domain "DOMAIN" on both the NT workstations and Win98 workstations. Is this because I added SAMBA01 using Server Manager on the PDC, even though workgroup / domain is different? Currently I've added the passwords directly to samba using smbpasswd. Theoretically I should be able to use the NT PDC to authenticate the passwords, and only maintain them one place right? Can I erase the passwords on the samba box somehow, verify they're gone by failing a login, then point samba to the PDC for passwords and verify it works by logging in using the PCD to verify the user? Sorry, I realize some of these questions probably relate more to MS PDC/Backup PDC, but the samba box will be my 1st backup PDC. Thanks, Cla.