search for: ntforms

I have been successfully running with Samba 2.0.7 for more than a year now but am having problems using version 2.2.7; both are running under HP-UX. The 2.2.7 version of Samba is running under HP-UX 11, the 2.0.7 is running under HP-UX 10.20. Drive connections to Windows 2000 systems have started coming up with 'Drive already connected' errors. The log.smbd file has lots of (No locks

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: Jan Mostert.vcf Type: text/x-vcard Size: 715 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20020306/e36726e6/JanMostert.vcf

Hello All, I have come across a problem that I am not sure where to begin: We have an HP DesignJet 5000 PS 60 wide format printer that is part of our public printing pool which we share out to the pc world via Samba. I am using Samba 3.0.11 in RHAS Enterprise Linux, Update 3. When I install the printer driver onto the server using the Windows APW, and then install the printer on a fresh

...r properties dialog is open, responses to clicks in it are very very slow, and ethereal shows me a stupidly huge amount of DCERPC request/response traffic between the XP box and Samba (hundreds per second, with the same small set duplicated). Questions for those kindly disposed to noobs: 1. Does ntforms.tdb only store certain standard settings (page size, orientation, whatever) or can it hold anything a Windows printer driver cares to throw at it? 2. Do I need to make ntforms.tdb writable by anybody other than root (for example, should I set it to root:lpadmin rwxrwxr-x like the directory where...

...ssentially the primary server periodically rsyncs a bunch of files over to the backup, including a collection of the tdb files. When I try to connect to the backup server, I get the following smbd panics in the logs: ----- [2010/05/11 14:34:32, 0] lib/util_tdb.c:tdb_log(682) tdb(/var/lib/samba/ntforms.tdb): tdb_reopen: file dev/inode has changed! [2010/05/11 14:34:32, 0] lib/util.c:reinit_after_fork(1054) tdb_reopen_all failed. [2010/05/11 14:34:32, 0] printing/print_cups.c:cups_pcap_load_async(432) cups_pcap_load_async: reinit_after_fork() failed [2010/05/11 14:34:32, 0] lib/util.c:smb_p...

...g tdbs to registry. * BUG 9735: Fix Winbind separator in upn to username conversion. * BUG 9766: Cache name_to_sid/sid_to_name correctly. Note about upgrading from older versions: ----------------------------------------- It is still the case that there are printing tdbs (ntprinting.tdb, ntforms.tdb, ntdrivers.tdb) which are in latin1 or other encodings. When updating from Samba 3.5 or earlier to Samba 3.6 or 4.0 these tdbs need to be migrated to our new registry based printing management. This means during the migration we also need to do charset conversion. This can only been done manua...

...g tdbs to registry. * BUG 9735: Fix Winbind separator in upn to username conversion. * BUG 9766: Cache name_to_sid/sid_to_name correctly. Note about upgrading from older versions: ----------------------------------------- It is still the case that there are printing tdbs (ntprinting.tdb, ntforms.tdb, ntdrivers.tdb) which are in latin1 or other encodings. When updating from Samba 3.5 or earlier to Samba 3.6 or 4.0 these tdbs need to be migrated to our new registry based printing management. This means during the migration we also need to do charset conversion. This can only been done manua...

...and about 150 printers. All printing is PostScript and goes to HP and Canon printers over lpd through custom 'if' filters which do accounting. To help this we're trying to automate the printer and driver registration processes, in particular make the nt_printers.tdb, ntdrivers.tdb (and ntforms.tdb?) files from some kind of textual config file which might look like this: pr-london1: hp2200 pr-newyork3: hp4000 ... Our goal is to bring our printing in line with our other configuration management, which has a central server of configs for routers, servers and so on. The config server d...

...We've got Sambe 3.0.14a and cups 1.1.23 on a Debian system. I've run: cupsaddsmb -U RALPH\\jgoerzen -a -v Where RALPH is our PDC (and it also the machine I'm running this command on). The entire command *appears* to work, but: * None of the tdb files in /var/lib/samba, including ntforms.tdb, ntprinters.tdb, etc. have their date stamp updated. (They all still show last month, which is when we upgraded to Samba 3). * Whenever we have had to shut down (cleanly) the server and reboot, on reboot, Samba has completely forgotten about all of our printers. I usually hav...

...the guest is a chrooted subdirectory on the host. When openVZ migrates a guest between two host machines it uses rsync to transfer the files. Unfortunately, this causes samba to panic and not accept any new connections (established connections are OK). In the logs I get " tdb(/var/cache/samba/ntforms.tdb): tdb_reopen: file dev/inode has changed!" . Of course the inode changed, but does it need to panic? Is there a workaround? Centos 5 samba-3.0.25b-1.el5_1.4 [2008/01/22 11:53:46, 0] lib/util_tdb.c:tdb_log(662) tdb(/var/cache/samba/ntforms.tdb): tdb_reopen: file dev/inode has changed! [...

...eed to have copied between the computers and which need to be made on each server. The specific question I am dealing with is what TDB files I need to replicate filesystems between the two servers. Below is a list of what the files I see in my samba directory are: account_policy.tdb ntdrivers.tdb ntforms.tdb share_info.tdb group_mapping.ldb ntprinters.tdb registry.tdb wins.dat private/schannel_store.tdb private/secrets.tdb I am wondering first which of these need to be replicated from server to server and which need to be unique to each server? For instance I know that account_policy.tdb can be re...

...the new server - make hot backups cd /var/lib/samba tdbbackup *.tdb - scp the backups to the new server - restore the tbd in the new server tdbrestore account_policy.tdb < /tmp/backup_dir/account_policy.tdb.bak tdbrestore ntdrivers.tdb < /tmp/backup_dir/ntdrivers.tdb.bak tdbrestore ntforms.tdb < /tmp/backup_dir/ntforms.tdb.bak tdbrestore ntprinters.tdb < /tmp/backup_dir/ntprinters.tdb.bak tdbrestore passdb.tdb < /tmp/backup_dir/passdb.tdb.bak tdbrestore registry.tdb < /tmp/backup_dir/registry.tdb.bak tdbrestore secrets.tdb < /tmp/backup_dir/secrets.tdb.bak td...

...n't work. I don't want to have to disjoin and re-join all my users since then all their information will need to be copied over to the newly created profile. Any and all help is appreciated. .tdb files copied over: -brlock.tdb -connections.tdb -locking.tdb -messages.tdb -ntdrivers.tdb -ntforms.tdb -ntprinters.tdb -printing.tdb -secret.tdb -sessionid.tdb -share_info.tdb -unexpected.tdb

...stribution. Besides pushing all the drivers from a central location to the edges, the administrator should also be allowed to customize the drivers settings and the distribution should send those customizations to the edges. I understand those settings are stored in the TDB files (ntprinters.tdb, ntforms.tdb, etc). The HOW-TO guide shows how to initialize the valid Device Mode. I wonder if there is any programmatically way to clone those valid settings to all the edges. Also, besides 'tdbdump' and 'tdbbackup', are there other tools to manage the TDB files? I'm developing on...

...; -DLOCKDIR="/usr/local/samba/var/loc ks" -DSMBRUN="/usr/local/samba/bin/smbrun" -DCODEPAGEDIR="/usr/local/samba/l ib/codepages" -DDRIVERFILE="/usr/local/samba/lib/printers.def" -DBINDIR="/us r/local/samba/bin" -DFORMSFILE="/usr/local/samba/lib/ntforms.def" -DNTDRIVER SDIR="/usr/local/samba/lib" -DHAVE_INCLUDES_H -DPASSWD_PROGRAM="/bin/passwd" -DSMB_PASSWD_PROGRAM="/usr/local/samba/bin/smbpasswd" -DSMB_PASSWD_FILE="/u sr/local/samba/private/smbpasswd" -DSAM_DIR="/usr/local/samba/sam" -DSMB_P...

...eed to have copied between the computers and which need to be made on each server. The specific question I am dealing with is what TDB files I need to replicate filesystems between the two servers. Below is a list of what the files I see in my samba directory are: account_policy.tdb ntdrivers.tdb ntforms.tdb share_info.tdb group_mapping.ldb ntprinters.tdb registry.tdb wins.dat private/schannel_store.tdb private/secrets.tdb I am wondering first which of these need to be replicated from server to server and which need to be unique to each server? For instance I know that account_policy.tdb can be re...

Hi Folks, I'm part of a Novell department that is working on moving from Novell NDPS printing to Samba printing. I have been told that the Samba environment will have to be clustered to assure the same level of redundancy for printing. Does anyone have any pointers? Whether actual experience in this or a location of good documentation of the clustering process? Thanks for

...mem-r REG 8,1 8192 69697 /usr/local/samba/var/locks/brlock.tdb smbd 27615 root mem-r REG 8,1 8192 69692 /usr/local/samba/var/locks/printing.tdb smbd 27615 root mem-r REG 8,1 8192 69693 /usr/local/samba/var/locks/ntdrivers.tdb smbd 27615 root mem-r REG 8,1 696 69695 /usr/local/samba/var/locks/ntforms.tdb smbd 27615 root mem REG 8,1 14831 22540 /lib/libdl-2.2.4.so smbd 27615 root mem REG 8,1 92218 22542 /lib/libnsl-2.2.4.so smbd 27615 root mem REG 8,1 26599 22503 /lib/libcrypt-2.2.4.so smbd 27615 root mem REG 8,1 1459437 22500 /lib/libc-2.2.4.so smbd 27615 root mem-r REG 8,1 8192 69694 /us...

...ouble with. Response time has gone from 30-40 seconds to 1-3 seconds. This is MUCH more reasonable. Details: I have a multitude of printers, but the worst one was one of my Canon ImageRunner 5000. I stopped samba: service smb stop removed the tdb files: cd /var/cache/samba rm ntprinters.tdb ntforms.tdb ntdrivers.tdb cd printing rm <printername>.tdb printers.tdb restarted samba: service smb start Samba then recreates the tdb files as it starts. I am not sure that you need to remove anything other than <printername>.tdb since I removed everything, but after I did I was able to r...

My samba has been setup in its current configuration for around 9 months and has worked without a problem, over the weekend my windows boxes were unable to access the samba shares. Using SWAT I found that the smbd was not starting. I have tried the following: Trying to start smbd (as root) from the cli with: smbd start Seems to execute the command and gave no errors but still swat says that