Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
im having trouble with one of my linux boxs contacting the outside world.
the box in question is running suse 9.1 with samba 3.x.
its role is file/printer server for the homogene home network. i'm using fixed ip addreses with the host names and ip addresses saved in the host file.
the dns addresses are also entered (router address, and 2 external)
samba is running and working perfectly.
the problem is from the samba box no outside ip can be reached (internal subnet is 192.168.x.x)
im not sure if this is samba typical that all non internal ip addresses are ignored or if i forgot to do something. The samba box has 2 network cards. the second one isnt configured correctly yet as i wish to use the box as squid/proxy/mail server and as such nead to reach the outside world:
i believe this configuration should work with the samba box in a dmz without the needs for buying an expensive router with dmz function (the cheaper routers on the market tend to cover the fact that their dmz function is really just an unprotected host port)
So your router's aren't connected directly to each other, but go through the SAMBA box first? This sounds odd to me, but maybe that's normal practice and I just am out of the loop
If it's possible, I'd temporarily connect another regular box to the router that seperates the world from your samba box and try surfing with that.
Generally when I'm troubleshooting network problems (which I'm sure you have tried, but just to cover it) I start with pinging google and then google's IP. If neither work, I look at my network card, ensure it has an IP, and ensure I can ping my router. If the card has an IP, can ping the router, and even other boxes on the LAN, then I move onto router. Is it denying me for a reason I can fix, or is there something physically wrong with it? If the machine is setup as the DMZ host, is it blocked somehow from traffic one way or the other, does another router produce the same the result?