search for: negotiator

Hi, I'm getting "Permission denied" error while connecting to a EMC Celerra (version 7) server from samba client on unix machine. Looking at the packet capture it is observed that samba client is authenticating with "anonymous" instead of the user name that has been provided. Here are flags received from EMC Celerra 7 server as part of "Session Setup AndX Response,

Hi, I'm getting "Permission denied" error while connecting to a EMC cifs share from samba client on unix machine. Looking at the packet capture it is observed that ?samba client is authenticating with "anonymous" instead of the user name that has been provided. Here are flags received from EMC server as part of ?"Session Setup AndX Response, NTLMSSP_CHALLENGE,

Hi Samba team, Could someone point me to a documentation which describes which NTLM flag combination in type 1 & 2 create which type 3 response. As far as I read MS has the following client/DC configuration combinations. Send LM & NTLM responses Clients use LM and NTLM authentication, and never use NTLMv2 session security; DCs accept LM, NTLM, and NTLMv2 authentication.

I'm having speed problems with the SCSI card we're using to do tape backup. It seems to be functioning in 16 bit mode and the current thinking is that perhaps it's using a legacy driver instead of the correct one. The Adaptec site has a 'driver' for RHEL5 which I've downloaded and tried to install but it seems to have a problem installing on a CentOS-5 system. [root at

qemu is about to add 'qemu-nbd --list', which exercises NBD_OPT_LIST and NBD_OPT_INFO to give the user as much detail as possible about an export without actually connecting to it. For that to display more than the export name when nbdkit is the server, we need to implement NBD_OPT_INFO. Thankfully, the NBD spec intentionally made the command very similar to NBD_OPT_GO, to the point that

This is the bare minimum needed to allow the user to take control over the rest of option negotiating. This patch adds several new API: nbd_set_opt_mode() - called during Created to enable the new mode nbd_get_opt_mode() - query whether opt mode is enabled nbd_opt_go() - used in Negotiating state to attempt to use export nbd_opt_abort() - used in Negotiating state to skip Connected state

Il 28/05/2013 17:09, Michael S. Tsirkin ha scritto: > On Tue, May 28, 2013 at 04:32:44PM +0200, Paolo Bonzini wrote: >> Il 28/05/2013 16:29, Michael S. Tsirkin ha scritto: >>> On Tue, May 28, 2013 at 04:06:02PM +0200, Paolo Bonzini wrote: >>>> Il 28/05/2013 15:32, Michael S. Tsirkin ha scritto: >>>>> At this point I am confused. I think there are two

Hai Amos, Thank you for your very clear responce.. few small questions.. Is there a way to setup the proxy for the following. 1) use negotiate kerberos for auth, ( which is working already for all domain joined machines ) 2) use a fall back that works, for now basic ldap works for non windows machines, and domain joined machines. 3) use any other fallback way for authentication users on windows

This is the culmination of the previous patches' preparation work for using extended headers when possible. The new states in the state machine are copied extensively from our handling of OPT_STRUCTURED_REPLY. The next patch will then expose a new API nbd_opt_extended_headers() for manual control. At the same time I posted this patch, I had patches for qemu-nbd to support extended headers

... sorry wrong list.. but you can read it and learn from it.. :-)) Greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at lists.samba.org] Namens >L.P.H. van Belle >Verzonden: dinsdag 18 augustus 2015 9:45 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] [squid-users] debian Jessie squid with >auth (kerberos/ntlm/basic) ERROR

Hello virtio folks, I noticed a mismatch between the way the specification defines device-specific virtqueue indexes and the way device and driver implementers have interpreted the specification. As a practical example, consider the traditional memory balloon device [1]. The first two queues (indexes 0 and 1) are available as part of the baseline device, but the rest of the queues are tied to

Add a new negotiation feature where the client and server agree to use larger packet headers on every packet sent during transmission phase. This has two purposes: first, it makes it possible to perform operations like trim, write zeroes, and block status on more than 2^32 bytes in a single command. For NBD_CMD_READ, replies are still implicitly capped by the maximum block payload limits

> "If" I understood your initial objective correctly (and I may not have), > the user's phones are negotiating the codec to be used for each rtp session. > > Asterisk parameters can be used to dictate rtp sessions between the sip > phone and asterisk, but that won't influence the next step in which the sip > phone negotiates a new rtp session directly with the

On 8/11/20 12:12 PM, Richard W.M. Jones wrote: > I think this needs extra documentation in docs/libnbd.pod because it's > definitely not clear just from the rather thin manual page for > set_opt_mode how it works. docs/libnbd.pod is a good place for a > broader description of how it works. Yes, good idea. State-wise, the existing flow was: Created - Progress only by command

Does os x (10.13) support negotiation of unix extensions/CIFS? When hard links didn’t work I dug in and while I found info on CAP_UNIX, and added ‘unix extensions = yes’ globally, the Negotiation makes no mentions: Negotiate Protocol Request (0x00) Capabilities: 0x00000077, DFS, LEASING, LARGE MTU, PERSISTENT HANDLES, DIRECTORY LEASING, ENCRYPTION Negotiate Protocol Response (0x00)

On 8/11/20 12:38 PM, Eric Blake wrote: > On 8/11/20 12:12 PM, Richard W.M. Jones wrote: >> I think this needs extra documentation in docs/libnbd.pod because it's >> definitely not clear just from the rather thin manual page for >> set_opt_mode how it works.  docs/libnbd.pod is a good place for a >> broader description of how it works. > > Yes, good idea. >

Hi, A number of students are unable to connect to our print server from their Windows 10 client laptop without entering a user/pass. More precisely: If you try to connect manually to \\IP it says "Username or password incorrect" and prompts to enter a username/password. Despite the server setting to map all users to guest (see further down). I did a packet dump and the client pc

Due to unknown reason, tinc failed to negotiate into UDP mode when first connecting, but will tinc keep trying/negotiating into UDP? or it has to be restart the tinc in order to start the negotiation process? Best Regards Bright Zhao ✉ -------------- next part -------------- An HTML attachment was scrubbed... URL:

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields