[Samba] Difference between samba 3.0.10 and 3.0.9 - resolution
Margaret Doll
Margaret_Doll at brown.edu
Tue Sep 12 15:26:27 GMT 2006
The problem was in the version of 3.0.10 that I was running. An
upgrade to 3.0.10-1.4E.9 solved the problem.
I was originally running E2.
On Sep 12, 2006, at 10:21 AM, Margaret Doll wrote:
> Another indication of the problem is that when I use
>
> smbclient -L SERVERNAME -N -d 3
>
> on the 3.0.9 system, I get a line
>
> resolve_hosts: Attempting host lookup for name SERVERNAME<0x20>
>
> prior to the login.
>
> I do not get this line in 3.0.10
>
> Why is 3.0.10 not attempting to resolve hosts?
>
>
> On Sep 11, 2006, at 4:02 PM, Margaret Doll wrote:
>
>> I upgraded one of my samba servers. I am using the same smb.conf
>> file that work on samba 3.0.9, but the "new" server is not
>> announcing itself.
>>
>> From the network neighborhood, across a subnet, I do not see
>> SERVERNAME listed under the workgroup DEPT.
>>
>>
>> I have disabled selinux. I have the same iptables enabled on
>> this system as on the prior system and another system still
>> running samba 3.0.9.
>>
>> smbclient -L SERVERNAME -N
>> ...
>> ...
>> Server Comment
>> -------- --------------
>> SERVERNAME Server for the dept.
>>
>> Workgroup Master
>> --------------- ------------
>> DEPT
>>
>>
>> In /var/samba/nmbd.log there is a line after SERVERNAME has
>> become the logon server
>>
>> nmbd/nmbd_logonames.c:become_logon_server_success(124)
>> become_logon_server_success: Samba is now a logon server for
>> workgroup DEPT on subnet 128.148.nnn.nnn
>> ***glibc detected *** free(): invalid next size (fast):
>> 0x090874c8 ***
>>
>>
>> Port 515 is open on the 3.0.9 system although it is not listed
>> in iptables.
>> Port 515 is not open on the 3.0.10 system.
>>
>> Any ideas on how to debug the problem?
>>
>>
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/listinfo/samba
>
More information about the samba
mailing list