similar to: Strange files

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?

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.

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. Here's a list of a few # find

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 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

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

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, 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.

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

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

I initially thought this was a cups problem, but looks like samba now . . . I have been using a Brother MFC9880 printer with Samba. Everything has been fine for the last month, until things stopped working recently (on a Monday morning with no intervention over the weekend. Samba log is below: My system: Debian woody Samba-2.2.3a-14.1 cupsys-1.1.14-5woody1 MFC9880 connected to server by USB.

On 17 May 99, Axel Neumann <amn@cromemco.com> had questions about DOS to UNIX Conversion: > It seems that a lot of people hate Windoze in such a way that they only > accept solutions that are not coming from M$. Maybe that's because the M$ "solutions" are crap, and much better alternatives already exist. > If you want to view UNIX text files correctly on a W9x

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

I am experiencing a problem with all time stamps having the same date and time stamp. I found this bug report http://us1.samba.org/listproc/samba/June1998/0239.html and see there is a fix. The question I have is has this issue been resolved in later versions of Samba code. It would be easier to upgrade than deal with a code change and re compilation. Scott Ranzal -------------- next part

On 07/29/2016 02:52 AM, Peter wrote: > On 29/07/16 18:10, John R Pierce wrote: >> also, try and scrounge another DDR2 SODIMM for that thing, according to >> my google search, it supports up to 2 x 4GB == 8GB, and you said you >> only have the stock 2GB. > > They are dirt cheap on ebay, from Hong Kong with free shipping. I would > go all the way and max it out. >

Hi! I''ve just a created a really simple rails scheduled worker for backgroundrb to start playing with : class SessionCleanerWorker < BackgrounDRb::Worker::RailsBase def do_work(args) logger.info "SessionCleaner> started" CGI::Session::ActiveRecordStore::Session.destroy_all( [''updated_at <?'', 120.minutes.ago] )

CentOS-6 When I login as root I see this prompt: [root at vhost04 ~]# When I login as a non-priviledged user I see this instead: sh-4.1$ .bashrc and .bash_profile have identical contents in /root and /home/user. What causes the difference? Why? How does one change the default so that all normal users get a [userid at hostname pwd]$ prompt? I have loked in/etc/profile.d and /etc/bashrc

Hi, I'm installing E100P for isdn pri line. My configuration are like this. zaptel.conf ======================================= span=1,0,0,ccs,hdb3,crc4 loadzone = us defaultzone=us bchan=1-15 dchan=16 bchan=17-31 zapata.conf ================================================= [channels] context=default switchtype=euroisdn context=default signalling=pri_net usecallerid=yes

I have problems import ms access 2000 data into Word 2000. The error is: DDE connection failed. Browsing the internet I found out that ms access uses ODBC for this (am I correct?). I have installed MDAC_TYP.EXE like in the Winehq documentation. I think that the msaccess driver doesn't work o.k. To reproduce: Run wine c:\windows\system\ODBCAD32.EXE --> in