[Pkg-samba-maint] Bug#654701: Bug#654701: cifs-utils: Windows share cannot be mounted anymore after dist-upgrade on wheezy (5.1 -> 5.2)

[Didier Trosset]

On 01/05/2012 09:48 PM, Luk Claes wrote:
> On 01/05/2012 11:43 AM, Didier Trosset wrote:
>
>> I have been mounting a Windows share for years. Since I 'apt-get dist-upgrade' my
>> Debian 'wheezy' testing yesterday (Wed Jan 4th 2012), I cannot mount it
>> anymore. This upgrade brings in cifs-utils version 5.2.
>>
>> The share used to be mounted automatically being is /etc/fstab using a
>> credential file. This does not work anymore. But I aslo tried to mount it
>> manually calling mount, and mount.cifs using interactive password prompts, and
>> even trying smbclient without success.
>
> smbclient and cifs-utils are using very different approaches, so if it
> fails for both, it's very probably a bug somewhere else.
>
>> The error returned by mount.cifs is:
>>
>>      mount error(115): Operation now in progress
>>      Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
>
>> I have another Debian 'wheezy' testing system that I did not 'apt-get
>> dist-upgrade'. This system can mount the same Windows share. This latter
>> is still using cifs-utils 5.1.
>
> Ok, so it's not  problem at the Windows side.
>
>> I had a look at the changelog for the 5.2 release, but it did not trigger
>> anything meaningfull for me.
>
> I guess next is looking bottom up a.k.a. can you ping the Windows server
> from the host failing to access the share? Is the traffic not filtered
> in between? If those are not the problem a network capture via wireshark
> might be useful to debug it further.

Yes I can ping the server. There's no traffic filter, and on top of 
this, both systems accessing the server are on the same switch and subnet.

Following your good advice, I started wireshark, and discovered that the 
DNS searched was not correct! Indeed, during the upgrade, I was proposed 
to enter missing domain DNS information for my system. A made a typo. It 
looks that it's what blocked the cifs mounting.

What I don't explain is why using directly the IP address in the mount 
command did not work if it was only a DNS domain name error?

Anyway, you can close the issue, with my apologies.

Thanks for your time.
Best regards
Didier

>
> Cheers
>
> Luk