similar to: Temporary file grief

Mike Brodbelt wrote: >Hi, >I'm running Samba 2.0.6 here as our main file server. Authentication is >done against an NT PDC, and Samba is also responsible for printing. >I'm getting some odd files created which aren't being deleted. They are >all zero byte files, named after a network interface, so I assume they >may be temporary files which are not being deleted.

At 4:00 every morning the 2 WinXP machines on my network generate a slew of queries to bad printer names. These names are variations on the name of a valid printer exported by Samba. Samba v3.0.10 is running on a RHEL4 system. It exports several shared drives and a single printer. The printer is named "lj4500", is managed by CUPS v1.1.22, and works correctly via Samba from both

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?

Hello, I am using Samba 2.0.3 on my FreeBSD 2.2.7 box. Works fine. It is already running for 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

Dear R Community, I have a dataframe like this dat product1 product2 ... productn 01.1.2008 1 1 1 02.1.2008 1 1 2 . 15.2.2008 2 2 NA . 04.4.2008 2 2 1 05.4.2008 NA 2 NA (date ascending order, 1:n products with status 1, 2 or NA) and want to produce a graphic like

Our Samba print server seems to slowly degrade, and get more and more errors over time, until it starts recieving "tdb fetch failed" messages, fatal errors, and getting INTERNAL PANIC's and dumping core etc.... I believe this to be related to .tdb corruption, but the tdbbackup utility does not see any problem with the TDB's. Eventually, certain printers will go

Hello. Maybe after work with FreeBSD I become too spoilt, but I expect that packages from one distribution kit works among themselves well. But that I see: $ rpm -qa | grep rpm rpm-libs-4.3.13_nonptl rpm-python-4.3.13_nonptl rpm-4.3.13_nonptl rpm-build-4.3.13_nonptl $python >>> import rpm ImportError /usr/lib/librpm-4.3.so: undefined symbol: rpm_execcon Thanks.

I noticed a few weeks ago that I was no longer able to access shares on a win98 box called cs198787-a. This used to work but it's now broken and I have no idea why???? I'm going nuts trying to fix this. I've even gone out and bought the book "Using Samba" .... great book btw. The samba server is running on a SuSE linux system and passes all the tests in the

Hi group, I can't seem to get passwd change from windows to work. I am running samba 3.0.20-3.1.20060mdk installed from rpms on Mandriva 2006; the clients are windows XP sp2. When I try to change passwd from windows I get "You do not have permission to change your password". What am I doing wrong? My global smb.conf is below. >From log.smbd I think this error pertains to

I have problems with one Windows NT. I installed Samba 2.0.2, but that did not helped. Kari Hurtta wrote: >Actually situation gone worst. Adding > nt support = no >halped somewhat (new problems seems disappeared). >That new errors was that printing try caused >that NT reported about IO-errors. >I just want indicate that special nt support >code perhaps have some

Hi We've noticed that we get zero length files left behind on Samba shares after printing to a Samba printer, of the form NExx: (appears as NExx~yy) from Windows due to name mangling. This only occurs in specific circumstances: Client running NT4 (SP6a) and Printing file on a Samba share and Printing to a Samba printer and Running particular applications (e.g. Word and Acrobat, but not

I have a bit of a problem, however, I am not sure if it has been solved, or what. I have: RedHat Linux 7.2 samba version 2.2.1a Client machine is Windows NT 4.0 (Service Pack 5.0) Printer: using an NT driver on an NT machine configured to print to the port-'file'. problem: I am trying to print a file on a samba file server to a "printer". When the file is stored on an

Hi, I've recently had the following experience, which may be of help to people here, so I'm mentioning my tests and conclusions. I've recently been observing this behaviour from Samba - this is an easily reproducible problem:- 1/ Open a share 2/ Create a new document in Word. 3/ Make some changes. 4/ Save the document using the save icon on the toolbar, this works as expected. 5/

Hi, This is a message requesting help for the following problem: Printing Word 97 documents, stored on a Samba server, on an NT4 system to an LPD print queue fails under certain well-defined conditions, creating an empty file called 'Ne<number>:' (e.g. 'Ne120:'). The problem appears to be easily reproducable, as long as you have more than 99 print queues on your NT system.

Dear all. After much grief I have finally found the source of some weird discrepancies in results generated using R. It turns out that this is due to the way R handles multi-line expressions. Here is an example with R version 2.8.1: ---------------------------------------------------- # R-script... r_parse_error <- function () { a <- 1; b <- 1; c <- 1; d <- a + b + c; e

Hi, as I wrote before: I'm not able to connect a Windows XP Pro notebook to a Samba 3.0.4 server. All the other machines (most Windows XP Pro, but also a few Windows 2000 and Windows 98) can connect without any problem. This one machine is not part of the NT domain because it needs to connect 1 or 2 times a week only, and is on the road most of the time. The machine could connect

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