Linux Server - Windows Client -CONFIGURE!!? 2

[energiza]

I've got RH-Linux 8.0 installed as server with all, seems to work ok, I'm already developing perl things on this server, Apache runs fine, all daemons at boot report OK.

When running neat on the GUI, this is, the Network Configuration, I get my ethercard active, which is configured with IP address 192.168.0.1. (let's call this machine ".1". I'm not running any DHCP server, the IP is static and on the host tab of this configuration window, the card is linked to the 127.0.0.1/localhost which when requested within the server via browser, makes apache to bring the home page I've in the http's root directory. The DNS tab of this same machine has localhost.localdomain on Hostname and blank on the DNS's fields below. I've tried putting something on primary, secondary and apache response becomes very very slow, so it's blank on those DNS fields.

That same machine has a disk with windows and at boot I use GRUB to switch to windows or to linux. Under Windows my 2 PC's LAN works OK.

The other only Windows machine is configured in Control Panel Network at the ethercard's TCP/IP, 192.168.0.5.(let's call this machine as ".5&quot The Gateway was given the 192.168.0.1.

I ping 192.168.0.1 on my .5 machine and the 4 attempts work fine with 0% loss. While I do this, the .1 machine is running the Network Analyzer on capture mode and every packet is reported with right "source"/"destination" ip addresses and what kind of request is in progress.

WHEN I REQUEST AN HTTP at .5 using Windows Explorer, .1's Network Analyzer receives the request and replies saying "Destination Unreachable".

¿Do you have any idea of what could be happening or what am I missing?

What I want to do is 2 things:

1.- Have a local or intranet web server under linux that can respond to my windows (.5) machine requests the same way it works when I dialup the windows machine (.5) to the internet.

2.- add a modem/router/hub (or a separated hub AND modem/router) to my 2 pc's lan that can give access to both machines to the internet (something I've done under windows only and I THINK should be as simple as just plug the modem router to the lan for the linux to access internet).

Thanks and Regards

 

[RhythmAce]

I'm goint to assume from the info you just gave, that you have the 2 machines connected using a crossover cable. The reason you have problems when putting anything in the dns is because you are not connected to the internet and the dns servers can't be found. What are you typing to get to the apache server from .5? Right now the only way is with the ip 192.168.0.1. If you assigned a host name to that ip, you would be able to use that also. The ServerName in httpd.conf should be localhost or the hostname of the machine since you don't have a registered domain name. By default apache will "Listen" for all addresses on port 80.

To share an internet connection get a little more involved. You could do this with iptables or using a proxy server such as squid. I think most people use iptables which is also your firewall. You will have to add another ethernet card so you can connect one to your lan and one to your modem. There is another option which I think is much easier. You could buy a cheap $29 router and connect it to your modem then connect both machines to it using patch cables (not crossover). You configure by using its ip which is usually 192.168.0.1. And if your lucky, your router comes with a wizard that will walk you through the setup. If not it's no harder than your network configs on linux. Keep in mind if you plan on opening ports to the internet, although a cheap router is very easy to setup, it doesn't offer the security that a full blown firewall such as iptables would.

 

[energiza]

Thanks. Yes, the way I'm requesting a web page from .5 is

http://192.168.0.1

and as I commented, .1 receives the packets (network analyzer). I found that http.conf by default has comments at the Apache Proxy section (clearly says "remove comments to enable proxy...&quot, so I uncommented that proxy section and "allow"ed 192.168.0.5 to "access" the http server since is "deny"ing to all.

-For those changes to actually take effect...-

Then rebooted(stop-start always produces some error when trying to browse after start httpd, and rebooting is the only way -in my case- to setup httpd ok).

Still, same situation, requesting http from .5 to .1 (

http://192.168.0.1

or

http://localhost.localdomain,

that is configured ok in ServerName, thanks) produces same effect in Network Analyzer, packets are transmitted and received BUT those from .1 to .5 carry the comment Destination Unreachable.

More things can be detected by the Network Analyzer of Linux. When in .5, I browse the Network icon to see the Workgroups and machines around, .1' shows all it is happening in the .5 machine, so the communication exists.

Yes I have a crossover cable connecting my 2 pc's AT THE MOMENT, and yes I will change that when adding the router;

Just a doubt:

I've installed those routers with that wizard that shows configuration page on the browser when typing the typical 192.168.0.1 (which will either force my ethercard at .1 to change its ip or change the router's instead) but I've done that only under Windows with the ip concepts handled so far herein, but no more than ip, subnet mask, gateway ip=router's ip, and that was it. ALL THIS REGARDING PHYSICAL COMMUNICATION WISE and leaving the security issues in a separate paragraph. Am I right?

Are you saying that it requires more considerations under linux -communication wise speaking?

If those considerations are related to the rules of the proxy, then we agree they are the security considerations that will restrict/allow physical communication as well but only from the security point of view, this means it's a one's conscious decision to allow or restrict, rather than the communication could be restricted because I forgot to configure something like a gateway address or some ip is not assigned. Right?

Well, I will appreciate the help to solve this thing of being ip-connected but with "Destination Unreachable". You know the ICMP handles the error messages of the IP layer, the Network Analyzer reports that ICMP says: "Source .1, Destination .5, Message: "Destination Unreachable", and such situation is mentioned in the "man icmp" as simply as "...one of the errors is DEST_UNREACH or so" (sorry if I perhaps twisted a couple of letters), but I haven't found what's the origin, there resides the answer, but I'm new in Linux.

Thanks very much again, awaiting for your kind ideas...