xp/2003 explorer freezes browsing shares on Samba 3.2 ipv6 hosts

[Pim Zandbergen]

After upgrading one of our servers from Fedora 7 to Fedora 9,
from Samba 3.0 to 3.2.0-2.17.fc9 I noticed this strange phenomena:

Windows 2003 and XP clients freeze when you type
"\\server" in an explorer address bar where "server" is the
name of the Samba 3.2 host.

Windows 2000 clients don't freeze.

2003/XP clients don't freeze when you enter "\\server\share"

They un-freeze if you restart samba, showing all the shares.
Refreshing freezes them again.

Here are some details on our network
- all samba 3.0 and 3.2 hosts are ipv6 capable
- some Windows clients are ipv6 capable
- DNS hostnames resolve to both ipv4 and ipv6 addresses
- NetBIOS over TCP is disabled, nmbd not running
- all samba servers are ADS clients in a 2003 domain

Here are some findings:
- it does not matter whether clients are ipv6 capable or not
- removing AAAA records for samba hosts does not help
- re-enabling NetBIOS over TCP does not help
- disabling ipv6 on the samba host does fix the problem

Disabling ipv6 on the host was not easy. I had to
prevent the ipv6 module from being loaded.

Has anyone else seen this behaviour?

Thanks,
Pim


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Jeremy Allison]

On Tue, Jul 15, 2008 at 10:39:21PM +0200, Pim Zandbergen wrote:

> After upgrading one of our servers from Fedora 7 to Fedora 9,
> from Samba 3.0 to 3.2.0-2.17.fc9 I noticed this strange phenomena:
>
> Windows 2003 and XP clients freeze when you type
> "\\server" in an explorer address bar where "server" is the
> name of the Samba 3.2 host.
>
> Windows 2000 clients don't freeze.
>
> 2003/XP clients don't freeze when you enter "\\server\share"
>
> They un-freeze if you restart samba, showing all the shares.
> Refreshing freezes them again.
>
> Here are some details on our network
> - all samba 3.0 and 3.2 hosts are ipv6 capable
> - some Windows clients are ipv6 capable
> - DNS hostnames resolve to both ipv4 and ipv6 addresses
> - NetBIOS over TCP is disabled, nmbd not running
> - all samba servers are ADS clients in a 2003 domain
>
> Here are some findings:
> - it does not matter whether clients are ipv6 capable or not
> - removing AAAA records for samba hosts does not help
> - re-enabling NetBIOS over TCP does not help
> - disabling ipv6 on the samba host does fix the problem
>
> Disabling ipv6 on the host was not easy. I had to
> prevent the ipv6 module from being loaded.
>
> Has anyone else seen this behaviour?

Can you get a network capture log of this behaviour
please and log a bug report at bugzilla.samba.org
and attach the trace.

Thanks,

Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Jeremy Allison]

On Tue, Jul 15, 2008 at 10:39:21PM +0200, Pim Zandbergen wrote:

> After upgrading one of our servers from Fedora 7 to Fedora 9,
> from Samba 3.0 to 3.2.0-2.17.fc9 I noticed this strange phenomena:
>
> Windows 2003 and XP clients freeze when you type
> "\\server" in an explorer address bar where "server" is the
> name of the Samba 3.2 host.
>
> Windows 2000 clients don't freeze.
>
> 2003/XP clients don't freeze when you enter "\\server\share"
>
> They un-freeze if you restart samba, showing all the shares.
> Refreshing freezes them again.
>
> Here are some details on our network
> - all samba 3.0 and 3.2 hosts are ipv6 capable
> - some Windows clients are ipv6 capable
> - DNS hostnames resolve to both ipv4 and ipv6 addresses
> - NetBIOS over TCP is disabled, nmbd not running
> - all samba servers are ADS clients in a 2003 domain
>
> Here are some findings:
> - it does not matter whether clients are ipv6 capable or not
> - removing AAAA records for samba hosts does not help
> - re-enabling NetBIOS over TCP does not help
> - disabling ipv6 on the samba host does fix the problem
>
> Disabling ipv6 on the host was not easy. I had to
> prevent the ipv6 module from being loaded.
>
> Has anyone else seen this behaviour?

