similar to: W2k logged out workstations keep 'alive' at smbstatus (3.0.23a)

Hi, Trying to be simple and direct. My last email didn't get answers. Thank you and best regards. Problem: ----------- W2K workstations remains connected do samba server at port 139, even after logoff, and this causes: false wtmp information and no possibility do control (even no fail proof) simultaneous logins. Workaround ( not acceptable )

Hi, After switching to samba3 I've noticed that it doesn't allow connections with empty usernames with security = user anymore. Samba2 mapped empty user to nobody, is there a way to achieve such behavior? It is needed for compatibility - we still have lots of W2k workstations that allow passing empty usernames in login prompts (as opposed to XP). Adding null/NULL to

Hi, I have somewhat successfully got Samba working where as users can map the drives to their win2k/xp workstations and wrote to the folders they are given permissions to. They can write to the folder, delete folders, write files, delete files, view the file listing, however, they can't open files. For instance, if there is a word document, they can't just double click on the share and

>>>>> Kurt Hornik >>>>> on Mon, 29 Jun 2020 16:13:03 +0200 writes: >>>>> Jan Gorecki writes: >> So the unique.default is from the R tools package during >> checks. I don't see those issues on CRAN checks. > I cannot reproduce this locally (and have no clues about > docker). Perhaps you can try to debug this

>>>>> Jan Gorecki writes: > Thank you both, > You are absolutely correct that example should be minimal, so here it is. > l = list(a=new.env(), b=new.env()) > unique(l) > Just for completeness, env_list during check that raises error > env_list <- list(baseenv(), > as.environment("package:graphics"), >

Thank you both, You are absolutely correct that example should be minimal, so here it is. l = list(a=new.env(), b=new.env()) unique(l) Just for completeness, env_list during check that raises error env_list <- list(baseenv(), as.environment("package:graphics"), as.environment("package:stats"), as.environment("package:utils"),

Hi, I am migrating a Samba 3.0.28 ( Slackware 12.0 ) that is a single PDC, to a PDC with domain members and/or BDC. This single PDC is plugged in a central switch and I have a lot of computer's rooms, in different ethernet segments, all them using switches and routers to reach this PDC. ( Something like this: PDC -> central switch -> router -> switch -> workstations )

https://bugzilla.samba.org/show_bug.cgi?id=1889 ------- Additional Comments From wayned@samba.org 2005-02-12 15:05 ------- Note that in the new version, this too-long receiver-side scan can be avoided by using --delete-during (--del). However, I'm still considering adding a "keep alive" message. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email -------

We recently installed this update, and found that half our customers would lose registration after about a minute. Packet capture shows that the phone sends the keep-alive packet (a SIP options packet), gets back a SIP 481 no subscription, then immediately loses registration. Turning off keep-alive fixes the problem. This is with Cisco/Linksys SPA phones, both older 9xx series and the newer 303

Tested with xm-test on i386 UP. See comment for more details. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Can anyone explain what is happening. After call virConnectOpen virEventRegisterDefaultImpl() call virConnectSetKeepAlive returns VirtError(1): internal error: the caller doesn't support keepalive protocol; perhaps it's missing event loop implementation, but the next call this sequence of commands returns success. Why virConnectSetKeepAlive not work right the first time? -- Fl at sh

At Tue, 1 Apr 2014 17:29:25 +0400, Fl@sh wrote: > > Can anyone explain what is happening. > After call > virConnectOpen > virEventRegisterDefaultImpl() > call virConnectSetKeepAlive returns > VirtError(1): internal error: the caller doesn't > support keepalive protocol; perhaps it's missing > event loop implementation, > but the next call this sequence

https://bugzilla.mindrot.org/show_bug.cgi?id=1712 Summary: partial server keep-alive implementation for SSH1 Product: Portable OpenSSH Version: 5.3p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: unassigned-bugs at mindrot.org

https://bugzilla.mindrot.org/show_bug.cgi?id=1712 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED CC|

Hello list, Is there some parameter on sip.conf to always let the client reachable ? I'm trying to avoid .... this situation : Sep 3 09:49:29 NOTICE[135442432]: chan_sip.c:7653 sip_poke_noanswer: Peer '1264' is now UNREACHABLE! Sep 3 09:49:39 NOTICE[135442432]: chan_sip.c:6408 handle_response: Peer '1264' is now REACHABLE! Regards, -Jefferson Carvalho

In a setup I've made i have a problem in the two way origination of the call. Asterisk 1 <==> Public internet <==> NAT <==> Asterisk 2 note the two way pointing arrows. When you call from the *2 to the *1, the call passes, but if you try to call from the *1 to the *2, it will not connect, unless you call from *1 to *2, and inmediately after hang-up, you call in the other

Hi, On my linksys/sipura phones/ATA, there is a setting called "NAT Mapping Enable" and another called "NAT Keep Alive Enable" These settings must be on in my setup so that my phones/ATA remain connected to my * server. My setup is: Home LAN - Pfsense (NAT, Dynamic Public IP)- Internet - PFsense (1-to-1 NAT, Static public IP) - Asterisk server. I was wondering:

Hi all, Anyone know how to make asterisk properly reply to options keep-alive? Or just force a 200 OK somehow? I recently took over a server and they have ~80 pap2 devices that send nat keep-alive and * always replies with 481 No subscription. It's more of an annoyance, I know but I like to keep my pcap's clean. S. -------------- next part -------------- An HTML

I have a simple 3 hosts virtual network setup with tinc vpn. Three hosts are using ips as A-10.0.0.1, B-10.0.0.2, and C-10.0.0.3. All 3 hosts(A,B,C) are in three different networks. B and C uses "ConnectTo" in their tinc.conf to connect to A's external IP. After all the setups are done, such as key exchanges etc, and start the tinc daemon on all hosts, the connections among the 3

It appears as though the 489 Bad Event response to the NAT keep alive event responds to the local address, instead of responding to the NATted address. This causes Linksys phones to go amber (no registration) after a short amount of time after placing calls. Turning the Linksys NAT keep alive off is a workound, but non-ideal in may situations. Apparently the asterisk devs don't even think