[SOLVED] RHEL 5 server / client problem

Deathkarr · 02-03-2010, 07:17 PM

I using a network switch so yes. When i ping the client from the server i get host unreachable. Though when I ping the client I get do u want to ping to broadcast then -b after typing -b we receive a List of commands. Would it make it easier if I listed my config settings for dhcp, ifconfig, static ip and network switch details.

DrLove73 · 02-04-2010, 08:31 AM

Yes please do. And router/firewall that you said you have on that Linux network. So list the settings for ALL units and devices that are connected to that Linux network in any way. Also, please list IP settings from your Windows that has access to the Internet.

Also:

1. Are Windows and Linux network in the same building/office?
2. Do you use same internet access/device for both Windows and Linux networks? If not, please write details.

You said that you have setup clients to use LDAP from 192.168.0.1. If you can not ping 192.168.0.1 from clients, than please try the manual settings I posted in post #8. It is for testing purposes, you can get it back latter.

Deathkarr · 02-04-2010, 10:56 PM

Here's the configuration files for the server

dhcpd
authoritative;
ddns-update-style interim;
#ignore client-updates;
default-lease-time 21600;
max-lease-time 43200;

option routers 10.112.89.207;
option broadcast-address 192.168.0.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.0.1;

subnet 192.168.0.0 netmask 255.255.255.0 {

range 192.168.0.104 192.168.0.254;

host bart {
hardware ethernet 00:24:81:99:89:8B;
fixed-address 192.168.0.115;
}

host marge {
hardware ethernet 00:11:5B:5C:B1:AB;
fixed-address 192.168.0.116;
}
host test {
hardware ethernet 00:0C:F1:AB:42:46;
fixed-address 192.168.0.117;
}

}

ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:80:0C:0F6
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:80ff:fe0c:fd6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:156 errors:0 dropped:0 overruns:0 frame:0
TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22339 (21.8 KiB) TX bytes:24287 (23.7 KiB)
Interrupt:185 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1943 errors:0 dropped:0 overruns:0 frame:0
TX packets:1943 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3328813 (3.1 MiB) TX bytes:3328813 (3.1 MiB)

Static IP
Static set IP addresses:

Address: 192.168.0.1
Subnet mask: 255.255.255.0
Default gateway address: 192.168.0.1/25

Our network switch is a fairly large one so it has it's own ip which is 10.112.89.207. We do have a smaller one that is 5 ports it's a netgear switch. We have no firewall it's just the 2 network switches as there is going to be no internet on the machines and the machines are all LAN based connection.

