Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Would someone please let me know how to set-up Samba, so I can share files with WinXP clients, but not to allow the network shares to be seen on the internet. What I mean is that when I go to grc.com, and let it run scans on my computer, Samba is letting grc.com see my WORKGROUP NAME, COMPUTER NAME, and USER NAME. This could also be my fault as I did try some tinkering around with the SuSE firewall 2 settings.I am a newbie so anything someone could suggest I will certainly try.
I am running SuSE 8.0 Pro as a gateway to share the PPP
connection I have. And yes I will read all the documentaion that came with Samba, it's just a lot to read, and I have not yet completed all of it.
The ports to block are as you said 137 thru 139, and they need to be blocked for both TCP and IP access.
An additional point is that you should NOT enable guest access in smb.conf. I misread the documentation, enabled that option, and in less than an hour one of my Windows boxes had fallen victim to a script kiddie's attack and in addition was infected by the Chernobyl virus, one of the worst in existence since it can destroy flash BIOS chips rendering the motherboard useless.
Fortunately I was running Tiny Personal Firewall on all the Windows boxes, configured for maximum security. That didn't stop the invader from coming in via Samba since I had enabled Samba's access on the firewall rules -- but it did trip the alarm when the zombie program he had planted attempted to call home. This let me isolate the affected machine, save the undamaged data from it, and stop the infection short. It also taught me the danger of allowing guest access other than to extremely limited areas of a network!
If you don't want outsiders being able to prowl your systems via Samba, use the "allowable IP addresses" access options in the global area of smb.conf to specify that only 127.0.0.1 and your LAN IP addresses (mine are 192.168.0/24) are allowed access.
Thanks Mara, and JimKyle
Sorry I did not write sooner, but I reinstalled SuSE, and I did find the solution to the problem. The SuSE Firewall2 init scrip had some lines of code for Samba support i.e. for Samba to connect to remote networks, and also for remote admin of Samba. Since I didn't need this feature, I just (#) commented out the lines of code that call this feature up, and YEAH! no more netbios stuff being seen by scans at GRC.
Thanks John McKenna
p.s. the firewall init script is found in /sbin, and the auther of the firewall makes a funny comment about these rules, "baah these rules look evil".