similar to: Misunderstanding of 'nmblookup' run results ! Why so ?

> > > > ############################################### > Log from running the "smbtree" command, with the broadcast flag > ############################################### > mimir /var/log/samba # smbtree --user jonesmz -b -d10 > lp_servicenumber: couldn't find homes > added interface ceph-public ip=fda8:941:2491:1699:60fa:e622:8345:2162 > bcast=

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

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)

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

.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. :(

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 an XP Pro box on my LAN, and I'm trying to figure out why nmblookup '*' can't see it. I'm writing a script that finds all the shares on the LAN and mounts them, and it works great except for this one box. On another windows box, when I run "net view", the XP box is listed as I expect. On my linux box, when I run "nmblookup -A 192.168.0.111" it

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

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:

I am using samba 2.2.1a , in an NT-4 domain. security = DOMAIN on the first logon to the samba server, I can see a message: Attempting host lookup for name MYPDCNAME<0x20> the next message appears after 10 seconds (that is the delay). samba tries to resolve MYPDCNAME with the wins server, and succeeds. Higher debug level (debug level = 10) does not produce more debug messages. Any ideas

Hello All, I have a Linux box running RH9 and Samba 2.2.7 as domain controller. Last week, we bought a new (better!) box and migrated our Samba installation to the new box and apparently everything was working fine, until we noticed that shares created in the Windows machines are not accessible by anyone in the domain. I've read all the docs and everything seems ok, but I can't get

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

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)

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

Hello, I'm using a Samba client to access a Samba Server. The "smbclient tool" is ok, both at the client as at the server. I'm having trouble with the "wbinfo" command (winbind service) at the client, as you can see below. Can anybody help me? Thanks!!! =Problem============================== Samba Server: samba-3.0.10-1.fc2 Samba Client: Version 3.0.0-14.3E

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

Hello list, i want to auth. squid against a win2000 AD group to get internetaccess using winbind. First i had installed samba.2.2.5 I configured smb.conf: [global] workgroup = CAMPUS server string = Samba Server hosts allow = 149.250. 212.68. 192.168. 127. security = domain password server = ATHENA encrypt passwords = yes socket options = TCP_NODELAY SO_RCVBUF=8192

Hi- Ok, this is puzzling me. I have two machines on different networks running Samba 1.9.18p10. On one machine, which is running Redhat 5.1, I can do "nmblookup -A <IP ADDRESS>" and get the IP address of a host on the LAN. This network also has an NT server domain controller, but I doubt that matters in this case, since I'm querying the machine directly. The second machine

SMBv1 (the anonymous thing behind network neighborhood) because of the massive security problems it caused was decprecated. Microsoft came up with network neighborhood and they've shut it down due to their bad implementation. Samba, likewise, doesn't support SMBv1 by default. On 7/12/20 10:29 PM, Michael Jones via samba wrote: > I'm trying to diagnose why my windows 10 clients

If you have 1 member server, you could enabe nmbd in that server. Or install : llmnrd on linux and/or avahi-deamon if you dont have a member. And make sure you can use "proxy dns" as in, The primary DNS domain on linux should match (see in windows) CMD: ipconfig /all The : - primay dns suffix - DNS Suffix search order Then you are able to use \\hostname or \\hostname.FQ.DN.TLD