search for: brucehohl

Hi, I have tried using a raw print queue with no drivers and printed from the windows end. Still Word or other app being printed from dies and no print request appears in the servers logs. Any more ideas? Cheers, Mark. -----Original Message----- From: brucehohl@access-4-free.com [mailto:brucehohl@access-4-free.com] Sent: 21 May 2004 10:27 To: samba@lists.samba.org Cc: mark.vodden@clearchannel.co.uk Subject: Re: [Samba] Printing to Samba/Cups from Windows kills windows application. From: Mark Vodden <mark.vodden@clearchannel.co.uk> To: samba@lists....

I've set up a test Samba PDC with a few test shares. From the first Windows PC I logged on to a local computer account and mapped drives to the shares on the Samba PDC. From the second Windows PC I joined the domain and used a logon script to connect to the shares. My question: What are the benefits of joining a Windows PC to the Samba domain? Both arrangements above appear to meet my

I am having an unusual bit of behavior with a recently upgraded 3.0.8 installation (from 3.0.2a). I upgraded the server and retained the secrets.tdb file. The server itself is using security = domain, and it had been joined to the domain prior to the upgrade. Now, once I started the new version, I couldn't log on, and would get the error "There are no logon servers available to service

Hi All, I have a strange problem with passwords, stored in LDAP. When i try to logon as a user with the correct password, access is denied and the log says check_ntlm_password: Authentication for user [administrator] -> [administrator] FAILED with error NT_STATUS_NO_SUCH_USER When i try to logon a user with incorrect password, access is (of course) denied, but the log now says

I have follow an example in "samba-3 by example book", where it explain how to relocate a samba server as ADS member domain, in a sentence it said to delete all /var/lib/samba/*tdb files, so "winbindd_cache.tdb" and "winbind_idmap.tdb" files but when I start the samba server again in ADS new domain something's wrong. Because it is not able to map the same UID and

Hello List, I run a few VMs via libvirt using '--sdl'. I would like to use qemu parameters -no-quit, -no-frame and -ctrl-grab with libvirt. Does libvirt support a way to use these qemu parameters? Does libvirt provide a way to add these options under <graphics/> in the domain.xml using 'virsh edit domain.xml'? My current <graphics/> is as follows: <graphics

I have upgraded to 3.0.8 from 3.0.4. Winbind now fails just after start. The following messages are written to /var/log/samba/log.winbindd: [2004/11/11 20:59:00, 1] nsswitch/winbindd.c:main(865) winbindd version 3.0.8-1.1.1-SUSE started. Copyright The Samba Team 2000-2004 [2004/11/11 20:59:00, 0] lib/fault.c:fault_report(36) ===============================================================

I just updated to samba-3.0.9 on suse 9.1. All packages from the suse ftp server were installed including the heimdal rpm updates. I am using "security=ads". The new smbd, nmbd and winbindd started OK but I ran into the following errors: filesrv1:~ # wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_INVALID_COMPUTER_NAME (0xc0000122) Could not check

I have Suse 9.1 + Samba 3.0.9 + winbind joined to a Windows 2000 AD domain "MyCompany". Yesterday for some unknown reason (appears to be Win2K issue) connections to Samba and the ability to browse the domain "MyCompany" from Win2K/XP workstations failed but connections to the public share offered by the Win2K server were OK. Also, all Win98 workstations and were unable to

I am looking for some documentation or instructions for setup and use of smbprngenpdf by Windows clients. Can anyone point me in the proper direction. Thanks.

I have a very small problem. Thanks for any suggestions. Say user1 logs onto a Windows XP workstation and opens file1. Then, if user2 attempts to open the file from another workstation the following message is displayed: "file1 is locked for editing by ''" Problem: *user1* is not displayed between the single quotes. However, say user1 logs onto a Win98 workstation and