Re: [Samba] Re: Specified network password is not correct

Every article I read says to drop port 445. If I do not, I get my log
file filled up with errors about getpeername failed.

Even with no firewall at all, I still get the password incorrect problem
so it seems to be not related. Any other ideas?

Thomas M. Skeren III wrote:

> Merle Reine wrote:
>
>> I had the firewall off but now turned it on.
>> I modified the firewall on the box and added the following:
>
>
> Why? Samba 3 listens for smb calls on 445.
>
>>
>>
>> iptables -I INPUT 1 -p tcp --dport 139 -j ACCEPT
>> iptables -I INPUT 1 -p tcp --dport 445 -j DROP (to stop the
>> getpeername failed error)
>> apparently XP tries to connect to port 445 first then port 139
>> causing errors.
>>
>>
>>
>> Now I am getting in /var/log/samba/smbd.log:
>>
>> [2005/10/26 14:17:49, 1]
>> smbd/sesssetup.c:reply_sesssetup_and_X_spnego(593)
>> Unknown packet in reply_sesssetup_and_X_spnego
>> [2005/10/26 14:17:55, 1]
>> smbd/sesssetup.c:reply_sesssetup_and_X_spnego(593)
>> Unknown packet in reply_sesssetup_and_X_spnego
>> [2005/10/26 14:18:19, 1]
>> smbd/sesssetup.c:reply_sesssetup_and_X_spnego(593)
>> Unknown packet in reply_sesssetup_and_X_spnego
>> [2005/10/26 14:18:24, 1]
>> smbd/sesssetup.c:reply_sesssetup_and_X_spnego(593)
>> Unknown packet in reply_sesssetup_and_X_spnego
>>
>>
>> In Windows, trying to connect now gives:
>>
>> Logon failure: unknown user name or bad password.
>>
>> As operator/operator is the correct user/pass, not sure what else is
>> going wrong.
>>
>> My previous setup on the 386 machine with samba 2.x serves 400 users
>> and has been working for years. Something must have changed in samba
>> 3.x. I tried to copy over the smb.conf from the 2.x machine but that
>> will not work either.
>>
>> Merle Reine wrote:
>>
>>> I am having trouble connecting to a Centos 4.1 machine. I have the
>>> following installed:
>>>
>>> samba-common-3.0.10-1.4E
>>> samba-3.0.10-1.4E.2
>>> samba-client-3.0.10-1.4E
>>> samba-swat-3.0.10-1.4E.2
>>>
>>> Currently running:
>>> smbd
>>> nmbd
>>> winbind
>>>
>>>
>>> My smb.conf is as follows:
>>>
>>> # Global parameters
>>> [global]
>>> preferred master = No
>>> domain master = No
>>> wins support = Yes
>>> encrypt passwords = yes
>>> remote announce = 192.168.1.255/soupx
>>> smb passwd file = /etc/samba/smbpasswd
>>>
>>>
>>> [homes]
>>> read only = No
>>>
>>> [test]
>>> comment = test share
>>> path = /u/sambausers
>>> valid users = operator
>>>
>>>
>>>
>>>
>>> I have one user in /etc/samba/smbpasswd:
>>> operator:11:8880F85FF03EAF3B944E2DF489A880E4:E337E 31AA4C614B2895AD684A51156DF:[U
>>> ]:LCT-435FE36C:
>>>
>>>
>>> I am in the process of switching an old 386 machine for a dual xeon
>>> machine. On the old 386, running:
>>> samba-2.2.5-10
>>> samba-common-2.2.5-10
>>> samba-client-2.2.5-10
>>> samba-swat-2.2.5-10
>>>
>>> I can connect to the 386 with any windows, linux, mac.
>>>
>>> When I try to connect to the new machine running samba 3.0.10 from
>>> unix, i connect fine:
>>>
>>> [root@soupx1 temp]# smbclient //soupx/test -W LINUX-SOUP -U operator
>>> added interface ip=192.168.1.208 bcast=192.168.1.255
>>> nmask=255.255.255.0
>>> Got a positive name query response from 192.168.1.9 ( 192.168.1.9 )
>>> Password:
>>> Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.10-1.4E.2]
>>> smb: \> dir
>>> . D 0 Mon Sep 26 15:27:14
>>> 2005
>>> .. D 0 Mon Oct 10 05:11:02
>>> 2005
>>> stores D 0 Sat Oct 22 06:02:08
>>> 2005
>>> npd D 0 Fri Jul 29 08:51:38
>>> 2005
>>> legal D 0 Tue Sep 23 15:22:20
>>> 2003
>>> .................................................. .................................................. .........
>>>
>>>
>>> When I try to connect from any windows machine, I get:
>>> net use z: \\soupx\test
>>> Enter the user name for 'soupx' : operator
>>> Enter the password for soupx:
>>> System error 86 has occured.
>>>
>>> The specified network password is not correct.
>>> .................................................. .................................................. .......
>>>
>>>
>>> I used smbpasswd -a operator and set the password (which works from
>>> a linux machine)
>>>
>>> In /var/log/samba/smbd.log I see:
>>>
>>> [2005/10/26 13:48:21, 1]
>>> smbd/sesssetup.c:reply_sesssetup_and_X_spnego(593)
>>> Unknown packet in reply_sesssetup_and_X_spnego
>>> [2005/10/26 13:48:28, 0] lib/util_sock.c:get_peer_addr(1000)
>>> getpeername failed. Error was Transport endpoint is not connected
>>> [2005/10/26 13:48:28, 0] lib/util_sock.c:read_socket_data(384)
>>> read_socket_data: recv failure for 4. Error = Connection reset by peer
>>> [2005/10/26 13:48:28, 1]
>>> smbd/sesssetup.c:reply_sesssetup_and_X_spnego(593)
>>> Unknown packet in reply_sesssetup_and_X_spnego
>>>
>>> I can connect to a public share on this machine without a password.
>>>
>>> Any idea what is wrong?
>>>
>>>
>>>
>>>
>
>
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba