Recent experience with the network leads me to believe that this is, at least
in part, a Windows Browser-Master problem.
Windows is known to have trouble (some say it's broken) with browsing
peer-to-peer networks. One computer in the network takes the role of being a
browser master. There is a
Thanks closing bug
** Changed in: samba (Ubuntu)
Status: Incomplete => Fix Released
--
cannot browse windows shares via gvfs-smb
https://bugs.launchpad.net/bugs/206585
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu
yes after those changes in smb.conf I can browse windows 2003 shares
--
cannot browse windows shares via gvfs-smb
https://bugs.launchpad.net/bugs/206585
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bu
So does it work properly when changing those options?
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
cannot browse windows shares via gvfs-smb
https://bugs.launchpad.net/bugs/206585
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
thanks for piont the target!
in smb.conf changing this parameters helps:
client signing = no
client use spnego = no
regards!
--
cannot browse windows shares via gvfs-smb
https://bugs.launchpad.net/bugs/206585
You received this bug notification because you are a member of Ubuntu
Server Team, which
seems to be a samba issue rather than a gvfs one
** Changed in: samba (Ubuntu)
Sourcepackagename: gvfs => samba
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
Status: Incomplete => New
--
cannot browse windows shares via gvfs-smb
https://bugs.launchpad.net/bugs/206585
Y
