This question is from a supernewby -- not with computing, just with Ubuntu, which I installed today.
My only problem -- so far -- is trying to open folders under "Browse Network" in the file manager. At least I guess it's the file manager, though nowhere do you find those words. You get to "Browse Network" by clicking the "Home Folder."
My network printer and "Windows Network" pop up soon enough, but double-clicking "Windows Network" may get to my local network, called "localan," or it may claim a timeout after about 100 seconds. If it does open localan, it shows the two Windows and a Debian machine on that network. Trying to open one of them is the most problematic. Oddly enough, after many timeout reports, suddenly the selected machine will open. At least it has once in an afternoon of trying. Once it opens, files in its folders are readily accessible.
The hardware can't be the problem. Yesterday I was running Windows Vista on it. Local network access was slick as a breeze and not the reason I abandoned Windows.
Typically after a minute or so, trying to open "localan," I get the following notification:
"Sorry, could not display all the contents of "Windows shares on localan": DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
and nothing else. Clicking "localan" again gets the same timeout and message, although once it did return the list of machines on localan.
Note that I am submitting this question from the same machine, using the same hardware and software, so it can't be the Ethernet adapter. Curious that this is an intermittent problem, which in my experience is rare in software. I can't believe that other users would tolerate it. Does anyone have a suggestion?
Thanks for your attention.