cannot browse windows shares via gvfs-smb

[orzeh]

Binary package hint: gvfs

When in 'run application' type: smb://widows_server (if it is important - real windows 2003 server in AD env), nautilus shows an empty window with info:
"The folder contents could not be displayed.
Sorry, couldn't display all the contents of "users on widows_server": Invalid argument"
in seahorse all passwords and usernames are correct so i think this is not rights related.
When i click "OK" the window remains empty and responsible.

[Sebastien Bacher (seb128)]

thank you for your bug report, does browsing it using smbclient from a command line works correctly? is the share listed in the network location?

[orzeh (orz3h)]

Thanks for the answer!
i've tried with smbclient:
"smbclient \\\\widows_server\\users password
Domain=[DOMAIN] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
smb: \> ls
client_check_incoming_message: received message with mid 9 with no matching send record.
SMB Signature verification failed on incoming packet!
Server packet had invalid SMB signature! listing \*
Error in dskattr: Server packet had invalid SMB signature!
smb: \> "
so it means problem with samba?
widows_server is main AD controller
ps.1 yes, the share is "users"
ps.2 on previous ubuntu this worked like a harm
regards!

[Sebastien Bacher (seb128)]

seems to be a samba issue rather than a gvfs one

[orzeh (orz3h)]

thanks for piont the target!
in smb.conf changing this parameters helps:
client signing = no
client use spnego = no
regards!

[Chuck Short (zulcss)]

So does it work properly when changing those options?

[orzeh (orz3h)]

yes after those changes in smb.conf I can browse windows 2003 shares

[Chuck Short (zulcss)]

Thanks closing bug

[Mark Ellse (markellse)]

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 defined hierarchy of who does it - generally the machine that is on longest but has the more recent operating system. The browser-master is the machine that stores a list of host names and their ip addresses, enabling browsing of the network. I think that Linux machines on a Windows network rely on the Browser-Master for browsing.

Setting up a Windows computer as a broswser-master is inaccurately and incompletely documented and supported by Microsoft, who really you to have a Windows server. My experience that the process of a browser election can be completely confused if other machines are on the network, leading to unreliable browsing with both Windows and Linux. In particular it may be that a non-Windows DHCP server inhibits Windows machines from being browser-masters.

Browsing problems on our network seem to have disappeared since we've installed an SME server (www.contribs.org) AS A DOMAIN/WORKGROUP CONTROLLER. This has resolved our browsing problems.