[Bug 456808] Re: Karmic-Networking (SAMBA) just does not work, even with detailed attention.

[floid]

Related observations, as I try to stalk down the Launchpad bug that
surely must exist for the apparent CUPS/samba Upstart race*:

Nautilus will show browsable items via smb://ip_address or
smb://dns_name (where, if anyone is confused, ip_address would be e.g.
192.168.1.64 and dns_name could be mymachine.local - or localhost for
127.0.0.1);

Whichever SMB stack Nautilus is using does *not* seem to be doing
netbios name resolution properly at the moment, at least on my machine
and network.  This is made confusing because it does retrieve the browse
tree of workgroups and netbios names, but falls over with a less-than-
descriptive error ("Unable to mount location, Failed to retrieve share
list from server" - well, yes, but apparently because it's not finding
the proper address for the server) if you double-click on any individual
host.

So, for determinism in testing, you might want to stick with IP
addresses there.



* The apparent race is evidenced by log.smbd entries such as:
[2009/12/10 11:26:10,  0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
after a reboot, so you're probably also better off testing with shared folders than with printers [which, if you're relying on samba to pick up from CUPS, won't appear until you give samba a restart so it can talk to a CUPS that's finished loading].

-- 
Karmic-Networking (SAMBA) just does not work, even with detailed attention.
https://bugs.launchpad.net/bugs/456808
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.