Displaying 5 results from an estimated 5 matches for "lason".
Did you mean:
jason
2006 Oct 18
1
Using CHROOT jail in SFTP
...fails with the following in the /var/log/messages file:
sftp-server[11001]: fatal: Couldn't chroot to user directory /home/newyork/ftpbcc: Operation not permitted
I was wondering why one would work and the other would not.
I am running SUSE Linux Enterprise server 9.0.
Regards,
John Monagin
Lason, Inc.
Office - 734-632-1681
Fax - 734-632-1650
Cell - 248-767-3956
jmonagin at lason.com
2005 Apr 04
6
NT_STATUS_WRONG_PASSWORD with multiple concurrent connects from same IP Address.
We are having a problem with SAMBA v 3.0.13 on Linux where a windows client
(single IP address) makes multiple connections at the same time
(different processes) to copy files onto our SAMBA server. As many as 20
simultaneous connections/file transfers may be occurring from the
same client IP address.
Some of the files succeed, and some fail. The windows client reports
that the directory does
2005 Apr 10
0
NT_STATUS_ACCESS_DENIED with winbinddauthentication
Thanks for looking Jerry...
Andrew Bartlett suggested trying spneg=no, and I'm going to test that later today...
Here's the URL of my original question:
http://lists.samba.org/archive/samba/2005-April/103115.html
To further clarify, I've spoken to the vendor of the software that's making the connections to the server (Sterling Commerce Connect:Direct) that they intentionally
2005 Apr 06
0
Bug? Authentication failure with multiple logins from same client IP addy
We have a client machine (Windows 2000) that runs an application which spawns separate processes with each authenticate separately to the SAMBA server (3.0.13)
When several of these processes run at the same time, SOME of the authentications fail with NT_STATUS_WRONG_PASSWORD written to the log.smbd file (error level 2)...I've attached a snippet of the log file to the end of this message
All
2005 Jun 03
1
NT_STATUS_WRONG_PASSWORD with multiple concurrent connects from same IP Address.
Andrew:
RE: SPNEGO=NO to solve Multiple simultaneous connects from the same client system..
We're finally getting around to implementing this parameter...we've discovered that it breaks connectivity with some of our Windows Xp clients...for some reason certain users are unable to authenticate from some of the Xp systems (the logs report NT_STATUS_NO_SUCH_USER). Strangely enough, other