similar to: exit codes of samba tools: not really a bug, but a proposal

I have a new SentOS 5 system and have been having problems with Samba. I had been able to access my test share but not my home share. Attempting to re-set thigns as describe by the "webmin configure samba" info resluted in being able to see everything but the home shares. I don't know if I could have copied or written to these other directories - didn't try. Continued

Hi, While going through DIAGNOSIS.txt on my samba 2.2.2 server, I came across the following test results: Test 5: [root@NetServer samba]# nmblookup -B resaddr8.research.bio2.edu '*' querying * on 209.64.53.8 name_query failed to find name * This appears to be a partial failure? Test 6: Initially, I got: [root@NetServer samba]# nmblookup -d 2 '*' added interface

Hi, After lots of struggle and rtfm I finally got most things running, except for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but plenty more to learn. Here's the setup in summary: system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master, wins server, domain master browser, no iptables; system bdc is the BDC on subnet 192.168.2.0,

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

Hello, I am hoping someone can help me.... I am trying to configure my samba...and the problem is the following: When I use nmblookup with -B option and Broadcast address it is impossible to find my samba server (named prova) that is: # nmblookup -B 10.254.14.127 prova querying prova on 10.254.14.127 name_query failed to find name prova If I do the same lookin up to another machine different

Hello together! I have an problem with the wins server, based on a Gentoo distribution with Samba 3.0.24. The problem is following: After an restart of samba everything works fine, but after an undefined time period its not possible to make an nmblookup for some other computers. The samba server is also configured as wins server. an cut from the smb.conf: ...... domain master = Yes

I have been unable to get my Samba shares on RedHat 7.3, Samba 2.2.3a to be visible from my Windows 2000 SP1 server. From the DIAGNOSIS.txt tests (results below) I think that nmbd is not working properly, but it stops and starts fine, and a ps -A shows 1 X smbd and 2X(?)nmbd processes running, I have tried the suggestions there without luck and am not sure where to go next. I'd appreciate

Hi everyone , Recently upgraded to 2.2.5 on RH73 and suddenly my Roaming profiles did stop working and on top of this my NMBD is giving me constant errors!!!! when i try nmblookup -U 127.0.0.1 _SAMBA_ name_query fail to find name _Samba_ then i have tried : nmblookup -B 192.168.123.1 MYSERVER and then : nmblookup -U 127.0.0.1 MYSERVER 192.168.123.1 MYSERVER<00> looks fine after this i

Well gang, I'm back and still haven't figured out why Samba isn't working with my Windoze PC's. I though I was close a couple times, but now I'm back to square 1. So now I'm going to spill as much information on you guys as I can in the hope that someone will notice what I'm doing wrong and help me get this thing running. Here are the computers on my home network:

Hi folks, I find that nmblookup seems to be receiving responses to name queries, but ignoring them. Here's what's happening: # nmblookup somehost querying somehost on x.y.255.255 name_query failed to find name somehost But watching the transaction with ethereal on the local host, I see that: 1. nmblookup on local udp port nnnn (some random number above 1024) sends an nbns

I used to be able to browse the windows shares on the network through Nautilus. I can see them as computers, but when I click on them, it fails. (I'm on Ubuntu 6 LTS, AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am

Hello. I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC. Samba can't find its hostname via nmblookup: $ nmblookup -B 192.168.1.255 frontier querying frontier on 192.168.1.255 name_query failed to find name frontier If I query Samba via unicast, it answers OK: $ nmblookup -U frontier frontier querying frontier on 192.168.1.31 192.168.1.31 frontier<00> Also,

Hi all ! I have a PDC and a BDC in 2 differents subnets. I would like to sync their browse list but it doesn't seem to work. Actually here are a part my smb.conf files : PDC ------------------------------ ... remote browse sync = 10.10.20.10 remote announce = 10.10.20.10 security = user encrypt passwords = true domain logons = Yes os level = 70 preferred master = yes domain master = yes

I'm debugging my Samba setup using the "Troubleshooting Techniques" from Sam's Teach Yourself Samba in 24 Hours. Everything works fine up until the nmbd section. I am able to do the following correctly: nmblookup -U 127.0.0.1 __SAMBA__ nmblookup -U 127.0.0.1 POGO (the server) nmblookup -B 192.168.1.255 WIN-CLIENT (the client) but when I do nmblookup -B 192.168.1.255

hi, when i give samba a workgroup name with more than 15 characters [the limit for netbios names], nmbd is unable to participate in browse master elections. it appears that parts of internal samba code honor 16 characters and parts only honor 15. details: i used a workgroup name of nodomain.nowhere, 16 characters, on samba 2.2.1a. the samba box was the only member of this workgroup on the

Troubleshooting steps fail. Trying to replace a standalone Netware server with a Samba4 server with AD. To isolate this test setup, changed server's static IP address and separated the wiring. Then went through the Troubleshooting portion of The Samba Checklist. Some tests pass. Some tests fail. I'm weak on Samba, DNS and AD. I appreciate your instructions on how to overcome the

$ nmblookup ohwow querying ohwow on 129.22.171.31 name_query failed to find name ohwow $ nmblookup -s /etc/samba/smb.conf ohwow querying ohwow on 129.22.171.31 name_query failed to find name ohwow $ cat /etc/samba/smb.conf [global] workgroup = scholars netbios name = fedora security = user wins server = 129.22.4.11 wins support = no name resolve order = wins lmhosts dns my problem is that

I've got Samba 2.2.2 installed and running fine on one of our servers (RS/6000 AIX 4.3.3 and using NT authentication), however, when I do Test #4 (from docs/textdocs/DIAGNOSIS.txt) it looks like this: npssrv{root}#nmblookup -B npssrv _SAMBA_ querying _SAMBA_ on 173.148.200.113 name_query failed to find name _SAMBA_ The test said I should get back the IP address of our samba server. I got

Hi there, i have Samba 2.2.7a running on FreeBSD-STABLE 4.7. I set up a few things and smbd and nmbd start up at boot, i can browse the net. However, nmblookup can only find IPs by SMB-names, but not SMB-names by IPs. Here is an example output of the failed lookup: %nmblookup -d 3 210.104.1.133 Initialising global parameters params.c:pm_process() - Processing configuration file

I'm trying to use nmblookup to find the IP address of a Windows machine called "MARKETKA" (only with an accent over the 'E'). If I do a reverse lookup on the IP address, with debugging enabled, I can see that the hex code for the accented 'E' character is 0x90: $ nmblookup -d 4 -A 192.168.1.15 | grep MARK answers 0 char .MARK.TKA hex