No, IPv6 was tested by Dr. David Holder on Windows
platforms vs. Samba on Linux and FreeBSD. Not sure
what distro's though.

Can you get a debug level 10 log from smbd on
the server when IPv6 is enabled against a client
that freezes. Also an IPv6 network capture would
help.

Thanks,

        Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[David Holder-2]

Jeremy,

We tested Fedora including 7 and 8.

I'll take a look at the network trace too. Name resolution is an area
which can be problematic in mixed networks.

Pim, please could you send a copy of your /etc/resolv.conf?

Regards,
David
------------------------------------------------------------------------
Dr David Holder CEng FIET MIEEE

Erion Ltd, Oakleigh, Upper Sutherland Road, Halifax, HX3 8NT

Reception: [phone]

Direct Dial: [phone]

Cell: [phone]

Registered in England and Wales. Registered Number 3521142
VAT Number: GB 698 3633 78




Jeremy Allison wrote:

> On Tue, Jul 15, 2008 at 10:39:21PM +0200, Pim Zandbergen wrote:
>  
>> After upgrading one of our servers from Fedora 7 to Fedora 9,
>> from Samba 3.0 to 3.2.0-2.17.fc9 I noticed this strange phenomena:
>>
>> Windows 2003 and XP clients freeze when you type
>> "\\server" in an explorer address bar where "server" is the
>> name of the Samba 3.2 host.
>>
>> Windows 2000 clients don't freeze.
>>
>> 2003/XP clients don't freeze when you enter "\\server\share"
>>
>> They un-freeze if you restart samba, showing all the shares.
>> Refreshing freezes them again.
>>
>> Here are some details on our network
>> - all samba 3.0 and 3.2 hosts are ipv6 capable
>> - some Windows clients are ipv6 capable
>> - DNS hostnames resolve to both ipv4 and ipv6 addresses
>> - NetBIOS over TCP is disabled, nmbd not running
>> - all samba servers are ADS clients in a 2003 domain
>>
>> Here are some findings:
>> - it does not matter whether clients are ipv6 capable or not
>> - removing AAAA records for samba hosts does not help
>> - re-enabling NetBIOS over TCP does not help
>> - disabling ipv6 on the samba host does fix the problem
>>
>> Disabling ipv6 on the host was not easy. I had to
>> prevent the ipv6 module from being loaded.
>>
>> Has anyone else seen this behaviour?
>>    
>
> No, IPv6 was tested by Dr. David Holder on Windows
> platforms vs. Samba on Linux and FreeBSD. Not sure
> what distro's though.
>
> Can you get a debug level 10 log from smbd on
> the server when IPv6 is enabled against a client
> that freezes. Also an IPv6 network capture would
> help.
>
> Thanks,
>
> Jeremy.
>  

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Pim Zandbergen]

Jeremy Allison wrote:
> No, IPv6 was tested by Dr. David Holder on Windows
> platforms vs. Samba on Linux and FreeBSD. Not sure
> what distro's though.
>
> Can you get a debug level 10 log from smbd on
> the server when IPv6 is enabled against a client
> that freezes.
Just entered a bug on bugzilla with a level 10 log and a
wireshark capture from the XP client.
> Also an IPv6 network capture would help.
>  
The wireshark capture was run on a non-ipv6 capable client.
Do you want me to repeat it for an ipv6 capable client?

I doubt there is difference, as there seems to be no
ipv6 smb traffic at all, just ipv6 ldap traffic.

What I do see is that smbd handles ipv4 smb connections on ipv6 sockets.
I know a lot of other ipv6 capable applications use ipv4 sockets for ipv4
connections, supposedly because of problems using ipv6 sockets for
everything, particularly on Linux.

Thanks,
Pim

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[raoulduke]

I'm not sure if this is the same problem I have. In my case I could track the problem down to my printer shares. If I disable the [printers] and [print$] shares in smb.conf everthing works just fine. With the printers enabled explorer freezes on some systems when I'm logged in as a domain user and try to browse the shares on my PDC.

Strangely that problem does not occur if I'm logged into a local account on the client (like Administrator).

David.