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.
somewhere on the XP box will be its settings for your LAN.
try running winipcfg, that will tell you what public and private IP's your XP box uses (it does for Win98).
I may have given you a slight red herring - you might be better of using a server name instead of the IP.
I typically refer to IP's because at home I use static IP's, and my workplace does the same
but if I wanted to, I could set up a web server on my games box (called Mage), and point my browser at mage:80 to get whatever webpage is being served (assuming httpd was on port 80).
I could do the same as above and point it at 192.168.xxx.xxx:80 for the same effect.
given your XP box is also the dialup, you could also point your browser on the linux box to the IP your XP box is given by your ISP - the request will get sent through the XP dialup to the ISP, and back again to the XP box, which will respond in the same manner (NAT takes care of the internal > external addressing)
given that the ISP will be dynamically allocating your IP (assuming a typical case), your public IP will be changing each dialup, as will the public DNS; to deal with this, use a free DNS server that provides a "static" DNS.
this is a fairly simple description, and I'm not across any problems you might get as I've not actually done it - I just understand the principles.
Anyways, I guess I'm not very clear at:
1. I found that my Linux system is using the IP, 192.168.0.38 while 192.168.1.1 was used by my WindowXP system.
2. I tried to SSH into my Linux system from my WindowsXP system, using PuTTy but failed. It shows "Network error: Connection timed out." I tried stopping iptables on my Linux system but it does not help too.
Sorry if I am sounding too stupid because I'm very new to Red Hat.
Originally posted by trallith Hello:
about the ssh problem, make sure whatever firewall your running isn't blocking port 22.
mikefoo said he dropped iptables to allow all connections:
Originally posted by mikefoo
...I tried stopping iptables on my Linux system but it does not help...
it might be worth while having the commands he used to do that posted as well.
it might not have worked.
Originally posted by trallith
Also, if anyone can tell me why he shouldn't connect over the lan, I would really appreciate it.
that was my original question
he hasn't provided any info to suggest he shouldn't, imo.
Originally posted by trallith
Oh ya, and if your running a webserver behind a router, you'll probably want to eventually setup port forwarding on the router, unless you have a seperate internet connection on the server also.
it was my assumption that eventually the webserver would be made available to the public; I don't know if that is going to be the case though.