On Oct 7 2009 16:57, Adam Tauno Williams wrote:

Date: Wed, 07 Oct 2009 16:57:15 -0400 From: Adam Tauno Williams To: Subject: Re: [opensuse] Windows 98SE can't access Samba openSUSE 11.1

...

since I updated from openSUSE 10.3 to 11.1 I cannot acces my samba shares with Windows 98 SE anymore. Windows NT based Systems work as before. Windows prompts for a password, but the valid smb password is rejected. enabling/disabling plain passwords or encrypted passwords on both sides doesn't change anything. No log entries in samba's logfiles. Using samba-3.2.7-11.3.2.

Older auth mechs (such as LANMAN) are disabled in recent versions of Samba [and recent versions of Windows for that matter]. You need to enable the appropriate legacy auth mech in smb.conf explicitly.

Possibly "lanman auth = yes" will do it.

It's weired... I tried some different settings, with following results: letting Windows send encrypted passwords, encrypted passwords enabled in smb.conf (with ntlm auth/lanman auth or only one of both...) leads to the mentioned error. disabling encrypted passwords in smb.conf makes windows say "invalid parameter" on connecting. turning password encryption off on both sides, it works! but i think with having password encryption disabled the windows NT style clients won't have acces anymore. Before the update the crypted way worked... I also increased the verbosity of the logs, some interesting lines could be: check_ntlm_password: sam authentication for user [XYZ] FAILED with error NT_STATUS_WRONG_PASSWORD check_ntlm_password: Authentication for user [XYZ] -> [XYZ] FAILED with error NT_STATUS_WRONG_PASSWORD the user is previously recognized. thanks four your help. Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, Oct 07, 2009 at 05:52:59PM -0500, David C. Rankin wrote: [ 8< ]

Adam hit the nail on the head. The lanman auth parameter is what you need. You will also want to upgrade samba. There were a few releases that had bugs with that setting after it was disabled by default.

http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_11...

The general Samba page in the openSUSE wiki points to the STABLE and TESTING repositories. See http://en.openSUSE.org/Samba for more general Samba on openSUSE information and the section "openSUSE Build Service" about how to get recent builds for openSUSE, SUSE Linux Enterprise and even some more Linux based systems. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

On Saturday 10 October 2009 04:00:15 pm you wrote:

...

...

...

Possibly "lanman auth = yes" will do it.

It's weired... I tried some different settings, with following results: letting Windows send encrypted passwords, encrypted passwords enabled in smb.conf (with ntlm auth/lanman auth or only one of both...) leads to the mentioned error. disabling encrypted passwords in smb.conf makes windows say "invalid parameter" on connecting. turning password encryption off on both sides, it works! but i think with having password encryption disabled the windows NT style clients won't have acces anymore. Before the update the crypted way worked... I also increased the verbosity of the logs, some interesting lines could be: check_ntlm_password: sam authentication for user [XYZ] FAILED with error NT_STATUS_WRONG_PASSWORD check_ntlm_password: Authentication for user [XYZ] -> [XYZ] FAILED with error NT_STATUS_WRONG_PASSWORD the user is previously recognized.

Adam hit the nail on the head. The lanman auth parameter is what you need. You will also want to upgrade samba. There were a few releases that had bugs with that setting after it was disabled by default.

http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_ 11.1/

Thanks for the fast help. I just upgraded to the latest Samba Version samba-3.4.2-1.1 (also updated all corresponding packages). No problems with the Windows NT as before. But Windows 98SE doesn't even find the server anymore in the network neighborhood. Even accessing by \\IP doesn't work. Getting following error on connecting of network devices: The following error occured while reconnecting [...] Permanent connection not available. I set the samba logs to max verbosity but getting no entry at all. No firewall is blocking the network interface. Here the global part of my smb.conf: # smb.conf is the main Samba configuration file. You find a full commented # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the # samba-doc package is installed. # Date: 2006-11-27 [global] workgroup = PANE printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = Yes domain master = Yes netbios name = PANE security = user passdb backend = smbpasswd:/etc/smbpasswd local master = Yes os level = 65 preferred master = Yes wins support = Yes encrypt passwords = Yes lanman auth = Yes ntlm auth = Yes log level = all:10

Thanks for further assistance, Paul

