similar to: A question ...

Hi. I have a samba server with 3000 users. I want to install another little server with a printer and I want to give access only to a group of users from the main server. [ MAIN ] [SAMBA-SERVER] | | | [little]-printer a group of users from MAIN can print [server] to this server Someone can give me a hint of how can I achieve this easily ? What document should I read ?

Hello, Kenny Cho wrote: >I've been successful using v,1.9.18a but not 2.0.4b, I believe it's because I >ended up downloading the binaries that doesn't have the shadow password support. >So my other question is how do I know if the smb binaries that I download has >that support? This may come across more bitter than I intend it to be. So please take this with a grain

I have a question about Win98 and Samba. Is there a registry fix similar to the WinNT plaintext passwd that needs to be performed? Win95, and WinNT can see Linux via Netbios, but the same machine, running Win98 cannot see the Linux box. I am running the most current version of Samba. The WinNT box can see the 98 machine fine. Does anyone have any experience with this? Please let me know if

Hello! I know that this is not samba related, but may be some one knows a quick answer: When using profiles, stored on a well running samba-2.0.0beta2 PDC, the NT PC's cache the profile during a user session. As this profile is not deleted on the PC and we have a lot of users with only few PC's we need a lot of diskspace for this old profiles. Is there a way (Registry Key, ..) that

I've been working on a package for openssh to include in the NetBSD package system (similar to the FreeBSD ports system). I'm being hindered in this by the fact that updates to these packages can be extremely slow (2-3 days minimum, more like 2 weeks including testing), too slow to compensate for the fact that the tarfiles for back-level versions of openssh-1.2pre* are going away. Given

Hi, If there is a place to post this, please advise, but I am stuck. I have recently installed openssh-1.2.3 on a Red Hat 6.1 installation. Everything compile ok but I don't get no password auththenticcation. So I recompiled openssh-1.2.3 without PAM support and it still does not work. I can log into the system otherwise (shadow password is enabled). Here is what I have in my

Howdy, I'm installing openssh 2.2.0p1 on a number of SUNs running Solaris 2.6 but ran into a few problems: 1. whenever I run a remote X11 application and f.i. change the windowsize I get anoying debug messages like debug: client_check_window_change: changed This is a problem since I want to use openssh in a production environment. Is there any way to turn these messages off?

Does the same fix for windows 95 fix windows 98? Does anyone know for sure -------------------------------------------- You can tune a piano but you can't tuna fish - REO Speedwagon

i'm looking for an answer to the problem WIN98/samba-connection. It shows the same failure as shown by WinNT unless the change of Registry to EnablePlainPasswd. Is there an answer where the entry "EnablePlainPasswd" should be by WIN98? Enable encryoptedPasswd in smb.conf brought no solution. Thanks an many greetings Lothar M?hlbauer Lothar.Muehlbauer@iiv.de

Does anyone Know the procedure for Windows 2000 workstation, in order to not encrypt passwords. What I needed is something similar to the transcription I make below that works for windows nt4 and 98. Thank's Emanuel Duarte (Portugal) ********************************** This should take care of the "clear text password" problemsyou've encountered: For Win 98 (To enable

Hallo Liste Derzeit mache ich meine ersten Gehversuche mit Linux (SuSE). Bis jetzt habe ich in einem kleinen Netzwerk f?r meine Tauchschule vier Rechner betreut. Einer davon war WinNT-4.0 Server und Arbeitsplatz zugleich. Nachdem ich nicht mehr bereit bin, mich mit dem w?chentlichen "blue screen" und dem monatlichen Neuinstallieren von NT abzufinden, bin ich derzeit beim Umsteigen auf

I can only conclude that Samba is an elaborate hoax and here's why. 1) Setup is more complex than Sendmail (it set the standard for complexity) 2) Even the simplest smb.conf causes trouble 3) You can pass ALL the tests in the DIAGNOSIS procedure, AND Samba will still not let you SHARE FILES or SHARE PRINTERS between Windows and Unix but you WILL be able to BROWSE YOUR SHARES (Just pretend

I have Samba 2.25 on a Redhat 8.0 box. My Id's and passwords work fine on a Windows 2000 or XP machine. I cannot get them to logon from a Windows 98 machine. Any Ideas????? THANKS --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.422 / Virus Database: 237 - Release Date: 11/20/2002 -------------- next part --------------

Hi! I'm new on the list, so please, be patient with me! I have a problem for wich I can't find the answer in the FAQ. Until recently I was running a 16 PC-s network with SCO OpenServer 5.0.4 and Samba 1.9.16p11 on the server and mixed clients (Win 3.11 to Win 95 OSR2). The users on the network have access to a PUBLIC directory on they own user directories on the server without

Greetings All, I have tried everything I can think of and can not seem to stop the PC from cacheing a local copy of a file retrieved over a samba share. I have tried oplocks = false and also setting veto oplocks = /*.txt/ Whatever I try the PC still shows me the old version of a file after I modify it on the unix side. If anyone can see anything wrong with my smb.conf file please let me know.

Hi, Im trying to compile samba-2.2.8a on BSDi... Here is the output from uname: 4.1 BSDI BSD/OS 4.1 Kernel #0 Upon compilation using both make and gmake I get the following: Using LIBS = -ldl Linking bin/smbd lib/snprintf.o: In function `vasprintf': lib/snprintf.o(.text+0x14): undefined reference to `VA_COPY' lib/snprintf.o(.text+0x45): undefined reference to `VA_COPY' *** Error

http://bugzilla.mindrot.org/show_bug.cgi?id=674 Summary: permanently_set_uid() doesn't work on BSDI 4.0.1 Product: Portable OpenSSH Version: 3.7p1 Platform: ix86 OS/Version: BSDI Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

Hello Sir, Please find the attached smb.conf with mail. I have configured the smb.conf file but having problems in connection from Windows98 machines but where as it works well with Windows NT 4.0. If I change security = share in smb.conf it will work with all the machines for both windows 98 & NT but there will be no security. I am using solaris 2.7 & our network is peer to peer

I found these articles that talk about the oplock_break problem (specifically they are related to problems with word97): http://support.microsoft.com/support/ntserver/serviceware/nts40/e9msge2bc.asp http://support.microsoft.com/support/kb/articles/q163/5/25.asp Basically they say: either apply sp3 on the winnt client or disable oplock on nt server But they don't say anything about win9x,

Gidday, I've just tried installing openssh-2.2.0p1 and found that it globbers my ssh_prng_cmds file which has been customised from the normally installed one. On BSDi 4.0.1 it doesn't detect enough commands for ssh-keygen to be happy. Most of the commands do actually exist, but I have to specify where they are. Could someone please modify the installation scripts to either backup this