Eric Veith
2003-May-25 19:33 UTC
[Samba] Problem reading/writing permissions under Windows (V 2.2.8a)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, as the subject says, I've problems reading the permissions of a file/folder beeing located on my Samba server with the Windows-Explorer. To solve the problem, I've read through log.smbd and found that introducion error: "error packet at smbd/nttrans.c(86) cmd=160 (SMBnttrans) NT_STATUS_BUFFER_TOO_SMALL" followed by various NT_STATUS errors. While grepping the archive for that error, I found a message in wich the author wrote this would happen frequently because Windows often tries to read/creat files that do no really exist. That's fine with me, but actually there is a real error causing the problem I describe: When I open the properties of any file or folder and swith to the security task, Windows shows me the users owning it, but not the permissions (exactly, it tells me that nobody of these has any permission). When I try to set any, nothing happens (it returns to none) and I find new NT_STATUS errors in the log. Can someone help me to fix that issue? It would be great, because I want to use roaming profiles. I think that "NT_STATUS_BUFFER" causes the problem. Sincerely, Eric Veith -----BEGIN PGP SIGNATURE----- Version: PGP 8.0 iQA/AwUBPtEannS3DTmNKZL8EQLZkwCgj7tfMrDBXcDYXydVDW1NKbf/0FoAmgJV csptV8y7N4REi9nd7pt2XDgC =ll/t -----END PGP SIGNATURE-----
David Morel
2003-May-25 21:40 UTC
[Samba] Problem reading/writing permissions under Windows (V 2.2.8a)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Dimanche 25 Mai 2003 21:33, Eric Veith a ?crit :> Hello, > > as the subject says, I've problems reading the permissions of a file/folder > beeing located on my Samba server with the Windows-Explorer. To solve the > problem, I've read through log.smbd and found that introducion error: > "error packet at smbd/nttrans.c(86) cmd=160 (SMBnttrans) > NT_STATUS_BUFFER_TOO_SMALL" followed by various NT_STATUS errors. While > grepping the archive for that error, I found a message in wich the author > wrote this would happen frequently because Windows often tries to > read/creat files that do no really exist. That's fine with me, but actually > there is a real error causing the problem I describe: When I open the > properties of any file or folder and swith to the security task, Windows > shows me the users owning it, but not the permissions (exactly, it tells me > that nobody of these has any permission). When I try to set any, nothing > happens (it returns to none) and I find new NT_STATUS errors in the log. > > Can someone help me to fix that issue? It would be great, because I want to > use roaming profiles. I think that "NT_STATUS_BUFFER" causes the problem.maybe not. On what filesystem are you trying to set attributes ?> Sincerely, > Eric Veith- -- *********************************** david.morel@amakuru.net OpenPGP public key: http://www.amakuru.net/dmorel.asc 28192ef126bc871757cb7d97f4a44536 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+0ThIqr7QF98duCMRAmpIAJ9HQLG0Kcyhj0rdyBVY0slVXjovhgCfSQ6i EahLR4AW4aloDn1fm7KV6f0=QbWg -----END PGP SIGNATURE-----
Gerald (Jerry) Carter
2003-May-27 14:51 UTC
[Samba] Problem reading/writing permissions under Windows (V 2.2.8a)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 25 May 2003, Eric Veith wrote:> To solve the problem, I've read through log.smbd and found that > introducion error: "error packet at smbd/nttrans.c(86) cmd=160 > (SMBnttrans) NT_STATUS_BUFFER_TOO_SMALL" followed by various NT_STATUS > errors. While grepping the archive for that error, I found a message in > wich the author wrote this would happen frequently because Windows often > tries to read/creat files that do no really exist. That's fine with me,No. This is usually seen when a fragmented RPC PDU needs to be continued in an SMBread/write.> Can someone help me to fix that issue? It would be great, because I want > to use roaming profiles. I think that "NT_STATUS_BUFFER" causes the > problem.I'm just a little short on details? What is the exact error? Where are you storing profiles? What are the permissions? What client OS and SP? etc.... cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+03t+IR7qMdg1EfYRAnTMAJ4oDIK1F9+xXEMGlVmp4S3wjx1QqQCeNyHB kx4Mo5EOOy+Ks9fhq6HK9Qk=gk5T -----END PGP SIGNATURE-----
Apparently Analagous Threads
- kerberos5 / gssapi support in mount.cifs?
- samba-tool ntacl sysvolreset - NT_STATUS_BUFFER_TOO_SMALL
- Problem setting password: : failed to pull old supplementalCredentialsBlob: NT_STATUS_BUFFER_TOO_SMALL
- iconv.c / static charset prototype/assembler bug?
- SMB Signing with "map to guest = " options