** 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
Desktop Bugs, 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
Hi Nikos,
You're having a different problem to this bug. This bug is about being able to
connect by IP address, but not by server name. Your problem seems to be that
you can't even connect by IP, which is a different issue.
Cheers
Andy
--
Connect to smb server by name doesn't work, but by IP
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
Steve,
thanks for your post. I was hoping there was a way to fix this without
disabling windows name resolution.
You say that it is a bad idea in general to use wins resolution. Is
there a better way to resolve windows host names especially when using a
DHCP server?
--
Connect to smb server by
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
Setting /etc/samba/smb.conf to: name resolve order = lmhosts wins bcast
host also makes it work for me. It hasn't worked since Dapper - hooray!
FYI - I run Hardy Heron on a laptop with my only connection via WiFi to
a wireless router which has a window box connected to it via cable. I am
not
** Bug watch added: Debian Bug tracker #459972
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459972
** Also affects: samba (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459972
Importance: Unknown
Status: Unknown
--
Connect to smb server by name doesn't work,
** Changed in: samba (Debian)
Status: Unknown = New
--
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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
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;
va9rant,
You are a genius. I've removed wins from the hosts: files mdns4_minimal
[NOTFOUND=return] dns mdns4 wins line in /etc/nsswitch.conf, and I can now
connect by name.
This bug is now solved for me.
Thanks very much
Andy
--
Connect to smb server by name doesn't work, but by IP address
When I remove WINS from nsswitch.conf, this breaks browsing entirely for
me. Ping by name also fails - resolution is incorrect because of
OpenDNS.
It seems I can connect and ping by name if I use the servername.local
instead of servername, even though I don't define the domain of my
computers at
hello can confirm that this bug may be caused by settings in
/etc/nsswitch.conf.
In my case, I have Hardy, installed with samba, firestarter (running at
startup) and winbind.
adding the value wins in the line in /etc/nsswitch.conf:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
I had the 100% exact same problem that Andy describes. However, for me
it was not a problem with Nautilus at all, and just a misconfiguration
of samba's name resolution.
The way I fixed it was
sudo gedit /etc/samba/smb.conf
Uncomment this line (remove the semicolon)
; name resolve order =
Hi Brandon,
Thanks for the tip. I've removed the DNS server addresses from my config, and
it hasn't made any difference.
Hi CoffeeBurrito (that doesn't sound like a very tasty snack :-) ),
I've tried this as well, sudo /etc/init.d/samba restart doesn't work (there is
no samba in the /etc/init.d
Please forgive me if this is incorrect, but I want to see if this
information helps others better troubleshoot this issue.
While researching the issue for my similar bug report, I found that
having a DNS server that responds to otherwise invalid host entries
(i.e. OpenDNS) may contribute.
Hi Seb,
I am running FireStarter, but it shows no blocked connections, and disabling it
and the firewall on my debian smb server doesn't stop the problem. There is no
hardware firewall on my internal network. My windows (sorry :-) ) machine
doesn't have this problem.
Here is the output from
Re MikeK's comment - yes using the IP address usually works, but the
reported problem is that the name or graphical solution is broken for
many, if not most users. We shouldn't have to insert the IP address to
use this feature.
--
Connect to smb server by name doesn't work, but by IP address
I had problem too. I stumbled upon a comment in
https://help.ubuntu.com/community/SettingUpSamba that said put IP
HOST in /etc/hosts. I did and problem resolved. Not elegant but it
gets around the issue.
--
Connect to smb server by name doesn't work, but by IP address does
I also have this problem also on 32-bit Hardy, and have had it ever since an
update in Dapper. Many others also have the problem - see posts at:
http://tinyurl.com/5e6psk
I previously reported this bug on launchpad.net with Bug 47386. The
problem remains just as bad as ever on Hardy.
--
I have the no application issue also. sometimes it will work, sometimes
not. Sometimes it will display the error and then still work for a
little while.
I am new to Ubuntu so I have not intentionally installed any firewalls.
However, I do not know if any come with the default install.
I don't
Forgot to mention that I am using the 64 bit version.
--
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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
thank you for your bug report. does using smbclient on the server name
work correctly? do you have some sort of firewall that could create the
issue?
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Incomplete
--
Connect to smb server by name doesn't work, but by IP address does
** Changed in: nautilus (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Confirmed
--
Connect to smb server by name doesn't work, but by IP address does
https://bugs.launchpad.net/bugs/235560
You received this bug
** Changed in: nautilus (Ubuntu)
Sourcepackagename: None = nautilus
Status: Incomplete = New
--
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
Desktop Bugs,
26 matches
Mail list logo
