search for: ne01

Mike Brodbelt wrote: >I'm using Samba 2.0.7, and I've got a small problem hwich has been >annoying me for a while now. My clients are all NT, and print via Samba. >I'm continually getting files like this created:- >/DIRECS/INDIRS/Ne01: >/DIRECS/LONDIRS/Ne01: >/DIRECS/UNDIRS/Ne01: >/DIRECS/Ne01: >Does anyone know why they appear, and how I can get rid of them? Hi, Welcome to the club. This was introduced in Samba 2.03 with the "nt smb support" parameter. Due to the fact that no one has fixed it it must...

...r a few months with a small amount of windows95 users and last week we decided to move all our userfiles from our SCO box with visionfs over to the Samba machine. No problems so far. But, strange files are appearing in the directorys of the NT40 workstation users. Under Unix they look like Ne00: or Ne01: or Ne04: and so on. The highest I have seen is Ne05: Once they are there the stay the same. If you look at them from the windows machine they look like Ne01~go. As far as I see they get written by the NT client (UID) and only if he looked in that directory from his machine. It is not nessesary to...

...file from samba, I don't get the prompt and printing fails. I have looked through the mailing list and haven't found anything simluar. I also looked at the recent fixes to samba, but haven't seen anything that deals with this problem. Sometimes, NT seems to write a file called "Ne01:", could that be part of the problem. In both cases, the win32 function 'StartDoc' return 1, it just doesn't display the dialog box. Brian

...1.9.18p10. After setting "nt smb support = no" Samba 2.0.2 responds as fast as 1.9. Also this fixed another problem that I had with an NT 4.0 SP3 client. If a file that is stored on a Samba share is opened from the NT client and printed to a Samba printer. Samba creates the empty file Ne01: in the directory where file resists. This bug has been reported under PR# 13685. I will now check if this bug has been fixed in Samba 2.0.3. Best regards, Axel Neumann =================================================================== Cromemco MPCT GmbH...

...y are all zero byte files, named after a network interface, so I assume they may be temporary files which are not being deleted. Here's a list of a few # find /usr/local/filestore/ -name \*: -print ./CLIENTS/CURRENT/COLLR/Ne02: ./CLIENTS/CURRENT/SLDD/surveys/Ne02: ./PRODUCTN/MISC-TXT/Ne01: ./PRODUCTN/MISC-TXT/Ne00: ./SCHEMES/CUSAC/EXECMTGS/Ne03: Does anyone know what's creating these, and how I can prevent them from cropping up? TIA, Mike.

...iles, named after a network interface, so I assume they >may be temporary files which are not being deleted. Here's a list of a >few ># find /usr/local/filestore/ -name \*: -print >/CLIENTS/CURRENT/COLLR/Ne02: >/CLIENTS/CURRENT/SLDD/surveys/Ne02: >/PRODUCTN/MISC-TXT/Ne01: >/PRODUCTN/MISC-TXT/Ne00: >/SCHEMES/CUSAC/EXECMTGS/Ne03: >Does anyone know what's creating these, and how I can prevent them from >cropping up? >TIA, >Mike. Hi, Welcome to the club. This bug was introduced in Samba 2.0.3 I believe but has never been fixed. These files...

Hello, We have a problem with excel and samba 2.0.6. ( on HPUX 11.00 and Solaris ) It is not possible to print to a file within excel. You don't get the window to specify a filename.. If you set "nt smb support = no" in the smb.conf file, the problem disappears. Can somebody tell me what "nt smb support = no" really does?? Regards, Eddy Reniers Philips Research

...OK to save changes regenerates the error. It can be worked around by saving the document to a new name, but that appears to be the only way. After some experimentation, changing the value of the "nt smb support" parameter seems to have cured this. However, I get a number of files called Ne01: or similar created on my shares, for no obvious reason, and I had heard that this was due to a bug, which could be worked around by setting nt smb support to no, which was why I had it set that way. Environment:- Server - Linux 2.0.x with Samba 2.0.7 (though this problem was certainly in 2.0.6)...

...rkaround mentioned in the references at the bottom of this email (adding a 'veto files' directive to smb.conf) still appears to work with 2.2.x, I'm sending this message because the original problem appears to be half-fixed. That is, in 2.2.x, print queues associated with the ports 'Ne01:' through to 'Ne99:' work correctly, but those associated with 'Ne100:' and above do not. I've attempted to look in the Samba sources for evidence of the half-fix, but I admit defeat. In case anyone wants a look, I've got multiple annotated level 10 debug listings for s...