Please see the bug below showing similar behaviour on Intrepid, together
with some steps to isolate the problem.
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/316862
--
smb workgroup detection takes too long
https://bugs.launchpad.net/bugs/73591
You received this bug notification becau
Joshua, Mark: your issue is apparently gvfs-related (Gnome), while the
original reporter has a konqueror issue. Please follow up on bug 316862
instead.
amichair and other KDE reporters: are you still experiencing the problem
with one of the supported releases ?
** Changed in: samba (Ubuntu)
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
I've moved since then to a new setup, now I'm with a new Jaunty machine
(upgraded from a fresh Intrepid installation) on the same LAN as the
original winxp box, plus another xp. I can only note what happens out of
the box now - I don't remember if there were any custom configurations
on the old set
Same problem here with Karmic Koala, half-solved.
The server is a Windows 2008 server. The Linux machine has only the
client part of samba. The IP addresses are fix.
In konqueror:
smb://servername works fine
smb://10.0.0.211 works fine
smb:/workgroup/servername fails
I found that my problem had
Network detection is taking too long in Lucid too...
--
smb workgroup detection takes too long
https://bugs.launchpad.net/bugs/73591
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 list
Ubun
