file server with router

[kmfan]

I am trying to configure a file server on REDHAT 8.0....i have a windows XP client.....i am not able to ping the server from the client ...i think it may have something to do with the /etc/resolv.conf file....it contains the ip address of the router and nothing else....could someone please help???? thank you

[bmccarthy]

The resolv.conf shouldn't have anything to so with it. That's just used for name resolution by the linux box, which would in fact be your router if your using a standard cable/dsl modem.

On the server, perhaps are you bocking ICMP with iptables? do a service iptables stop and retry your ping.

I assume you have all your ip info and routing correct... right?

[kmfan]

could you please explain in further detail what i should do ....maybe step by step....i am quite the novice .....thank you very much for your help

[bmccarthy]

Well, starting from the beginning, did you set up any kind of ip configuration or are you relying on DHCP?

If you type in ifconfig at a prompt, you should get information on eth0, including ip address, gateway, statistics, etc. Run that command and repost the relative information... ip address and subnet mask.

Verify that your routing table is correct, type route at the prompt and post the output.

While your at it, you may as well do an ipconfig /all on the XP client and post that, (it's not always Linux's fault that things don't work! :)

After getting all that info, go to a command prompt, type in 'service iptables stop' (as root, by the way), then retry your ping.

Post all the results of the above.

[kmfan]

# ifconfig
eth0 inet addr: 192.168.1.101 Bcast: 192.168.1.255
Mask: 255.255.255.0

lo inet addr: 127.0.0.1 Mask: 255.0.0.0

# route

Kernal IP routing table
Destination / Gateway / Genmask
192.168.1.0 / * / 255.255.255.0
127.0.0.1 / * / 255.0.0.0
default / 192.168.1.1 / 0.0.0.0

# ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : win-client
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ri.cox.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-03-47-DC-93-AD
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.9.16.30
68.13.16.30
Lease Obtained. . . . . . . . . . : Sunday, November 17, 2002 1:05:54 PM

Lease Expires . . . . . . . . . . : Monday, November 18, 2002 1:05:54 PM

what does service iptables stop ...do??? what are iptables.....???? thanx for your help

[kmfan]

i did the command:

service iptables stop

it works now

I am assumming that i stopped some sort of firewall....how can i reconfigure the firewall so it will allow me to connect but not totally allowing complete access....if this is the case????

[bmccarthy]

Well, that looks ok so far. So you can't ping the linux box from the wxp box, right?

iptables is the new packet filtering/firewall configuration program for linux. If you set up the firewall configuration to be high in Redhat, I believe that it sets uptables up to block anything incoming, including ICMP (which is used for pings). So, I would suggest performing a "service iptables stop" to shutdown any firewall rules you may have. After doing so, perform a "iptables --list", you should see something almost identical to below:

[root@mc1 bob]# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Then try to ping the linux box again from the wxp machine.

If this still fails, try pinging from both machines the following list:
ping 192.168.1.100
ping 192.168.1.101
ping 192.168.1.1
ping make-up-some-host-outside-your-network.com

This way we can try to see just who and what each machine can talk to.

[bmccarthy]

Our posts crossed paths...

OK, that answers the problem. iptables is blocking ICMP.

If you are just using this box for internal use, and you already have some sort of cable/dsl router (which suffices just fine as a firewall for all of us not housing millions of $$ behind our firewalls), and you feel comfortable doing so, then I would suggest just stopping iptables.

run 'chkconfig iptables off' to stop iptables from starting up on the next reboot.

That should take care of you, just be advised, your linux machine has no firewall now. Like I said, that should be ok behind your router, but you should still just be aware of that.

[kmfan]

ok...thanx for your help....just one last question....there is no way to configure the firewall on the linux box to allow the connection without shutting it off?????

thanx again for your help

[bmccarthy]

Oh, absolutely. But then you are talking about configuring your entire iptables system, which can be a somewhat daunting. There are all kinds of utilities to aid in this process, though I would always suggest trying the "hard way" first, then going to the gui helper utilities.

Go to google and type in 'iptables sample scripts configure'. I just found several pages with loads of information on setting up iptables. Read all those, screw around with iptables for a while, and when you get lost again, repost.

[kmfan]

hey thanx alot you've been a great help......kudos to you for being so informative....thanx

[logf]

This is my problem. Though I am using Windows XP Pro trying to ping a RH 7.3 box (fresh load). But it work ping from WXP -> RH 7.3, or even RH 7.3 -> WXP:(
Though I can connect to the internet on the RH 7.3 box.
I tan lokkit (I think it was) from Gnome, and set it up to allow ALL hosts via Eth1, and to block all from Eth0 (I run 2 NICs - setting out a gateway.) - Eth0: 192.168.0.161, Eth1: 192.168.0.162.
When I try to ping out the ICMP requests route through the Eth1, but still tell me it's unreachable.
When I try to ping into the RH box it tells me "unreachable"

I have also went to Bash and ran "service iptables stop" without luck. Any idea?

P.S. I have static IPs on the machines for internal LAN use (all using 255.255.255.0, with the same Gateway 192.168.0.254). So there is NO DHCP running (not even the wireless modem has DHCP anymore). Also this worked just fine when I had RH 7.0 loaded, but everysince I ran a fresh reloaded (LLF/R) It hasn't worked:(

[kmfan]

the problem I was having was that i could not ping the Linux box from the WXP box.....that problem was solved by using service iptables stop

you may have a problem with your DNS/DHCP/IP configuration if shutting down the iptables is not working

here is a link that may help

http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf

good luck

[logf]

I was thinking along the lines of DNS/IP Problems, I will look into it.

Logan

[bmccarthy]

Could be all kinds of things. Why does both eth0 and eth1 have addresses on the same subnet? If your routing table shows all data on the 192.168.0.0/24 going through eth0 (which is most likely) then you won't get anything going out.

So, begin with posting ifconfig and route info, as shown in previous posts. While your at it, since it sounds like you probably have that set up ok so far (I just want it to reference your setup), lets take a look at your iptables configuration. Post your sysconfig/iptables or whatever else you use to start iptables (startup script, lokkit config, whatever).