well...does that win-box have an ip-adress ?

otherwise give it a static like 192.168.0.5 and try to ping ?

egag

At the moment I using CAT5 5e patch cable, which is what I'm using on eth0 to my internet router. I've also check the netcards and they're working OK.

I already tried giving the win-box a static IP, but there is still no ping. The winbox is now set up to automatically receive DHCP. Either way I should be able to ping the server from the workstation right.?

Is there any 'dummy' test that I can type in from the linux command prompt that would show an error.?

strange thing....

i think your win-box needs an ip. to ping it ( what command would you use ? ping < adress> )

you could try " #ping -b 192.168.0.255 " ( broadcast ) to see if there's any response.

and patch cables are oke.. if the leds are burning there should be a connection possible.

edit: also try " #ping -I eth1 < adress> "

egag

I finally managed to find the problem. It was a mixture of cables and firewalls. I connected 2 new cables and dropped the firewall on both the server and the workstation. After doing this I could ping both machines an obtain an IP from the server.

My next step is to configure an IPtables firewall that will allow access to the new subnet and function as a NAT. My current working dhcpd.conf is now:

ddns-update-style ad-hoc;

subnet 192.168.1.0 netmask 255.255.255.128 {
range 192.168.1.11 192.168.1.50;
option routers 192.168.1.1;
option domain-name-servers 193.162.xxx.xxx, 194.239.xxx.xxx;
max-lease-time 86400000;
min-lease-time 900;
default-lease-time 864000;
}

Any suggestions for a simple NAT firewall which allows users on the eth1 LAN to access the internet through eth0.?