The other question is what are Windows XP and KDE network browsing doing
differently than
Gnome? Windows XP and KDE are not affected by this issue at all. Until I
figured out the order
change, I used smb4k without any problems
When you access \\NAME on a non-AD, non-WINS-enabled Windows,
I acknowledge this is an issue but it's a difficult decision. Putting bcast
before host by default slows down SMB host resolution for everyone, in order
to make it usable for those using broken ad-crippled DNS...
On the other hand, this is generating a constant flow of Nautilus/samba bugs.
**
Is there any way to detect that DNS redirection is taking place other
than the long delay in getting the gui to display? Or, you could just
use a time-out that after a certain amount of time or a failure to
detect the network correctly a suggestion pops up that DNS redirection
is/may be taking
On Wed, Jul 01, 2009 at 03:50:16PM -, Martin G Miller wrote:
Admittedly, my networks are very small, so perhaps on a network with
dozens or hundreds of machines, the resolve order makes a difference,
but in my case with only 6 machines or so, it seems to have no negative
affects at all.
Given a way to detect broken DNS at package install time, it might be
reasonable to set name resolve order to broadcast first
at that point, if such brokenness is detected. A comment line indicating that
resolve order was set like this because DNS brokenness was detected at
date/time could
** Package changed: nautilus (Ubuntu) = samba (Ubuntu)
--
Nautilus can't browse local network if ISP uses DNS redirection
https://bugs.launchpad.net/bugs/389909
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Thank you for bringing this bug to our attention. Unfortunately a paper
cut should be a small usability issue that affects many people and is
quick and easy to fix. I'm afraid this bug can't be addressed as part of
this project.
Though the fix is simple. This is Bug does not affect the majority
