similar to: Why 2 login failures before success?

Hi! Just today, I managed to attach my Win98 client at home to my remote network which is controlled by a Linux samba 2.0.5a server. The TCP/IP connection is working just fine, I'm able to access all services like ftp, telnet, ... The Win98 client is connected to the network using the DialUp-Network. The option "log on to remote network" is activated and as far as I can conclude

The Samba v2.0.4b doc says: share modes (S) These open modes are not directly supported by UNIX, so they are simulated using shared memory, or lock files if your UNIX doesn't support shared mem- ory (almost all do). Yet I have these files on my (RedHat v6.0 / kernel v2.2.10) system: # ls -l /var/lock/samba total 12 -rw-r--r-- 1 root root 1048576 Jul 8

linux 2.0.33, user level, encrypted pass, guest user ftp. map to guest = bad user All works fine. I needed to put a user with a null password in smbpasswd with "smbpasswd -n" so I added the parameter null passwords = yes Now all works as expected but samba does more logging: 1) Everytime a user logins with a right password it logs that the password is wrong, however the user can

I'm trying to get win9x clients to connect to a Samba 2.0.4b server on FreeBSD 3.2-STABLE. Some of these machines have Windows logins different from the Unix user on the server, and the smb.conf manpage suggests that the "share%username" hack should be used in this case. This seems to work fine on my old 1.9.18p8 server, but not on any of the newer ones. With debug level 5 I see

Item Subject: cc:Mail Text Hi Mike, I got almost the same problem as you when I was using 2.04b on HP-UX 10.20 machine. I can not map to \\servername\sharename to my hpux machine from Win95 successfully when the sharename is different from the client login name. But it's successful on my WinNT. I can not resolve this problem but have a

I'm running Samba v2.0.5a on a RedHat v6.0 system. This server provides SMB shares to Win98, OS/2 and Linux clients. Everything is running fine with the Win98 and OS/2 clients, but I have a few questions regarding Samba and Linux clients. 1. Is there a way for Linux systems to receive SMB messages? Something analogous to Windows' "WinPopup" or OS/2's "Network

Hello, all.. I'm running into some weird password problems with Samba 2.0.5a. Here's what I'm *trying* to do. I have several Linux & Sun boxes that I'd like to share their resources with various DOS/Win9x PCs. I don't want to have to maintain password files on each of the these. Currently, the Unix passwords are shared via NIS, with a SunOS box as the master. What I

When the Win9x and OS/2 machines on my LAN boot-up, they set the local time from the Samba (v2.0.4b) server. Is it possible to do the same thing on a Linux system? If so, how is it done? Yes, I know I can use rdate to accomplish the same goal, but I'm trying to restrict the accessible services on the server to the most minimal possible. Since I have to have Samba services anyways, I

Hello I have this problem with printing to a HP Laser Jet 4L set up on my linux box which is the local samba server for the intranet. I can only print as root or as a user admin user = thatuser. I need to be able to set a password for the printer and only those users to use the printer who know the password. Or a similar solution. As ordinary user Windows98 says:

I'm having a hell of a time mounting Samba shares under Linux. Both server and client are running kernel v 2.2.1x on otherwise RedHat v6.0 systems. The machine running the Samba (v2.0.5a) server is working great. Directories and printers are easily accessable from Win98 and OS/2. It's Linux as a SMB *client* that is giving me problems. I can easily mount shares from a command prompt

i changed ip to my server and then i cant connect anymore using _NT authentication this the error i got from the log file: [root@server samba]# tail -f log.luca [1999/08/27 19:07:05, 0] passdb/smbpassfile.c:trust_get_passwd(294) domain_client_validate: unable to read the machine account password for machine SERVER in domain SATORI. [1999/08/27 19:07:05, 1] smbd/password.c:pass_check_smb(528)

I've got a couple problems with Samba<-->OS/2 communications. First, though, here's my environment: Samba machine: Celeron/400 /w 256MB of RAM IDE hard disks 100Mbps 3Com NIC RedHat Linux v6.0 + all RH-released updates + kernel v2.2.13 Samba v2.0.6 filesystem: ext2, cache size: dynamic OS/2 machine: Pentium 3/550 /w 256MB of RAM SCSI hard disks 100Mbps 3Com

I've got a 5-disk CD-ROM changer that I'd like to access via Samba v2.0.4 on my Linux (RedHat v6.0) system. I already have Samba up and running well, but I haven't had to deal with the CD changer until now. The kicker, of course, is while there's 5 disks, there's only 1 read mechanism. That means that the accessing of any given disk may mean first selecting that disk to be

Using Samba v2.0.10 on a RedHat v7.1 box, I see that the Win98 clients on our network are making sporatic requests for user "nobody" (as shown below). Anyone know what's going on here? My network has both Linux and Win98 clients, but only the Win98 clients are showing this behavior. Both the Linux and Win98 clients access the same shared drives, but only the Win98 clients use

I recently sent the message below to this list, hoping I could get advise on improving Samba (v2.0.6) write performance from an OS/2 client (I got no responses). I subsequently ran the same tests from a Linux client using smbmount, also v2.0.6, and got the same results. The hardware config of the Linux client is the same as the OS/2 client below. Obviously, the problem is not

Hello, I want to set up my Samba-servers to use encrypted passwords (smbpasswd). First I enabled "Update Encrypted" to set the correct password and then I disabled "Update encrypted" and enabled "encrypted passwords". When I map up a share from the client everything is working ok, but in the log I have the following: [1999/11/09 21:37:10, 1] smbd/password.c:(532)

I've got a user here that is unable to connect to any of the Samba shares that are available -- in fact, she doesn't even get past the username / password validation step. The message that Samba puts into the logs is as follows : NT Password did not match ! Defaulting to Lanman To narrow down the problem, I logged onto her machine as myself (from the same domain also) and then got onto

Hello Samba, ???????, 30 ??????? 99, you wrote: sso> SAMBA Digest 2359 sso> For information on unsubscribing see http://lists.samba.org/ sso> Topics covered in this issue include: sso> 1) Re: Unix .TXT vs DOS .TXT files sso> by Gerry Creager N5JXS <gerry@cs.tamu.edu> sso> 2) Switching user share on NT and smbd spawning sso>

When an OS/2 or Win9x client logs into a (Linux) Samba v2.0.6 server the running smbd spawns a copy of itself. That second instance of smbd then handles all the shares for that client machine. In contrast, a Linux client which does multiple smbmounts (also Samba v2.0.6) will cause the server to spawn a copy of smbd for *each* smbmount mountpoint. This has the potential for using up a lot more

When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was told that configure could determine my operating system. LynxOS, for those that don't know, is a Unix-like RTOS. It comes with a binary version of Samba, but a) it's old and b) it's not built for encrypted passwords which means I can't access it from WinNT. Can anyone advise me on what it would take to build