** Description changed:

  This private bug is a support escalation to parallel Public Bug #216104
  which explains the same issue.
  
  This was mistakenly filed without the private flag as bug #235774.
  Notification went out to various non-Canonical people, including the
  Ubuntu Bugs team.  The first bug was closed as Invalid for now, this is
  a repost.
  
  The Places > Connect to Server... dialog in hardy do not work to connect
  to Windows share in hardy. There are multiple failure, and its behavior
  is extremely confusing. This worked without any problem on gutsy using
  the same server and same credentials.
  
  The share we are trying to connect to is hosted on a Windows Small
  Business Server 2003 server.
  
   - Local username: ubuntu
   - Remote username: ubuntu
   - Windows server name: win2003
   - Windows domain name: canonical (it is an Active Directory)
   - Share name we connect to: clients
  
  To be sure this is not a problem that have been fixed in an upcoming
  update already, I installed the following package from hardy-proposed:
  
  nautilus 2.22.3-0ubuntu1
  gvfs, gvfs-backends and libgvfscommon0 0.2.4-0ubuntu1
  
  == Steps to reproduce ==
  
  1. Go to Places > Connect to Server..., choose "Windows Share" in
  Service Type, fill in "Server", "Share", "Username" and "Domain Name"
  appropriately with the value above, click the Connect button (see
  Screenshot-1.png)
  
  2. "Enter Password" dialog is shown. Provide password and then click
  Connect (see Screenshot-2.png)
  
  3. An error message is displayed: 'Can't display location
  "smb://win2003/clients" -- The specificed location is not mounted'.
  However, the shortcut icon appear on the desktop nonetheless (see
  Screenshot-3.png). Click Ok to dismiss.
  
  4. Double-click the shortcut icon titled "clients on win2003" on the
  desktop. The "Enter Password" dialog is displayed again, this time with
  a wrong value for Domain (see Screenshot-4.png). Change Domain from
  "MSHOME" to "canonical", provide password and click Connect.
  
  5. The content of the share is displayed as expected, but a second
  shortcut icon appear on the desktop, with the same name (see
  Screenshot-5.png).
  
  == Problems ==
  
  1. Confusing "Can't display location "smb://win2003/clients" -- The
  specificed location is not mounted" message, even tough a shortcut icon
  for the share appear on the desktop.
  
  2. "Enter Password" dialog is displayed twice: once after filling the
  info in Place > Connect to Server, and then again when trying to open
  the share from the shortcut icon on the desktop.
  
  3. The "Enter Password" have wrong value for Domain the second time it
  is shown. It should display the value entered originally.
  
  4. When the correct domain and password are provided in the second
  "Enter Password" dialog, a second shortcut to the share appear on the
  desktop with the same name.
  
  Not sure if this bug should be filed against Nautilus or GVFS or
  something else, so I left the package field blank for now.
  
  If required, it is possible to give access to the VM for both the 8.04
  clients and the Windows server. The client VM on the Montréal VMWare
  server is "Ubuntu-8.04-desktop-i386", the server VM is "Windows Small
  Business Server 2003".
  
  Related Canonical support case is #2267.
  
  I did not report a public bug right away, as there are a couple bugs on
  the subject already in Launchpad and it is unclear if and how they
  relate to this one. Also, I was not sure if the bug should be reported
  as a single one, or as multiple independent ones.
  
  QA Team response deadline: May 30th 2008 11h AM EDT.
+ 
+ REF: 50020000002qQ1a

-- 
P3: Regression, multiple problems when using "Places > Connect to Server" to 
connect to Windows share in hardy (reposted)
https://bugs.launchpad.net/bugs/235782
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to