similar to: smbclient does not wok if encrypted passwords is true.

I recently reinstalled Linux on my fileserver (RedHat 7.2), which was running Samba (v 2.2.1a). Now, trying to reconfigure Samba back to its original state (silly me didn't keep a copy of the conf file) I've run into a problem. My win98 machines can't find the Samba server by name, but they can by number. By this I mean: On a Linux desktop, smbclient -L //marvin/ works as

Hi all, All Win98 & Win2k used to be able to connect, but as of last week only one Win2k is able to access the share folder, but not without a little issue. Another Win2k in the same subnet have intermittent connection issue and Win98 is not able to access the folder. Setup: Samba 2.2.2 install into Solaris8 in a subnet with two other Win2k server. This subnet is connect to a number of

Hi, I'm trying to connect to a share on a linux box from a win98 (or win2k) machine through an SSH tunnel. The documentation found on the subject says to setup an entry in LMHOSTS file in the form of: 127.0.0.1 sambaserver #pre checking the status of the cache with NBTSTAT -c after doing a NBTSTAT -R does not show the entry for "sambaserver" If I put any other

I have an NT Network and as one of the first steps in eliminating NT from my shop I need to be able to mount some of my NT shares on my Linux boxes. When I execute: smbmount //NTXX/ShareName /NTShare it asks me for a password. I enter the correct password (yes I've checked my capslock key and made sure I typed it correctly) but I get the following error. 10819: session setup failed:

Note: LMB = Local Master Browser DMB = Domain Master Browser Have Samba 2.2.7A running embedded in a variant of ucLinux. My interest was only to use Samba as a WINS server. I've set up the SMB.CONF with this config. for one test: wins support = yes local master = no domain master = yes preferred master = no os level = 0 I've set up the SMB.CONF with this config. for the other

All - Client: Win98, first version Server: Linux Mandrake, Samba 2.0.7 I'm trying to setup a Samba server to replace a customer's evil Windows 98 server, and have run into a problem. When used with encrypted passwords, it doesn't work. I tried all of the usual cures, and found that it worked perfectly if I enabled plaintext passwords in Win98. When I switched back to encrypted

I am trying to use Samba between a RedHat Linux 9 system and several Win98 PC's. From the Win98 systems, I can see and access the Linux folders I have made available. I can see the Win98 PCs and their shared directories from the Linux box. Understanding that Win98 requires encrypted passwords, I have set the "encrypt passwords" keyword in the smb.conf file to "yes".

Hi all I've a samba server listen on eth0 (everything ok) and eth2 server1 has eth2: 192.168.100.212 <--> 192.168.100.213 (another linux server) with another interface 192.168.30.0/24 from network 192.168.30.0/24 I can ping 192.168.100.212 and works with samba shares (but only using numeric IP) I don't see any computers from windows machines. nbtstat doesn't find any host

I have just speant several hours trying to nut out an error with a new installation of SAMBA 3, and the results may indicate something has changed with the way the Name Server (nmbd) responds to certain request. It could also be network stack related, but I am about at my limit of skills to diagnose it any further. I have just installed Fedora Core 1 to a test server in order to play around

I have a mixed network of Win95, Win98 and Unix machines. I am using Samba very happily. I would like to add a Windows NT 4.0 and Windows 2000 client machine to the network, but don't know how to turn off the password encryption. I am currently editing the registry on the Win98 machines. If someone can tell me how to edit the NT 4.0 and Win2000 registry I would appreciate it. Thanks, Dan

Hello, yesterday I've changed my password system to encrypted password because somebody wanted to log in with win98 notebook. And I wanted not to make the change in registry of the notebook. Therefore I set encrypted password = Yes, added and enabled the user with smbpasswd -a -e <account>. After this change he can log in via dhcp in our network. But in the next morning I've

Greetings, I am running samba 2.2.5 win RedHat 8.0 Linux machine Windows 2000 machine has fixed IP 192.168.0.40 Windows XP machine has fixed IP 192.168.0.30 Linux machine has fixed IP 192.168.0.1 on eth0 (local network NIC) and dynamic IP on eth1 (NIC connected to ADSL modem). I can ping 192.168.0.1 ( linux machine) from all machines I can ping 192.168.0.40 ( windows 2000 machine) from all

My LAN is running Samba v1.9.18p10 under RedHat Linux v5.2. Using the SMB services are Win95 and OS/2 clients. It's all running fine. I will soon be adding Win98, though, and I understand that there is a question of password encryption. I'm concerned how the encrypted/plain-text communication of password will affect my existing configuration. If I reconfigure Samba to use encrypted

On Wed, 3 Aug 2016 18:41:53 +0200 "Pol Hallen" <samb at fuckaround.org> wrote: > Hi all > > I've a samba server listen on eth0 (everything ok) and eth2 > > server1 has eth2: 192.168.100.212 <--> 192.168.100.213 (another linux > server) with another interface 192.168.30.0/24 > > from network 192.168.30.0/24 I can ping 192.168.100.212 and works

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

I have just entered the wonderful world of windows filesharing at my small home LAN and I'm experiencing the following problem: When I continually listen to ogg files in Windows 2000 Server from a samba server the music locks up every 15 minutes or so. Everything in the windows gui suffers from terrible preformance until i get to disconnect the share from the samba server, then everything

I use Samba 3.14.17 and later test Samba 3.6.9. The computer is WINs server on Samba. wins support = yes All work good. But now I see that NetBIOS clients cannot to re-register their names on WINs, when he change IP. >From WinXP SP3 I do nbtstat -RR Answer: NetBIOS-names registered by this computer were changed. >From server: relay2# nmblookup -U 10.0.0.1 -R -S aiy querying aiy on

> > > Adding pdc1 to the hosts file (c:\windows\system32\drivers\etc\hosts) > did > not make a difference. After adding pdc1 to lmhosts, "net use > \\pdc1" did > work. So in the case of pdc1 one, the name is being resolved as a > netbios > name (i.e. via lmhosts) not a tcp/ip type name (i.e. via dns or hosts) > > But then why does "net

we have been trying to move our samba box to a faster server, with better NICs, faster processor and more memory. both the old and new server are using samba 3.0.14A both on debian based distributions (old was sarge, new is breezy) here are the steps we followed: install samba from the apt archives. confermed that they were the same version. copied smb.conf from old server to new server. changed

network B, I can see the TCP session established, the challenge and response negotiation, the Tree Connect AndX Request and Response, the LANMAN server enumeration exchange, and orderly shutdown. When using the same client to browse the Samba domain on network C, I can see the TCP session established, the challenge and response negotiation, the Tree Connect AndX Request and Response, but then the