SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: SuSE 9.2, Slackware Current, Arch Linux 0.7
Posts: 119
Rep:
Survey Says... Samba!!!
Well I assume you know how to connect 2PCs together, if I am assuming too much let me know... but I will try to give you a quick how-to on setting up Samba using YaST.
Samba is, as you may or may not know, an implementation of the Server Message Block protocol (smb, hence samba, get it!) Since you want your other computers to be able to access you Linux Box your going to want to enable the Samba Server, not just the client. Fortunately this is very easy for us in SuSE. Under YaST in the Network Services section should be a spot for samba. There are 2 options in the network services panel, you are going to want to click on Samba Server. Click Enable Samba Server and change the name of the workgroup to the one that your Windows PCs are currently on then click next.
In the next window that pops up make sure that both share homes (this shares your /home/(your username) directory) and Share Printers are checked. It is possible to share more of your PC if you click on the advanced button, however I suggest you have a strong sense of how samba configuration files work before doing this, documentation can be found on the Samba Website. If you have a question about how to share a specific directory on you computer I might be able to help you with that too.
You also need to set up the Samba Client, it's right next to the server setup section. There is only one configuration option, so it's pretty easy... just click on it and set it to the correct workgroup setting for your windows network.
So there you go, your Linux PC should now be able to 'talk' to your Windows PC's and vice versa, Simple, no?
Last edited by electronique; 11-15-2004 at 11:33 PM.
In any IP-based network any host can provide Internet connectivity, providing that it, itself is connected to the Internet. As electronique guided you, you will need to configure your 9.2 box as a gateway (i.e., 192.168.0.10) and configure the firewall to allow traffic from your Windows PC through.
There is a better / easier method. Go to Best Buy and get a $45 Netgear Internet Router, or Linksys whatever. Then plug your Internet connection to the router (which is bullet proof for security) and you can connect up to 252 client machines to share the gateway. I personally use the Netgear RP614 and I have had ZERO intrusions.
This is a hardware based solution, rather than the software based one provided by SuSe. It also give you an option of going Wired or Wireless.
Last edited by slacker9876; 11-16-2004 at 02:45 PM.
there are SOME benefits of the SuSE software router over a hardware based linksys type device. You get a bit more flexibility. So, if you want to get a second NIC for your SuSE box, you should look into iptables (http://www.netfilter.org/ . Be warned, there is a lot of reading ahead of you.
I moved from using my Linux system as my gateway to using a Linksys router. My home SuSE machine(s) is not a server class machine and is not intended to be active 100% of the time, it's also not a low-end machine either. If you use Linux as your gateway as well as other functions, you might happen to be married or have children that are using the internet when you want to mess with Linux. So, if you are just starting to learn the ins and outs of Linux (which implies messing things up and fixing them) you might want to shy away from Linux as your gateway.
So, the Linksys/Netgear router , still put IPTABLES on you SuSE, and run XP SP2 with the firewall feature. Like the previous post said, it's not really as good a solution because you lack flexibility in your security and I don't think the Linksys and Netgear are quite as secure as IPTABLES.
If you want to use the SuSE machine as a learning tool for building the firewall, then I'd still head out and get a Linksys or Netgear but connect them directly to one of your ethernet ports. This solution will provide a lot more security then having your Linux machine connected directly to the Internet.
Distribution: SuSE 9.2, Slackware Current, Arch Linux 0.7
Posts: 119
Rep:
obviously the originator of this thread hasn't included enough information for us to even help him (linux-windows network...? pretty vague) On top of the he also hasn't replied... so instead of us posting 50 tips when we don't even know what he needs help with.. why don't we just close the thread and forget about it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.