"Updated the gvfs and samba related packages from hardy-proposed [on 24th June 2008]. Trying to reach a Windows Server 2003 share in an Active Directory domain environment through Nautilus' "Connect to Server..." resulted in the following message box after supplying the login info:
"Sorry, couldn't display all the contents of "smb": The specified location is not mounted"
Upon reloading the same Nautilus window, it produced the original "Unable to mount" message. Both before and after the update, connecting to a share on the server with smbclient works as intended (using the -U and -W arguments to specify login info).
I have talked about this to Sebastien Bacher earlier this month, but I guess it should be made public that I have talked to my supervisor at work about this and we can provide remote access to a Hardy box in a Windows Server 2003 domain environment for testing purposes. I would like to ask the developers to contact me if this will be needed and we will discuss the details in private."
As of today, browsing Windows 2003 shares works (i.e. it lists the available shares on the server correctly), actually listing the contents of the shares and mounting produces the above symptoms.
Crossposting my relevant info from bug #209520:
"Updated the gvfs and samba related packages from hardy-proposed [on 24th June 2008]. Trying to reach a Windows Server 2003 share in an Active Directory domain environment through Nautilus' "Connect to Server..." resulted in the following message box after supplying the login info:
"Sorry, couldn't display all the contents of "smb": The specified location is not mounted"
Upon reloading the same Nautilus window, it produced the original "Unable to mount" message. Both before and after the update, connecting to a share on the server with smbclient works as intended (using the -U and -W arguments to specify login info).
I have talked about this to Sebastien Bacher earlier this month, but I guess it should be made public that I have talked to my supervisor at work about this and we can provide remote access to a Hardy box in a Windows Server 2003 domain environment for testing purposes. I would like to ask the developers to contact me if this will be needed and we will discuss the details in private."
As of today, browsing Windows 2003 shares works (i.e. it lists the available shares on the server correctly), actually listing the contents of the shares and mounting produces the above symptoms.