mtdub2, I've found that starting pyNeighborhood as root (either from command prompt or add 'gksu ' to the desktop file on the 'Exec' line; e.g. 'Exec=gksu pyNeighborhood') fixes the issues you're encountering. It's probably just a simple permissions problem somewhere (I've never bothered to figure it out). Also, I DO use the 'mount as user' option and it works fine for me but the alternative should work as well.
While I appreciate the suggestion, I have been starting pyNeighborhood from a command prompt as root. I'll try adding gksu to the exec line . . . stand by... Hmmm... I don't know. I mean, it seems to be working now. I tried starting it from a root command prompt, as before, got the same results, then I tried changing the "Always use default user" setting, added my user name and password, and 'poof' it was working. I mean, immediately after changing the "default user" setting, I double-clicked on a share that it previously would not mount, and it mounted it. My problem now :-) is that when Midnight Commander comes up (I'm assuming it's Midnight Commander -- maybe it's something else, I don't know), the directory names are in white text. (?) Being as the background is also white, I don't see them until they are selected. How would I go about changing the colors? I did also try "gksu pyNeighborhood" from a user terminal ($ gksu pyNeighborhood), and after entering the root password, it worked fine too. Well, sorry for the trouble guys, I honestly thought I had tried to run pyNeighborhood from a root command prompt already or I wouldn't have posted. Any ideas though, on how to set the colors so I can see the directories?
While in the preferences, one might as well change file manager from "xterm -e mc" to "xfterm4 -e mc". With xterm you get a tiny little window and mc has a color scheme that makes it almost unusable.
Too funny... Thanks, guys. Before I got the previous post done, you had answered that question.
Now I have another problem... when I mount a share, I do now get a readable window, but it only displays /proc -- on both sides of the window. I shut down pyNeighborhood, started it up again, and it does the same thing. Any idea what's causing that? Because before, with "xterm -e mc" at least it was displaying the share I had just mounted. Well, I think I just figured out what's going on with that: the share I'm trying to mount has a space in the name. If I try to mount a share without a space in the name, it works fine. Okay. So, any ideas on how to get it to work with a share that has a space in the name? :-)
Thanks again for your quick response.