Your static IP and the gateway are on two different subnets. The gateway IP needs to be on the 192.168.0.0/24 subnet or you need to re-IP the server to be on the 10.10.0.0/?? subnet.

Thankyou very much. I'll try it tomorrow and let you know how everything goes.

You definitely need to correct that Gateway IP address. However, just as a FYI, if you're pinging any host in your network say 192.168.0.2, it should have pinged - gateway IP address is irrelevant to reach a machine which is within your subnet.

Sorry I haven't replied for ages but I have been doing a lot of configurations on the server like openldap and stuff like that. Changed it and just to clarify does that mean that I would now have to ping 192.168.0.1/24. Plus if i was testing to see if i could mount an nfs folder on a client machine would i have to change the following command:

mount 192.168.0.1:/home /home/ to

mount 192.168.0.1/24:/home /home/

Can you now ping Server from Client and vice versa?

If you can, setting up nfs share and accessing it from Client is not to much complicated. I even set up automounting nfs share for my notebook.

No. the ping returns network host unreachable or it returns ping -b. Which is why i thought you would need to add the /24 .

Then you need to learn a networking one-on-one. I sugest you visit www.tldp.org and read few manuals and howto's

Using the 192.168.0.x subnet, set it this way:
Server:
IP: 192.168.0.1
netmask 255.255.255.0
gateway: 192.168.0.Y (where Y is numer of your network gateway/router to get outside of that subnet). this not necessary for now.

Client: 192.168.0.2
netmask 255.255.255.0
gateway: 192.168.0.Y (where Y is numer of your network gateway/router to get outside of that subnet). this not necessary for now.

Run as root "service network restart" on the Server (and on the client if you use Linux).

Now to ping client from server PC, run: "ping 192.168.0.2", and from the client type "ping 192.168.0.1". If you are not getting anything, you have something wrongly setup, either software or hardware.

Be aware that if you connect 2 PC's directly, without a network switch, you need to use crossover LAN cable.

Accidentally posted twice ignore this reply

My server is a dhcp server so I shouldn't neet to make a static ip for my client. Wouldn't this mean that my ip address for the server 192.168.0.1 will also be the Default gateway address. The network will have no internet

Yes, if your server acts as DHCP server PROPERLY, and you DO NOT have any OTHER DHCP server plugged in that physical network, it will. But since you are unable to ping between client and server, I suggest you set it up manually as I told you, so we can debug this problem.

Removing unknown variables is the best way to do that, and your networking knowledge is so low I can not rely you set that DHCP server properly.

By the way, 192.168.0.1/24 (or 192.168.0.1/255.255.255.0) is not proper IP address to use, that is logical representation of the IP, meaning IP/netmask since /24 replaces "255.255.255.0"

I think that my option router in the dhcpd.conf file might not be 192.168.0.1. Though if it was I would turn off the dhcp service and make the client and server both static using the settings you previously said. But would I leave the gateway blank or should I put in 192.168.0.1 for both server and client.

Both of my machines are Linux. I'm just using windows as a way to communicate to you guys.

Then take a look at your Network settings in Windows and just change IP for both server and client. You can use last number in IP address from 1-254, but I recommend 200 (192.168.1.200) for server and 201 (192.168.1.200) for client. Also, if you use router with DHCP, then both Linux units should be able to access internet when left in Automatic IP mode.

There is a possibility that you overlap 192.168.0.1 on your server with routers IP, so change IP's for both Linux-es as above and use gateway that Windows set's on his connection.

I'm not understanding. Should i change option routers to server ip address. I also need to keep the server ip at 192.168.0.1 cause that's what i have my clients connect to for ldap.

Let me explain my network a bit better I have about 3 client machines all running linux and one server running rhel5. I have a network switch which connects to a larger switch and I can't get internet on the machines. I use the Windows machines to get internet help like through forums. The windows machines are not connected to the network

Umph. What is the IP of the router/gateway facing internet that is connected to your Linux network? If it is 192.168.0.1, then you have problem since the same IP is used for server.

Something bothers me. DO you or don't you have connection between clients and Server? Can you ping Server from clients? You are too much confusing to understand.