Displaying 4 results from an estimated 4 matches for "nbtd_mailslot_browse_handler".
2016 Aug 19
2
User accounts being blocked
...dreplsrv_notify_schedule(5) scheduled for: Fri Aug 19 15:13:35 2016 BRT
[2016/08/19 15:13:32.271240, 5] ../source4/libcli/dgram/dgramsocket.c:65(dgm_socket_recv)
Received dgram packet of length 201 from 172.16.16.137:138
[2016/08/19 15:13:32.271406, 4] ../source4/nbt_server/dgram/browse.c:70(nbtd_mailslot_browse_handler)
Browse HostAnnouncement (Op 1) on 'domain<1d>' '\MAILSLOT\BROWSE' from 172.16.16.137:138
[2016/08/19 15:13:32.271453, 5] ../source4/libcli/dgram/dgramsocket.c:65(dgm_socket_recv)
Received dgram packet of length 201 from 172.16.16.137:138
[2016/08/19 15:13:32.271484, 4]...
2016 Aug 19
0
User accounts being blocked
...le(5) scheduled for: Fri Aug 19 15:13:35 2016 BRT
> [2016/08/19 15:13:32.271240, 5] ../source4/libcli/dgram/
> dgramsocket.c:65(dgm_socket_recv)
> Received dgram packet of length 201 from 172.16.16.137:138
> [2016/08/19 15:13:32.271406, 4] ../source4/nbt_server/dgram/
> browse.c:70(nbtd_mailslot_browse_handler)
> Browse HostAnnouncement (Op 1) on 'domain<1d>' '\MAILSLOT\BROWSE' from
> 172.16.16.137:138
> [2016/08/19 15:13:32.271453, 5] ../source4/libcli/dgram/
> dgramsocket.c:65(dgm_socket_recv)
> Received dgram packet of length 201 from 172.16.16.137:138
> [2016/...
2019 Jul 04
0
warning after samba update to 4.10.5
...to 4.10.5 and testing I
have detected that we receive this message:
[2019/07/04 08:28:26.449232, 5]
../../source4/libcli/dgram/dgramsocket.c:65(dgm_socket_recv)
Received dgram packet of length 184 from 192.168.168.1:138
[2019/07/04 08:28:26.449375, 4]
../../source4/nbt_server/dgram/browse.c:70(nbtd_mailslot_browse_handler)
Browse AnnouncementRequest (Op 2) on 'DOMAIN<1d>' '\MAILSLOT\BROWSE'
from 192.168.168.2:138
[2019/07/04 08:28:26.449559, 5]
../../source4/libcli/dgram/dgramsocket.c:65(dgm_socket_recv)
Received dgram packet of length 201 from 192.168.168.3:138
Is this correct?
Thanks!
2016 Aug 19
5
User accounts being blocked
Dear,
I've been noticing that constantly, some user accounts has been repeatedly blocked.
We use DC Samba 4.4.5.
Here we have a blocking policy, if the wrong password is entered more than 5 times. But most users say they do not screwed up the password. They perform the log at the beginning of working hours. After a while, they block the session and when they try to log on again, the