similar to: No subject

gid=500) (pid 30102) [2000/11/30 10:44:37, 0] smbd/nttrans.c:call_nt_transact_ioctl(2516) call_nt_transact_ioctl: Currently not implemented. uname -a: Linux ***** 2.2.14-5.0smp #1 SMP Tue Mar 7 21:01:40 EST 2000 i686 unknown smbd -V: Version 2.0.7 nmbd -V: Version 2.0.7 rpm -a -q | grep samba: samba-common-2.0.7-4 samba-client-2.0.7-4 samba-2.0.7-4 ls -l samba*: -rw-rw-r-- 4312642 Oct 18 11:54

Guys, I think the answer to my question is to upgrade samba. However, since this is my production machine, I thought I would try and understand the problems I'm having a little better to insure that an upgrade will correct my issues. My setup - Mandrake 7.2, samba 2.09. Win98, ME and XP clients. The 98 and ME machines have no problems. The XP machine has some intermittent slowness

Hiya! Samba 2.0.7 on HP-UX 11.0. When a user tries to map a drive, the smb.log shows the following: NOTE: the stanza ending in PANIC repeats 3 times, snipped here for brevity ===================================== [2002/02/28 11:12:43, 1] smbd/server.c:(641) smbd version 2.0.7 started. Copyright Andrew Tridgell 1992-1998 [2002/02/28 11:12:43, 1] smbd/files.c:(215) file_init: Information

Hi, I've seen a few messages about this but no answers in the archive... I have a win2k machine & a Redhat7.0 machine running samba2.0.7. I recently had to re-install my win2k machine, so I backed up everything onto the samba machine (approx. 5Gb). When I copied the files back to the win2k machine after the re-install, some of the files turned out to be corrupted. There were no errors

Hello Guys, I'm having a very strange problem with my file server ( latest samba RPM from redhat ) [root@krusty secundarias]# rpm -qa | grep samba samba-client-2.0.10-2 samba-2.0.10-2 samba-common-2.0.10-2 [root@krusty samba]# uname -r 2.2.19 One of our machines ( NT4 workstation with SP6a ) is saving files on a share that becames unacessible for all users. After some research on

Hi, I've a question about a problem using a samba share in a UNIX AIX server. In my scenarious there is a fileNET server (running on a win2000 server) which use a samba share on a AIX sever for cacheing file, this share is configured for allow access to a particular user (pangol). It seams that user have access permission but an error is returned when fileNET try to write a file. Thanks in

We are running Samba 2.0.7 on a Redhat 7.0 Server in an Accounting Practice. When one of our users trys to open Handy Ledger which is stored on out JDAData Share. When he trys to connect I get the following messages in the logs. [2001/03/19 16:22:43, 0] smbd/nttrans.c:map_share_mode(443) map_share_mode: Incorrect value 0 for desired_access to file \ [2001/03/19 16:22:43, 0]

Hi, We have a large (8 CPUs, 32GB RAM) x86 Sun server running x8664 Debian Lenny, with Samba 2:3.2.5-4lenny6. It's a BDC and file server. I have noticed various entries in the log files that I'd like to understand better. Some machines are generating this: [2009/11/16 15:10:49, 0] smbd/nttrans.c:call_nt_transact_ioctl(2019) call_nt_transact_ioctl(0x9005c): Currently not implemented.

Hi William, I got no positive reply since I made my posting. Only you and another guy, who made the same experience. No answer to the question, what functionality has "call_nt_transact_ioctl" and what effect on SAMBA has the missing of this procedure. Sorry, Michael William Soudan schrieb: > Hi Michael, > > I'm getting the same message in our samba logfiles as you

On a server that has been running smoothly since it was setup, and with no changes to configurations or network or anything, users cannot save a shared QuickBooks file. they have been regularly using, updating and saving to this file for a few months. All users are able to create and update other files in the same share. I have not confirmed if they are able to create and update new QuickBooks