Configuration for client machine:

ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:F1:AB:42:46
inet addr:192.168.0.117 Bcast:192.168.0.1 Mask:255.255.255.0
inet6 addr: fe80::20c:f1ff:feab:4246/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:227 errors:0 dropped:0 overruns:0 frame:0
TX packets:397 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24389 (23.8 KiB) TX bytes:51340 (50.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7594 errors:0 dropped:0 overruns:0 frame:0
TX packets:7594 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9962572 (9.5 MiB) TX bytes:9962572 (9.5 MiB)

Thanks for all your help

DrLove73 · 02-05-2010, 07:26 AM

First of all, following option has no function in 192.168.0.0/24 subnet:

Code:

option routers 10.112.89.207;

Following option is the reason DHCP clients can not ping server:

Code:

option broadcast-address 192.168.0.1;

change it to

Code:

option broadcast-address 192.168.0.255;

Also, I strongly suggest that you move first 3 "option" rows inside actual subnet statement.

Next, you have set fixed IP's for those 3 clients inside the DHCP range which is an error. Fixed IP's must not be the part of the dynamic range in that subnet, so in your case, IP's in range 104-254 must be avoided for fixed IP's.

Resulting dhcpd.conf is:

Code:

authoritative;
ddns-update-style interim;
#ignore client-updates;
default-lease-time 21600;
max-lease-time 43200;

option domain-name-servers 192.168.0.1;

subnet 192.168.0.0 netmask 255.255.255.0 {

option routers 10.112.89.207;
option broadcast-address 192.168.0.255;
option subnet-mask 255.255.255.0;
range 192.168.0.104 192.168.0.254;


host bart {
hardware ethernet 00:24:81:99:89:8B;
fixed-address 192.168.0.101;
}

host marge {
hardware ethernet 00:11:5B:5C:B1:AB;
fixed-address 192.168.0.102;
}
host test {
hardware ethernet 00:0C:F1:AB:42:46;
fixed-address 192.168.0.103;
}


}

Also, you server's gateway IP has an error. If you set gateway address, you must not use broadcast on the end. And gateway IP can not be the actual IP of that PC, so either remove it all together, or change it to something inside the subnet but not on the dhcp range, like "192.168.0.100" and then if you need to connect this subnet with some other subnet, you will have to have a router that will have that IP and be connected to that other network.

Use this subnet calculator for any further setups.

Deathkarr · 02-05-2010, 08:52 PM

Thanks so much. I won't have access to the server again for a few days but i shall be sure to change it. Thanks a lot

Deathkarr · 02-07-2010, 09:21 PM

Ok Now When I Attempt To Restart DHCPD It Says DCHPD Faild the Error Was: (No Code Displays) I Also Have Realised Both Machines Have The Same Hostname Could This Be The Problem? Also The Fixed IP's Are No Longer Needed As his Was Just A Test To See Whether It Would Work

DrLove73 · 02-08-2010, 04:33 AM

The possible problem could be that you copy/past-ed from windows machine, and there is a known problem that Windows and Unix/Linux EndOfLine characters are not compatible. You need to type config files in Linux environment.

Other possibility is that I errored somewhere, in which case you need to revert to your original config and then just fix IP problems. I hope you bade backup of that file, I forgot to warn you to make one.

Deathkarr · 02-09-2010, 04:36 PM

We did copy and paste from windows though we retyped it in the linux environment. It still didn't work. I din't make a backup file. Here's what the subnet calculator returned for us.

Address: 192.168.0.1 11000000.10101000.00000000 .00000001Netmask: 255.255.255.0 = 24 11111111.11111111.11111111 .00000000Wildcard: 0.0.0.255 00000000.00000000.00000000 .11111111=>
Network: 192.168.0.0/24 11000000.10101000.00000000 .00000000 (Class C)Broadcast: 192.168.0.255 11000000.10101000.00000000 .11111111HostMin: 192.168.0.1 11000000.10101000.00000000 .00000001HostMax: 192.168.0.254 11000000.10101000.00000000 .11111110Hosts/Net: 254 (Private Internet)

DrLove73 · 02-09-2010, 04:49 PM

I meant that you first return all settings to the condition you had before any editing (the one in your post #18), check if everything is functioning, and then to just implement IP/subnet changes I wrote without reshuffling option rows.

Like this :

Code:

dhcpd
authoritative;
ddns-update-style interim;
#ignore client-updates;
default-lease-time 21600;
max-lease-time 43200;


option routers 10.112.89.207;
option broadcast-address 192.168.0.255;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.0.1;


subnet 192.168.0.0 netmask 255.255.255.0 {

range 192.168.0.104 192.168.0.254;


host bart {
hardware ethernet 00:24:81:99:89:8B;
fixed-address 192.168.0.101;
}

host marge {
hardware ethernet 00:11:5B:5C:B1:AB;
fixed-address 192.168.0.102;
}
host test {
hardware ethernet 00:0C:F1:AB:42:46;
fixed-address 192.168.0.103;
}

for the resulting script after all changes.

But do changes one by one and test after each change apply and test. That way you can catch the error and fix it.

Deathkarr · 02-11-2010, 01:22 AM

It works now. Thank you so much for your help. Do you know of any good how tos that I could use as for future reference so as to not make the same mistake again.

DrLove73 · 02-11-2010, 03:07 AM

https://www.isc.org/software/dhcp/documentation