I added the pre-release updates to intrepid and tested browsing it
works.
However, If I try to "Connect to a server" and don't specify the share
name I get and error saying unable to mount. I believe in previous
versions I expected to get a list of shares. Maybe this behavior change
was intentio
Update,
Cannot display location "smb://servername/"
The message I get is "No application is registered as handling this file"
- Original Message -
From: "max"
To: ja...@rubixnet.com
Sent: Monday, January 26, 2009 12:23:49 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Bug 207072] Re: nau
I am running intrepid.
My machine is not joined to any domain.
I go to Places -> Connect to Server...
Select select "Windows Share" from the service type.
Enter the:
Servername
Username
Domain
Click Connect
I get a prompt for the password
Enter the password.
Then I get the error message
Cannot
I agree the unpatched version does have the same behavior, however I was
referring to the pre-hardy version of ubuntu when this problem initially
came up. Gutsy did not have this issue.
- Original Message -
From: "NTolerance"
To: ja...@rubixnet.com
Sent: Monday, January 26, 2009 1:22:10
mba shares for machines
inside an ADS network.
Tab, this is a different issue than the one being discussed here. The
problem you are reporting is discussed in bug #216104.
--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You rec
i dont know how to get rid of this someone help
--
dpkg was interupted you must mnnually run 'dpkg --configure -a' to correct the
problem
https://bugs.launchpad.net/bugs/119856
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-termin
The gvfs patch mention above also fixed this for me. No other solutions
worked. I used the binary replacement method.
--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a member
Here is a compiled binary for amd64 of the first issue in this
thread. It does not solve the whole issue but might help some people
get by until an actual fix is released. Again this only only solves the
issue of browsing shares on a Windows machine from a Ubuntu workstation
that is not joined to
That sounds like a different issue. Maybe a browser master problem.
This bug affect specificly browsing the shares on the machines not the
entire domain/workgroup.
- Original Message -
From: Martin G Miller <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Thu, 25 Sep 2008 15:34:33 -0500 (G
