Setting to Invalid in samba since it always boiled down to OpenDNS doing
resolution in a way that require some configuration for samba to work
with.
** Changed in: samba (Ubuntu)
Status: Confirmed = Invalid
--
Connect to smb server by name doesn't work, but by IP address does
The problem disappeared with Karmic Koala on my PC.
--
Connect to smb server by name doesn't work, but by IP address does
https://bugs.launchpad.net/bugs/235560
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
I had the same problem in Kubuntu. The problem was is that DNS was set
to resolve before WINS, meaning that openDNS jumped in, fooling the app
into thinking that was it. The fix was to move wins from the end of
line 11 in /etc/nsswitch.conf to after files. Then it worked fine, if
a little slowly.
Gabriel:
How is your problem related to this bug ? This bug is about being able to
connect by IP address, but never by server name. In your case, you can connect
once... then the connection dies somehow. Please open a separate bug to track
your issue.
--
Connect to smb server by name doesn't
Thank You for response. I was looking for my bug in launchpad, and picked
this thread because of the same error pop-up window. Sorry for confusion, I
try to open a new bug report.
2009/4/8 Thierry Carrez thierry.car...@ubuntu.com
Gabriel:
How is your problem related to this bug ? This bug is
Important notice: After reconnect via nautilus sidebar icon, the desktop
icon works too.
--
Connect to smb server by name doesn't work, but by IP address does
https://bugs.launchpad.net/bugs/235560
You received this bug notification because you are a member of Ubuntu
Server Team, which is
So I can reproduce the bug. Now I am sure, it has nothing related with
NAS box sleep mode. The first connection went good as always. The
desktop icon works. After couple of minutes (10-15), I try to reconnect.
1. The first error message appears (pic1 - Sorry for foreign language), it
says:
Confirming this bug on Jaunty Beta. The first connection is always
successfull, the shared folder icon appears on desktop and on nautilus
sidebar too. The error message pops up when I retry to connect the
shared folder couple of minutes (10-15) after. This happens with
retrying to connect via
** Tags removed: proposed-pkg
--
Connect to smb server by name doesn't work, but by IP address does
https://bugs.launchpad.net/bugs/235560
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing
** Changed in: samba (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
--
Connect to smb server by name doesn't work, but by IP address does
https://bugs.launchpad.net/bugs/235560
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I have a Hardy Heron machine that is trying to connect to a share on a
Gutsy machine and I get the same problem trying to connect to the share.
If I follow the instructions to remove 'wins' from nsswitch on both
sides (it was only originally on the Gutsy machine), enable the mdns4 on
both sides
Hello all,
I'm afraid I'm having the same problem.
I'm trying to connect to the Samba shares on a NAS-4220-B Icybox.
I keep getting Couldn't display smb://192.168.1.64/nikos/.. There is no
application installed for this file type messages.
I now realize this is a misleading message as it has
Thanks Steve, That's fixed it for me (Setting /etc/samba/smb.conf to:
name resolve order = lmhosts wins bcast host).
I had previously thought that adding the value wins in the line in
/etc/nsswitch.conf as suggested by va9rant had fixed it, and it had, but
it also stopped the network drives
Setting /etc/samba/smb.conf to:
name resolve order = lmhosts wins bcast host
And leaving /etc/nsswitch.conf as default allows me to browse OK.
Thanks for the advice Steve. You said:
... Opendns breaks the assumption that DNS servers won't return bogus
records when asked for hosts that they
If you are using opendns, then address resolution will not work correctly
because samba gives precedence to DNS records over broadcast name resolution by
default. This is considered a reasonable default because broadcast name
resolution is not scalable and should be a method of last resort;
15 matches
Mail list logo
