search for: samba2.0.7

Displaying 18 results from an estimated 18 matches for "samba2.0.7".

2001 Feb 23
1
Printing with samba2.0.7
Hi all, I've just install samba2.0.7 on server Tru64. We have one printer HP5Si and others HP4 on the network. Using Samba from our Win95 customer we can print correctly to HP4 but to our HP5si we have the file wanted and one blank page and one page indicated "@PJL RDYMSG DISPLAY=" " ". So we want to suppress these pages. Is there anyone who can help me ?
2001 Mar 15
0
Fwd: Re: win98-samba2.0.7 = Network collisions
looks like you sent this to the wrong person... ----- Forwarded message from JON GERDES <GERDESJ@gkn-whl.co.uk> ----- Envelope-to: mikef@mikef-linux-x86.matchmail.com Delivery-date: Thu, 15 Mar 2001 00:18:43 -0800 Date: Thu, 15 Mar 2001 08:17:40 +0000 From: "JON GERDES" <GERDESJ@gkn-whl.co.uk> To: <mfedyk@matchmail.com> Subject: Re: win98-samba2.0.7 = Network
2001 Mar 14
1
win98-samba2.0.7 = Network collisions
Hi, I have an Samba 2.0.7 Fileserver on my RedHat 7.0 Linuxbox Access to the shares with an Linuxclient - all works fine. When I use an Win98 or WIN ME client, I've got many network collisions. (Same file and share) Any ideas ? Thereis only one socket option set in my smb.conf: socket option = TCP_NODELAY Network = 100MBit/s Ethernet Changing of NICs,cables or Hub doesnt't resolve the
2001 Nov 24
1
win98printer+samba2.0.7
LaserjetHP4MP is connected to win98 machine "server". My goal is to print from Slackware7.1 machine using Samba. So far, I did: smbclient //server/"HP 4MP" -P ...password etc... smb> print /home/test.txt ...system annonuces printing but nothing really happens until another printing job is being sent from windows machine, printing my linux page as the first one. My
2001 Nov 30
4
NT_STATUS_ACCESS_DENIED??
I installed Samba2.0.7 on my FreeBSD 4.1 box and joined an NT domain. It worked perfect until I changed the hostname today. I found that I couldn't chage the machine password if hostname length is 15. The precedure I do is 1. stop samba 2. change hostname to "abcde1234567890" 3. run smbpasswd -j DOM -r DomControl, then I get the following error message. cli_net_auth2: Error
2000 May 09
1
Windows 2000 crashes
We used samba 2.0.6 under Redhat 6.1 with W98/NT4 clients without any problems. Now we upgraded one PC with Windows2000. In the beginning everything worked fine. But suddenly there are problems: Browsing a specific subdirectory of a share on the server cause a inmediate crash of W2k with a automatic restart. I upgraded to Samba2.0.7, again W2k crashes. I connect to this subdirectory from a
2002 May 09
1
Can't Apply Group ACL
Thanks Samba Team to support the ACL functionality. It is a very cool feature. I just replaced my Samba2.0.7 version to Samba2.2.4 and tried to test ACL function. User setting is perfect. But when I try to add a group from [Select Users, Computers, or Groups] dialog, and press [Ok]. It displays [Unable to lookup username for display]. Do I miss anything? Or current Samba version not support the
2002 Jul 31
2
wierd samba problems - NEED COMMENTS
am exhausted for solving this. using samba2.0.7 and 2.2.5 in 5000 nis/nis+ and win2k domain environment samba member server in domain giving access to nfs home directories everything working smooth since last 3 years lately couple of users unix home directory are not completely listed when seen from windows explorer via samba. permission on unix home direcotry are 755 ( i changed to 777 to
2000 Jul 21
12
SAMBA 2.0.7
Dear Samba team: I just download SAMBA 2.0.7 from http://samba.gorski.net/samba/ftp/Binary_Packages/redhat/ and I have already installed SAMBA 2.0.6 which come with my red head linux 6.2 CD. But the 2.0.7 SAMBA is conflict with SAMBA 2.0.6. and it will not allow me to install the latest version of SAMBA. It gives me error messages while I am trying to install samba2.0.7 "Conflicts
2000 May 04
0
SAMBA digest 2512 / 2.0.7: unsolicited oplock break reply
Giulio Orsero wrote: > I've used > oplocks = no > for a long time now, because of the famous "oplock_break" error, but I > decided to give 2.0.7 a try. > [ snip ..] > > - the server is linux 2.2.14/samba2.0.7; it's not the server where I > used to made oplock_break tests. It's another one on another lan. It's > used almost exclusively to store
2001 Apr 01
0
(no subject)
I have a pcwin3.11. I was mapping solaris 2.5 with samba2.0.5 fine. I added the solaris2.7 system with samba2.0.7 to this small lan. Actaully this solaris 2.7 box was another 2.5 box that I upgraded it. I ftped the smb.conf file from the solaris2.5 box to the solaris 2.7 box so that this way the two solaris systems match and that pcwin3.11 will work with both equally well. I even mated the
2001 Apr 08
0
File corruption when copying from samba to win2k
Hi, I've seen a few messages about this but no answers in the archive... I have a win2k machine & a Redhat7.0 machine running samba2.0.7. I recently had to re-install my win2k machine, so I backed up everything onto the samba machine (approx. 5Gb). When I copied the files back to the win2k machine after the re-install, some of the files turned out to be corrupted. There were no errors
2001 Dec 03
2
Incorrect password or unknown username
Dear ALL: I installed Samba2.0.7 on redhat6.2. First I chose the security = user, then I always could not pass test 8 or test 9 from win2000. The error message says either "access denied" or "Could not log int from the work station" while I am sure that the host allow parameter allows this computer. Also I set "encrypt passwords = yes" and created a smbpassword
2000 May 03
2
2.0.7: unsolicited oplock break reply
I've used oplocks = no for a long time now, because of the famous "oplock_break" error, but I decided to give 2.0.7 a try. I still get "oplock break" errors as before, but this time I got a new error too: [2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXX/xxxxxx/mailbox.pst
2003 Nov 07
13
File Locking
Hi, I'm running smbd 2.2.8. I'm a little green when it comes to file locking with samba. I have two users that access a single data file on a FreeBSD box. It's a moneydance data file and obviously it gets messed-up if two users are writing to it at the same time. Is there a way with samba to stop a second instance of the file from being opened, something like a "File In
2003 Oct 27
92
Help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 dragen@pbsi.org ?rta: | I am hacing trouble. I can see my linux box from my windows box, I can connect | and browse but I cant delete or modify files. Do I have something wrong? | | The is my smb.conf | | [global] | netbios name = dragenlinux | server string = "DragenLinux" | workgroup = WORKGROUP | security = share | log file =
2003 Dec 01
0
No subject
to see the logs to check. Andrew Bartlett Samba Build Farm Maintainer -- Andrew Bartlett abartlet@pcug.org.au abartlet@samba.org Return-Path: <gcarter@valinux.com> Delivered-To: samba@samba.org Received: from Eng.Auburn.EDU (dns.eng.auburn.edu [131.204.10.13]) by lists.samba.org (Postfix) with ESMTP id 48F454E77; Tue, 3 Jul 2001 06:56:24 -0700 (PDT) Received: from localhost
2003 Dec 01
0
No subject
<-----------------------------------------------------------------------> Changes to user passwords are captured by a special DLL, which traps and then stores the password changes in encrypted form in a private area. On each synchronization schedule, the synchronization service first examines the SAM file for changes, and then checks this private area for passwords to be synchronized. Once