If you are using Mandrake 9.0 or have added your Linux-based computer(s) to a workgroup, while you were doing all of the above the Windows boxes on your LAN were not unaware of your Linux computer antics with LinNeighborhood. Take a look at the Network Neighborhood/Entire Network folder on your MS Windows machines.
You should find your Linux workgroup(s) plus your Windows workgroup(s) listed in the Entire Network folder of the MS Windows Network Neighborhood. If you double-click on the Linux workgroup in which your Linux-based computer is a member, you should see it listed. In Figure 5, the Md workgroup is the Linux-based computer workgroup and the Wo workgroup is the Windows-based computers workgroup.
However, before you can access the shares on your Linux-based computer from your Windows-based computer, you must setup a user account and a Samba account for your Windows username/logon on your Linux machine. Please see the Accounts on Remote Computers section on Page 2 for that procedure.
Wrapping It Up
With Linux, there are lots of choices when it comes to working with files, printers, and other such resources on remote, networked computers. Some are better choices than others. Moreover, what is a better choice for one Linux user might not be a better choice for another Linux user. Today's discussion and tutorial is aimed toward attempting to provide a better choice for Linux beginners, computer newbies, and people migrating from MS Windows to Linux.
Likely, graphical-interface software for enabling access to remote, network computers from a Linux-based computer is a better choice for Linux beginners, computer newbies, and people migrating from MS Windows to Linux. Of the several such graphical interfaces for enabling access to remote, network computers from a Linux-based computer, we picked LinNeighborhood. Another article by another writer might pick a different piece of software for enabling access to remote network computers. And we plan to cover other networking-tool software in later articles.
In order to make it easier for people migrating from MS Windows to Linux, we used a Network Neighborhood metaphor similar to that found with the Microsoft operating systems. You can use the Linux Network Neighborhood paradigm for accessing shared resources on remote networked computers even if you decide to use software other than LinNeighborhood for enabling access to remote, networked computers from your Linux-based computer.
For us, LinNeighborhood was slightly easier to install and to use with Mandrake 9.0 than it was with SuSE 8.1. We gave up trying to use it with Red Hat 8.0.
For additional information about LinNeighborhood and how to use it, please see the LinNeighborhood Release Notes (Links in Resources section, below.)
Linux software such as LinNeighborhood makes a valuable contribution to making Linux Networking as easy as Microsoft Windows Networking. Nevertheless, working with remote shared resources is easier with MS Windows than it is with Linux, at this time.
One thing the Linux distributions providers could do to help make Linux Networking as easy as Windows networking is to configure Samba or other networking software automatically during the Linux distribution installation and to pre-mount all the shared, remote resources in a network folder. Then when a Linux user wants to access shared resources on networked computers, all he/she would have to do is to open a network folder, such as our Linux Network Neighborhood and voila', it would be just like opening the MS Windows Network Neighborhood.