Here is the ouput you asked to see:
system4://home/main4
root:# vlsmbmnt
Mount/Unmount
Mounting [\\SYSTEM1\shared] at [/root/mnt/SYSTEM1-shared]
retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(

manual page (e.g. man mount.cifs)
While doing this, I figured out a few things.
As you can see, I'm trying to access a shared directory on SYSTEM1. That shared directory is called
shared stuff
with a space embedded in the name. When I saw the output in the terminal window, I thought, perhaps that space in the name is part of the problem. So, I went to the SYSTEM1 machine, changed the name of the directory in question to sharedstuff, and tried vlsmbmnt on SYSTEM4 again to access the sharedstuff directory on the SYSTEM1 machine. And - it worked. Also, to access the sharedstuff directory on SYSTEM1 from SYSTEM4, I had to enter the username and password for SYSTEM1, which is what I want.
Then - I tried to access sharedstuff using the menu item NETWORK >> WINDOWS NETWORKING, instead of going through the terminal. It did not work. I assume it did not work because using the menu item I was not logged in as root.
So, here are my questions:
1) Does the output I show above from the terminal tell you something else useful that I am overlooking?
2) How do I get the menu item NETWORK >> WINDOWS NETWORKING to work while not root?
3) How do I get SYSTEM4 (Vector Linux) to deal with directories on other machines that have spaces embedded in their names? The other machines - Ubuntu, Crunchbang, openSUSE, Windows - don't have a problem with this.
4) From SYSTEM1 (Ubuntu), I am able to see SYSTEM4 (VL) as part of the workgroup, but I can't mount - or even see - the directory in SYSTEM4 that I want to share with other machines. What do I need to do in SYSTEM4 to make that work? (I am wondering if that is due to the problem with setting the shared drive in SYSTEM4 to available=yes.)
5) Bonus question: Thanks for the tip about using the middle mouse button to paste stuff. I did not know about that. However - One benefit of VL is it is lightweight, so I can use really old hardware. How do I copy and paste from xterm if I have a really old mouse that has only two buttons on it?
(To MOE-lnx: Thanks for the reply. I have Windows in the mix, that is why I am going with SAMBA, my poor understanding is that in such a case SAMBA is the tool to use. Is that correct? Anyway, I already have SAMBA set up and running well on five other machines, I'd hate to change it now just because of Vector Linux. Besides, even if I were to go with sshfs - whatever the heck that is - I'd still want to figure this out. Supposedly SAMBA is *supposed* to work in VL, and if it isn't working because something is wrong, I'd like to see it fixed, instead of it coming back to bite me months later in some fashion I don't expect. It is sort of like, I go to the repair shop to get the radio in my car fixed, I wouldn't be satisfied if they said I could set a boombox on the seat and listen to the radio that way instead of fixing the radio. Finally, I'll admit that right now I'm all googled-out, I can't start from scratch on sshfs right now. There is a HUGE problem with Google stuff, and that is that there is no quality control. I can find lots of documentation out there, but is it any good? Is it complete? Is it up-to-date? Is it good practice? When you're new to some topic, you're not in a position to know what you're looking at.)