search for: nego

...ver are domain member of my Samba PDC. On a win2k server, we have a DCOM application that have sometimes a problem. The problem is : the server don't answer, no shared directory and no DCOM service are available. But five minutes later, all services is available. In samba.log, we can see a SPNEGO connexion problem (SMB_err = 49152). All win2k server are patched to the last microsoft patch (SP4). Is a samba problem, a windows problem, a network problem. A answer is very apprecied. Thank you -- St?phane Purnelle <stephane.purnelle@tiscali.be> Site Web : http://www.linuxplusvalue.be

...nd group queries fail. This is OBVIOUSLY using LDAP and TLS. If this was via NTLM/Kerberos, the above setting wouldn't make the slightest difference. But all that aside - the key question is: [Again, lets quit arguing if this is TLS/LDAP or Kerberos.] *** How do I get visability into the TLS negotiation so I can figure out what's wrong with my ca/certs/keys. -Greg

...]= 255 (0xFF) smb_bcc=16 [2004/02/23 10:45:00, 10] lib/util.c:dump_data(1830) [000] 34 C7 44 02 6A AB 67 47 93 AC B8 1A 63 CC 56 45 4.D.j.gG ....c.VE [2004/02/23 10:45:00, 4] lib/time.c:get_serverzone(122) Serverzone is -3600 [2004/02/23 10:45:00, 2] libsmb/cliconnect.c:cli_session_setup_spnego(665) Doing spnego session setup (blob length=16) [2004/02/23 10:45:00, 3] libsmb/cliconnect.c:cli_session_setup_spnego(669) server didn't supply a full spnego negprot [2004/02/23 10:45:00, 6] lib/util_sock.c:write_socket(407) write_socket(4,164) [2004/02/23 10:45:00, 6] lib/util_sock.c:wr...

...SSH servers using Vintela Putty. I am now trying to use the Kerberos credentials to access Samba shares. I can mount the shares using my Kerberos tickets from a Linux and I see the service ticket for cifs/FQDN but it doesn't work from Windows. When connecting to a share I can see that the negotiation phase offers Kerberos 5, MS Kerberos and NTLM. The Linux client choose Kerberos but Windows choose NTLM and prompt for a login/password. Is there a way to remove the NTLM from the nego phase on the Samba side or to force Windows to try Kerberos first on the client side ? Config: Debian uns...

...hosts allow = 192.168.0. 127. interfaces = rl1 bind interfaces only = Yes server string = Freebsd client code page = 852 dead time = 15 keep alive = 15 [Ogolne] path = /home/samba browseable = yes public = yes read only = no i makedir /home/samba drwxrwxrwx 2 nego userzy 512 Feb 11 17:11 samba and now i stared smbd -D nmbd -D it worked for one day and when next day i restarted server i couldn't connect to this from my network (with winXP and win98) but i can connect to it with smbclient from that server and second: Feb 11 17:09:47 localhost nm...

...0, Andy Lutomirski wrote: > Let's take a step back from from the implementation. What is a driver > for a virtio PCI device (i.e. a PCI device with vendor 0x1af4) > supposed to do on ppc64? Today, it's supposed to send guest physical addresses. We can make that optional via some nego or capabilities to support more esoteric setups but for backward compatibility, this must remain the default behaviour. > It can send the device physical addresses and ignore the normal PCI > DMA semantics, which is what the current virtio_pci driver does. This > seems like a layering vi...

On Tue, Sep 2, 2014 at 1:53 PM, Benjamin Herrenschmidt <benh at kernel.crashing.org> wrote: > On Mon, 2014-09-01 at 22:55 -0700, Andy Lutomirski wrote: >> >> On x86, at least, I doubt that we'll ever see a physically addressed >> PCI virtio device for which ACPI advertises an IOMMU, since any sane >> hypervisor will just not advertise an IOMMU for the virtio

On Tue, Sep 2, 2014 at 1:53 PM, Benjamin Herrenschmidt <benh at kernel.crashing.org> wrote: > On Mon, 2014-09-01 at 22:55 -0700, Andy Lutomirski wrote: >> >> On x86, at least, I doubt that we'll ever see a physically addressed >> PCI virtio device for which ACPI advertises an IOMMU, since any sane >> hypervisor will just not advertise an IOMMU for the virtio

...stale-usluge ) Koliko puta ste se zapitali? * ?to se doga?a s Va?om nekretninom dok Vas nema (posebno nakon nevremena)? * Uslijed neprovjetravanja Va?a ku?a-apartman ima neugodan miris? * Primjetili ste pojavu gljivica, vlage i plijesni? * ?elite izbje?i mukotrpna ?i??enja (kada do?ete i prije nego odlazite)? * ?eljeli biste iznajmljivati nekretninu kada ju ne koristite, ali to ne radite jer je to neizvedivo zbog udaljenosti (jednostavno ?ivite predaleko)? * Koliko puta ste se zapitali koliko novca i vremena tro?ite na samo jedan neplanirani (zimski) obilazak? Na sva postavljenja pitanja i...

...Betz je autor vi?e knjiga, a njegova posljednja pod nazivom ?Krafte aus dem Nichts ? Geheimnisvolle Orte und ratselhafte Energien? tretira drevne megalitne lokacije, menhire, dolmene i sveti?ta. Prave?i komparativnu analizu zaklju?io je da su drevni narodi bili tehnolo?ki i nau?no mnogo napredniji nego ?to im to dozvoljava konvencionalna nauka. Nakon mjerenja u Visokom Betz je odr?ao predavanje za stru?ni tim Fondacije i volontere Pete smjene zaklju?uju?i da postoji prisustvo elektromagnetnog zra?enja na vrhu Bosanske piramide Sunca frekvencije 28.125 kHz ?ime je potvrdio ranija mjerenja stru?nja...

...>> Let's take a step back from from the implementation. What is a driver >> for a virtio PCI device (i.e. a PCI device with vendor 0x1af4) >> supposed to do on ppc64? > > Today, it's supposed to send guest physical addresses. We can make that > optional via some nego or capabilities to support more esoteric setups > but for backward compatibility, this must remain the default behaviour. I think it only needs to remain the default in cases where the alternative (bus addressing) won't work. I think that, so far, this is just ppc64. But see below... &gt...

...>> Let's take a step back from from the implementation. What is a driver >> for a virtio PCI device (i.e. a PCI device with vendor 0x1af4) >> supposed to do on ppc64? > > Today, it's supposed to send guest physical addresses. We can make that > optional via some nego or capabilities to support more esoteric setups > but for backward compatibility, this must remain the default behaviour. I think it only needs to remain the default in cases where the alternative (bus addressing) won't work. I think that, so far, this is just ppc64. But see below... &gt...

...I would have though that winbind would be able to use this to encrypt and authenticate all LDAP traffic. However when I run tcpdump on port 389 on the server - see below (**) - it's clear that some of the traffic is unencrypted. It looks like winbind is at least trying to do some sort of negotiation (GSS-SPNEGO) but then after that is falling back to unencrypted queries. On the client machine I am able to kinit with the directory administrator creds and do ldapsearch at the command line with Kerberos authentication (-Y GSSAPI) But oddly, I cannot authenticate using the keytab: roo...