similar to: netbios name resolution problem

Hi, Problem: When our network has any glitches causing a network time-out for more than a few minutes, our samba servers lose their connectivity with our WINS server even after the network is restored. This causes the WINS server to tombstone the name registration for the samba server(s), thereby causing clients to not connect through the browser. SMB connections are not affected so the

Hi everyone. I just got a copy of Win2k in and have been messing with it. Have a question, and have searched the archives for the answer, but didn't find it. Can Win2k domain logon to a pre-3.0.0 samba server? Or di I need to get TNG running? I can get NT4.0 boxes to authenticate and login fine (Samba pre-3.0.0), but Win2k keeps complaining: "The following error occurred validating

I am having trouble with one of my samba PDC's. It does not recognize itself as the domain master browser even though it is set to be so. I can not add machines to this domain and I suspect this is why. Has anybody seen this or know what causes it? Notice this: DOMAIN_ALBANY(3) current master browser = ALBANY_PDC DOMAIN_NYC(2) current master browser = NYC_PDC

Aug 6 11:21:44 linux nmbd[2193]: [2014/08/06 11:21:44.614859, 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) Aug 6 11:21:44 linux nmbd[2193]: process_lanman_packet: Discarding datagram from IP 192.168.1.6. Source name LINUX<00> is one of our names ! Aug 6 11:22:50 linux nmbd[2193]: [2014/08/06 11:22:50.279516, 0]

Hi I have a bunch of FreeNAS servers and a TrueNAS HA server all spamming the logs with these messages every minute about their own source name (examples below). These boxes are on two physically separate networks, and I find it unlikely both networks should have some sort of undetected loop. Any ideas on how to debug this? Samba version is 4.1.18. FreeNAS box on network A " Jan 5

Dear Sir, I want to ask that since I have installed Linux RedHat 7.1 with Samba Server inside it. I also configured it follow some books , however, my problem now is that . I can brower the linux computer through other computer in the same domain. However, when I try to access it, then it will said network problem and can't access it. I have tried ping to both computer name and ip address

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

I had a problem similar to my current one a week or so ago, and I was encouraged to upgrade from Samba 2.2.9 to 3.0.7, which I did. Now that I've completed that nightmare, the problem I initially set out to fix is still there, just different. Namely: I am trying to set up Samba 3.0.7 on a SuSE 9.1 box as an LDAP PDC whose only job will be authentication. Our LDAP server is on a separate

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

Hi. I've a Samba 3.4.7 running on Ubuntu 10.04 configured as PDC. It has always worked but lately these months strange things started to happen: clients cannot join the domain anymore. I had to reinstall a computer but when I tried to add it back to the domain I get this error message in Windows XP: DNS_INFO_NO_RECORDS. It seems windows cannot get server name via dns? The samba server runs

After running several days in the same configuration, my 3.0.6 nmbd crashed with the above error (see log below). Maybe there is a connection to this message some seconds before: register_name_response: server at IP 192.168.0.4 rejected our name registration of AK<1d> IP 192.168.0.12 with error code 6. The ip .4 machine is a win2k server, which works (or should work) as an ordinary

I've been messing around with running samba 3.4.14 inside a freebsd jail over the last couple of days, and am running into an odd problem where wbinfo -u and wbinfo -g succeed, but getent passwd fails (insofar that it shows only local users, but none of the domain users). Here's my smb.conf: [global] interfaces =192.168.0.16/32 bind interfaces only =yes security

estewart@dudley.lib.usf.edu wrote: > > On an Ultra 1 running Solaris 2.6 and using gcc 2.8.1 > > ipc.c: In function `api_RNetServerEnum': > ipc.c:1194: warning: passing arg 4 of `qsort' from incompatible pointer > type > > Compiling nmbd_incomingrequests.c > nmbd_incomingrequests.c: In function `process_node_status_request': >

On Mon, Sep 5, 2016 at 1:58 AM, Volker Lendecke <vl at samba.org> wrote: > What platform are you on? Can you run that under valgrind? Gentoo, using gcc-5.4.0. initiate_name_query_packet: sending query for name GRIZZLY<1d> (bcast=Yes) to IP 172.27.12.255 add_response_record: adding response record id:23039 to subnet 172.27.12.66. num_records:6 ==10086== Invalid read of size 4

I admit theres a LOT about the windows networking I dont understand - and even though this may NOT be a SAMBA issue per se, I thought I'd post it here. Have a 400gb samba server thats been working well (am upgrading to current patches today, btw). I've got 3 Win2k workstations, on two subnets, that have drives mapped, and connect every morning on startup just fine. All the machines

Found nmbd down with this in the log; [2001/02/27 19:21:36, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.113.255(138) ERRNO=Network is unreachable [2001/02/27 19:21:36, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.22.255(138) ERRNO=Network is unreachable [2001/02/27 19:22:18, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.3.1(137) ERRNO=Network

I create multiple server instances for the samba with systemd, everything ok, but after reboot server, the service nmb does not work randomly. selinux disable samba version 4.2.10 config smb [global] workgroup = WORKGROUP3 netbios name = net3 security = user interfaces = enp7s0f3 bind interfaces only =

This looks like a bug to me, except . . . no one else seems to have encountered it, and it's in a pretty basic area, so there must be something wrong at our site. When the Unix server becomes a local master browser, Samba is unable to sync its browse list w/that of the DMB. None of our NT machines are having any trouble, and our tech. support guy says the DMB is in good health. Rebooting

The only thing related to 'addresses' in my /etc/samba/smb.conf file is a "hosts allow": hosts allow = 192.168.3.0/24 127.1 I'm going to ignore the 'local hosts case, as if I solve the other, the localhost case may get solved by inference. I thought the 'hosts allow' would allow any host on the local 192.168.3.0/24 subnet. The hosts have no problems

Hi All, On my first internal NIC, Samba is working perfectly. On my new, second internal NIC, I am getting the following in my messages log: libsmb/nmblib.c:send_udp(793) Packet send failed to 192.168.254.255(138) ERRNO=Operation not permitted nmbd/nmbd_packets.c:send_netbios_packet(163) send_netbios_packet: send_packet() to IP 192.168.254.255 port 137 failed I though .255 was a reserved