Paul, here is the global and homes for my old smb.conf I used with win95 and win98 for years (change the 'changeME' entries and the IPs): [global] use sendfile = No workgroup = changeME server string = Samba %v printcap name = cups load printers = yes printing = cups show add printer wizard = no disable spoolss = yes log file = /var/log/samba/log.%m max log size = 100 time server = yes hosts allow = 127. 192.168.7. map to guest = bad user security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 69 domain master = yes preferred master = yes name resolve order = wins lmhosts bcast wins support = yes dns proxy = no [homes] comment = Home Directories browseable = no writable = yes -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2009-10-08 at 00:18 +0200, Paul Neuwirth wrote:

...

Date: Wed, 07 Oct 2009 16:57:15 -0400 From: Adam Tauno Williams To: Subject: Re: [opensuse] Windows 98SE can't access Samba openSUSE 11.

...

since I updated from openSUSE 10.3 to 11.1 I cannot acces my samba shares with Windows 98 SE anymore. Windows NT based Systems work as before. Windows prompts for a password, but the valid smb password is rejected. enabling/disabling plain passwords or encrypted passwords on both sides doesn't change anything. No log entries in samba's logfiles. Using samba-3.2.7-11.3.2. Older auth mechs (such as LANMAN) are disabled in recent versions of Samba [and recent versions of Windows for that matter]. You need to enable the appropriate legacy auth mech in smb.conf explicitly. Possibly "lanman auth = yes" will do it. It's weired... I tried some different settings, with following results: letting Windows send encrypted passwords, encrypted passwords enabled in smb.conf (with ntlm auth/lanman auth or only one of both...) leads to

On Oct 7 2009 16:57, Adam Tauno Williams wrote: the mentioned error. disabling encrypted passwords in smb.conf makes windows say "invalid parameter" on connecting. turning password encryption off on both sides, it works!

Encrypted passwords should certainly work with Windows 98. I assume you have a SAM setup so that encrypted passwords can work - tdbsam, ldap, etc...

but i think with having password encryption disabled the windows NT style clients won't have acces anymore.

Correct.

Before the update the crypted way worked... I also increased the verbosity of the logs, some interesting lines could be: check_ntlm_password: sam authentication for user [XYZ] FAILED with error NT_STATUS_WRONG_PASSWORD check_ntlm_password: Authentication for user [XYZ] -> [XYZ] FAILED with error NT_STATUS_WRONG_PASSWORD the user is previously recognized.

Is this debug level 10? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Cristian Rodríguez wrote:

On 07/10/09 16:54, Paul Neuwirth wrote:

...

with Windows 98 SE anymore.

Nobody supports that thing anymore, looks like you need to move to the 21 century...

Actually, its pretty light weight, i.e. fast (not hoggish). As long as you run an AV tool, and browse with an up to date Firefox, your pretty safe. JF -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

phanisvara das wrote:

On Thursday 08 October 2009 07:04:28 am Jim Flanagan wrote:

...

Actually, its pretty light weight, i.e. fast (not hoggish). As long as you run an AV tool, and browse with an up to date Firefox, your pretty safe.

but the AV thing has to include a firewall, which many didn't. when i was using win 98, i found a firewall more important than the AV.

With Windows, you should use an external firewall, rather than trusting any software firewall. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, 2009-10-07 at 20:34 -0500, Jim Flanagan wrote:

Cristian Rodríguez wrote:

...

On 07/10/09 16:54, Paul Neuwirth wrote:

...

with Windows 98 SE anymore. Nobody supports that thing anymore, looks like you need to move to the 21 century... Actually, its pretty light weight, i.e. fast (not hoggish). As long as you run an AV tool, and browse with an up to date Firefox, your pretty safe.

Nah, I've run Windows for years with no AV at all. It all depends on how you use the machine. If all services are disabled and you never run IE or Outlook your exposed surface is pretty small; you certainly shouldn't use such a configuration for sensitive functions but for many uses I wouldn't worry about it. In my experience, if you are plowing through unknown Internet sites and clicking every link you see then no amount of preventative is going to save your machine. And many times there simply is no choice. We have a million dollars worth of VOIP PBX systems.... that can only be administered using Windows 9x running a specific version of IE6 hosting a specific version of the Microsoft JVM. Ugh. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, Oct 9, 2009 at 9:15 AM, Andrew Joakimsen wrote:

Yes but try to find an AV software for Windows 98... even Firefox is no longer supported for anything under Windows 2000.

http://www.avast.com/eng/system-requirements-avast-home.html 95/98/ME 486 with 32MB RAM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org