similar to: Looking up Netbios name of host

Need Help with this one ASAP! When I issue smbstatus I get the following error: doing parameter max log size = 50 Processing section "[mytest]" doing parameter browseable = yes doing parameter read only = no doing parameter path = / Processing section "[homes]" doing parameter browseable = yes doing parameter guest ok = no doing parameter read only = no doing parameter create

Hi All, Here's an interesting one... I need to be able to connect smbclient on a linux machine to a dos based machine, which is running MSCLIENT and the WG1049 patch. I can browse to the machine and see all the files from Network Neighbourhood in Windows, but if I try and go in with: smbclient \\GAUGE1\C, or even just smbclient -L GAUGE1 all I get is: Added interface ip=10.0.1.1

Hi. I got this email-address from BUGS.txt file of the samba distribution. I read it carefully. I got configured and working samba, I work with samba above one year. I still have a problem, and, according to the samba log output, I think it's probably a bug. When I try to use the shares with audit support, I have my Far disconnected and telling me that something is wrong. I have that

I'm running Samba 1.9.18p8. If I use nmblookup to query the name of an NT server, as in nmblookup -A <ip address> then a packet trace shows an RPC reply coming back and nmblookup displays a list of names belonging to the NT server. If I try the same query on a Windows 95 machine, nmblookup only says Looking up status of <ip address> No status response (this is not unusual)

I have NEVER been able to get nmbd to work in anything even remotely approximating a usable fashion. All I want it to do is DNS lookups. I can't even get it to do that reliably. It looks in some cases like it isn't even sending a response back to the querying clients. When I do a request that fails, I get this: --- nmb packet from 192.55.114.4(3175) header: id=8172 opcode=Query(0)

HI ! I have a problem with nmbd, i can't logon on a WinXP machine (wfassi-PC ,everything was alright until at a moment user coudnt connect anymore) , here is log.nmbd : [2013/07/15 16:39:26, 5] libsmb/nmblib.c:797(read_packet) Received a packet of len 50 from (192.168.0.89) port 137 [2013/07/15 16:39:26, 4] libsmb/nmblib.c:106(debug_nmb_packet) nmb packet from 192.168.0.89(137)

.11 server is running 2.0.5. The .54 server is a mac server which we've also trying to get to see my machine (elbie) running 2.0.7 and the other machine running 2.0.10. nmblookup -M SAMBA is reporting that .11 is acting as the master browser. If this is a known problem with Samba 2.0, I can upgrade, but I'd rather not upgrade and discover I'm still having the same problem. :(

Hi Samba users, I'm using a typical Samba 3.0.14a PDC/Ldap setup. The pdc is also the WINS server. The wins server is working perfectly with one exception. The server cannot query itself. I searched through log.nmbd and this is what i found : > [2005/05/26 17:06:55, 4] > nmbd/nmbd_workgroupdb.c:find_workgroup_on_subnet(173) > find_name_on_subnet: on subnet 192.0.2.14 - name

Hello, I am having problems getting nmbd to work as a WINS server. nmblookup fails, as lookups from a PC. If I turn the debugging way up, in the log.nmb, I see: [1999/12/20 18:55:26, 4] libsmb/nmblib.c:debug_nmb_packet(109) nmb packet from 160.101.120.62(44713) header: id=28190 opcode=Query(0) response=No header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=No header:

Dear Ladies and Gentlemen, I am writing to ask your help with what may be an nmbd interworking problem. The situation is as described in the samba distribution documenet BROWSING.TXT. I have LANS connected by routers to a central site. FreeBSD 2.2.2R/Samba 1.9.17 nmbds at the remote LAN act as WINS proxy's to a a Samba WINS at the central site. All is well when the WINS proxy samba and the

I sent the following message to the list nearly two weeks ago and didn't receive a single response. In fact, I haven't received any replies to the last 3-4 questions I have asked (over the past 6 months). Maybe it is my wording??? I see the messages in the digest, so I know they are going to the list. :-) I have no right to complain and only cause to be very happy with the rest of

# testparm smb.conf Load smb config files from smb.conf Processing section "[documentation]" doing parameter comment = Engineering Documentation doing parameter path = /opt/eng-docs doing parameter writeable = Yes doing parameter guest ok = Yes pm_process() returned Yes lp_servicenumber: couldn't find homes Loaded services file OK. WARNING: You have some share names that are longer

Hi team, I'm dealing with AS/U as a member server on a Samba 3.0.20 PDC. Jonction seems ok, and from the member server I can see PDC's shares (with net view) and authenticate user (with net logon user passwd /domain:domainname). On the other side, I fell into timeout when running smbclient -L member from the PDC. Here is a log.nmbd loglevel 10 from PDC as there is no other log

On Thu, 25 Jan 2024 16:28:57 +0000 Vincent DROUIN <vdrouin at chapsvision.com> wrote: > Thanks for the advice about the security line, I won't use domain > type anymore then. > > I know name_status_find is using NetBios, what I don't know is why > this function is called when using 'security = ads', and as a result > of the fail my domain is added to the

Dear, I have very little network: NT Server 4.0 SP3 and Linux Samba server 1.9.18p6 I saw DIAGNOSIS.txt and steps 1-7 is done good. When I sad on NT "net view \\CLOP "I got the message "Semafore period time out". I see NT Server from Samba, but I do not see it from NT. "Search->Computer" from NT Explorer did not help too. NT is a WINS server. When I reboot NT

Hi all! I am using samba server at the company i work. Samba version is: 2:3.2.5-4lenny9 Some settings: os level = 255 domain logons = no wins support = yes domain master = yes local master = yes preferred master = yes i have dhcp configured witch sends wins server address (this samba servers address) to all clients. After I (re)start samba within a minute or so all computer of our network

Newbie question. If I type nmblookup __some other machine__ I get the correct response from Samba. If I type nmblookup __mymachine__ then I get an error yhat it is not found. So if nmbd is not setup right, how do I fix it? --Dan Dan Huston Phone (602) 965-2420 Measurement, Statistics and Methodological Studies Fax (602) 965-0300 Psychology in Education

Active Directory running on Windows Server 2019 Samba 4.15.8 (built from buildroot, using heimdal & libgssapi_krb5) Samba is running on a custom Unix distribution, all ports are open for the tests Testparm -s result : # Global parameters [global] bind interfaces only = Yes disable spoolss = Yes idmap cache time = 300 idmap negative cache time = 0

Hi, I've recently upgrade to Samba 1.9.17p1 from 1.9.16p11 (for Solaris 2.5), but have now found that smbclient fails to connect to user shares on win95 machines. I've tried the same login account from a win95 account and am able to mount shares from other win 95 machines. I've also tried running the old smbclient binary with the new smbd & nmbd daemons, and that lets me log

Hello, I'm having a problem logging in to the Samba domain from an XP machine. The machine is added to the domain but after reboot I can't login. I've done the signorseal registry hack but I'm still not able to login. The error I get when logging in is this: "Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or