similar to: OK, need some help with Win2K clients real bad

Greetings, I read with interest the few posts in the archives discussing problems I have recently encountered with data corruption of an ACT 2000 database residing on a Samba 2.07 share, SuSE Linux 7.1 (2.2.28 kernel), with about 25 Win2K clients. I did not, however, see any apparent resolution to this major problem - I either am going to have to rebuild from scratch my current Win2K Server, or

Hi all, I was wondering what the feeling was of those on this list as to how stable this alpha is? Is it useable in a production environment for basic file sharing of a shared database (ACT)? The reason I am asking is I am having major file corruption issues with Win2K clients using 2.07, and if the suggestions already made do not fix the problem, I would be willing to try it, if it is

Help! I finally got it installed, and now I can't get into SWAT... I go to http://servername:901, and get a 'The connection was refused by the server" Can anybody tell me what dumb thig I'm doing wrong? I really ned to get this thing working tonight... Thanks Charles Marcus

Hi, I just installed 2 Win2K sp4 workstations on an otherwise working Samba 2.2.8a network and 2 of the 3 printers are showing "Access denied". What's up with that? The other computers that are working just fine are Win98, XP and Win2K NOT sp4. Here is part of the global section: printing = bsd load printers = yes disable spoolss = yes printcap name

Hello, I have a new RH 7.2 installation (kernel 2.4.7-10) with Samba 2.2.1a and I can't print from my Win2K box. I get an "Access denied: unable to connect" error from the printer entry in Windows. The logs don't seem to be helping me. Here's my smb.conf file: [global] workgroup = MYGROUP server string = Samba SMB Server interfaces = 192.168.1.1/24 127.0.0.1/24 hosts

I've discovered a couple of things while troubleshooting my printer setup problems. 1. print$ must be 0744. I ran a level-3 debug, and was seeing "chmod failed" errors. Upping it to level-10, I saw something that pointed to unix rights of 0744; my dir's were set to 0755 or 0777...neither worked. When I set print$ and it's subdir's to 0744, the chmod errors went away.

I have a patch that enables "user password timeout" for 2.2.2. It works only for WinNT, Win2000 (tested and Samba on AIX and Linux) and I think with WinXP. It does not work with Win9x. You can download the patch from http://www.m-wohlfarth.de/Downloads/Samba/samba.html. I never had the problem with automatically expiring password as described in the originating message - I couldn't

I have a small Samba 2.2.1a plus Win2k workgroup. Samba is running on Redhat 7.2. There is a networked laserjet 5000 using a static IP which I can print to successfuly from the linux box, and from the win2k workstations via the queue on the linux box. The weird thing is that, on the win2k worksations, if I double click on the printer icon the status of the printer is reported as "Access

Hello to all, This is my first ever use of a mailing list so bear with my ramblings and illiterate prose. I have been using samba from 2.03 to 2.07 for over a year now. We run DHCP, WINS on the samba (acting as domain) box running Mandrake 6.0. Windows machines are running everything from Win95 up to Win2K. With Win2K I have problems with slow read/write, particularly for one application

I have a Redhat Linux 7 machine running Samba 2.07 for file server access only. Samba is setup to use our NT server (4 w/sp6) as the primary domain controller to validate accounts on. Fine, this is all working dandy. Except that for some odd reason, when some of our Win2k clients are accessing the file server, they will occasionally get an "Insufficient Quota" error. Now,

Hello again, Thanks James for your replies. In regards to the slow read/write, the software vendor is aware of the problem, at some stage they will buffer the read/write, but it won't happen overnight, the binary file is quite complicated. So there are no updates available for this particular issue and I don't expect any for a couple of months. The software in question can generate

I?m running Debian Linux 3.0 r1 with Samba 2.2.8a and I have got printing problems: --- when I print something the job don't appear in the window printing status, so I have no way to check the actual status of the job, or to delete the job from window printer status in Win2K. here is configurations file of smb.conf: [global] workgroup = Gertian log level = 99 queuepause

I have been working on loggin onto my linux server from my win2K box and get this error in the log.smb file passdb/smbpassfile.c:trust_password_lock(119) trust_password_lock: cannot open file /etc/NEFF.LINUX.mac - Error was no such file or directory passdb/smbpasssfile.c:trust_get_passwd(288) domain_client_validate: unable to open the machine account password file for machine LINUX in domain Neff

Is there a way foe me to get the print job name to be something other than "remote downlevel job"? All my jobs are now printing flawless except for this. I would like to be able to get a file name or program at least. Thanks Tony McGrew www.multicam.com

I'm running Samba 2.27 on RH8 system. I've got samba as the print spooler for Windows XP clients and using winbind as the user validation against my Win2K DC. Permissions on the spool directory are root root with the sticky bit on. Clients can delete their own jobs from the que, but the spool directory is not being expunged of print jobs and the last job constantly displays in the client

Hi All, When I use smbmount to attach a NT 4 Server's drive C:, I use the following command: smbmount //inet_server_1/C$ /mnt/server1 -o username=xxxxxx,password=xxxxxx,fmask=700,dmask=700,nosuid,noexec now, if I am su'd to root, and do a df -h I get: Filesystem Size Used Avail Use% Mounted on /dev/hda1 6.7G 2.5G 3.8G 39% / //inet_server_1/C$ 7.8G 3.2G

My Win98(SE) Samba clients can query the Samba-exported printer status, but Win2K(SP3) clients cannot. Both clients can actually print documents. I am running Samba v2.2.3a on a Linux (Red Hat v7.3) system. This server makes 2 printers (via a LPR subsystem) and several shared directories available to our Linux, Win98 and Win2K (soon to be WinXP also) clients. From a Win98 client, print

I'm currently having a problem with the new released Samba 2.2.5: I cannot print anymore on my shared printer. What is strange is that It worked fine with samba 2.2.4, but now I got an access denied whenever I try to access the printer... /var/spool/lpd/samba is chmod 777 and the username is in the group lp Here is part of my smb.conf: [global] workgroup = HOME netbios name =

Hi, I am new to samba and Linux and need some help coming up with a solution to a nerve racking problem. Here is what we are trying to do. Users log into an NT environment (accessing shares via samba running on Linux/Aix). The user should only see and have access to the share(s) he/she has been assigned to. Similar to Novell "map root" or symbolic links. Our issue is try to

I've seen this issue asked about and asked about in the archives, unfortunately I can't seem to find a real solution only people's theories. The issue involves a 2.2.5 Samba server acting as a member print server in a Windows 2000 domain. I can add printers from the server to clients in the domain and then print. The issue comes when I try and view/manage the print queue from Windows.