My Windows machines require authentication - i.e. require a known username/password. In Breezy, I used to be able to browse these machines. I would be prompted with a username/password dialog box. Once I filled in the correct details, browsing these shares was like browsing local folders.
On Dapper (Flight5) however, I am not presented with a username/password dialog box. Instead, I am given an error box saying that it could not browse that location. I am not even able to see the shares available on the machine.
Additionally, when I use Places->Connect To Server, I am able to specify a username/password and a desktop icon is created for the location. But I still receive the same error when I try and double-click the icon.
If I boot into my Breezy partition, this all still works so it is definately not a configuration issue with my Windows machines and hence should be treated as a regression in Dapper.
This will affect a lot of people that work in environments with non-public Windows shares.