This message I found in my smb log file : [2000/01/31 08:56:47, 0] smbd/nttrans.c:call_nt_transact_ioctl(2387) call_nt_transact_ioctl: Currently not implemented. corresponding code in nttrans.c : /****************************************************************** ********** Reply to IOCTL - not implemented - no plans. *******************************************************************

I am running samba-2.0.3-8 on Redhat 6.2 in five global locations. All are fine except one. In this location when a user runs MS Visual Developer they are able to open, save compile and edit files just fine. However when they type either [Enter] or [Bkspc] to add or delete a line, in this case only MSVD hangs for several seconds. Insert several lines and wait 1+ minutes!!! I have watched the

Hello, we run samba 2.0.6 on Solaris2.6 and use it together with clearcase (version 3.2.1). Sometimes the checkout of files from a clearcase NT-client hangs and probably causes clearcase to destroy the viewstore. In the samba logfile of that client I found the following message: [2000/02/17 09:29:49, 0] smbd/nttrans.c:call_nt_transact_ioctl(2401) call_nt_transact_ioctl: Currently not

Hi everybody I'm actually facing some strange messages in smb logs: our samba server is running fine but I can see a lot of this message in the log : Apr 27 13:33:53 lnx-ds01 smbd[18773]: [2009/04/27 13:33:53, 0] smbd/nttrans.c:call_nt_transact_ioctl(2029) Apr 27 13:33:53 lnx-ds01 smbd[18773]: call_nt_transact_ioctl(0x90060): Currently not implemented. after sometime (one hour, one

Hi All, I'm experiencing some really funky Samba errors, and I'm hoping that some of you might have some ideas. This only happens sporadically, and when it does, I loose Samba connectivity for a while. Here are my Samba logs: Jun 2 13:29:01 nasone smbd[20289]: [2004/06/02 13:29:01, 0] smbd/nttrans.c:call_nt_transact_ioctl(2076) Jun 2 13:29:01 nasone smbd[20289]:

Hi samba lists !! =20 =20 I=A1=AFm found error message Windows XP =A1=B0The network name cannot be found" When I try to connect to smb server that is mapped e: =20 1. I was downloading very large file 40GByte with torrent during 5 hours. 2. This error occurred!=20 3. But web server and telnet is OK 4. I retry to reconnect to smb server with IP

All, Since upgrading to 3.0.23d on several linux servers, I'm seeing the following error repeatedly in my logs: Jan 2 15:05:49 boothost smbd[27935]: [2007/01/02 15:05:49, 0] smbd/nttrans.c:call_nt_transact_ioctl(2332) Jan 2 15:05:49 boothost smbd[27935]: call_nt_transact_ioctl(0x90078): Currently not implemented. Aside from the obvious, what does this error mean? I've googled for

I'm seeing these errors every couple minutes from my Samba server (3.0.28... RHEL5 build). [2008/09/15 11:59:44, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463) call_nt_transact_ioctl(0x9005c): Currently not implemented. I realize what 'currently not implemented' means, and since no users have complained, I assume the message is ignorable. I was wondering however, if anyone can

As I posted to samba@samba.org one month ago, we found the same error as Chuck Thier (smbd/nttrans.c:call_nt_transact_ioctl(2401) call_nt_transact_ioctl: Currently not implemented.) as a possible reason for some crashes of ClearCase clients on WindowsNT (we use Samba 2.0.6 on Solaris 2.6 and ClearCase 3.2.1). Therefore I support his wish, that this functionality should be implemented in samba

Hi folks, First of all I have a well-working samba-2.2.2-20011013 on a Redhat 7.1 with 2.4.7. (Fast like a thunder 8-). Good job guys!) But. I have a little problem with printing: At my work we have only NT 4.0 workstations on our LAN with sp6a or sp5. This problem is appearing when a client try to print onto a printer attached to samba. Sometimes. But sometimes not. > api_net_sam_logon: