If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

In this figure, I want to get the Windows Laptop to resolve an address from the DHCP Ubuntu Server. What I have done is installed dhcp3 (apt-get install dhcp3...) and then tried to do things the way they did on http://ubuntuguide.org/#installdhcpserver
, I used eth0 for the interface that will serve requests like they did, when it came to the second part of the dhcp.conf I commented everything like they did. However, on the second part I changed things to fit my situation, so it looks like this...

I have both eth0 and eth2 active on my Network Settings and am able to connect to the internet from the Linux Box, however (needless to say) my Windows XP Laptop behind my DHCP Server can't get an IP address

I appreciate any help greatly, I hope to get this running so I can get to the next phase of my little project!

The real question is not whether peace can be obtained, but whether or not mankind is mature enough for it...

So I was like, nice... and then turned on my Windows Laptop to see if it gets an IP and it does, it comes up with 10.0.0.99 with the default gateway as 10.0.0.1.

Unfortunately, even though it grabs an IP it still cannot get to the internet, I can't even ping 10.0.0.1 (100% packet loss) niether can the server get to the internet. It keeps wanting to use the eth0 interface as the default gateway and not eth2?

Any advice? Thanks a bunch!

The real question is not whether peace can be obtained, but whether or not mankind is mature enough for it...

3. Routing. Check with "route" the routing table for the various interfaces.
Eth0 and Eth2 should know what to do with 10.0.0.*, 192.168.0.*
(and 0.0.0.0, default). Check [1-3] for further information.

Your notion is correct, that is exactly what I want to do with one minor correction, A.eth0=10.0.0.1 (DHCP bound) not 100.0.0.1 (but I'll assume that was a simple mis-type).

In my network interfaces I commented the bottom part with the gateway and that seemed to be able to get the DHCP server to now connect to the internet again. The conputer now sees eth2 as the default gateway, which is good because eth2 is outgoing to the internet.

Now as for pinging, I can ping 192.168.0.1, 10.0.0.99, www.google.com, 10.0.0.1, and 127.0.0.1. One weird thing though is that after about 10 minuites of reloading the network I will not be able to ping either of those addresses (with the exception of 127.0.0.1), however, if I reload the network interfaces 'sudo /etc/init.d/networking restart', it will work again. (Just thought that was weird).

On the 10.0.0.99 Laptop I can ping 10.0.0.1, 10.0.0.99, and 192.168.0.102 but nothing outside that such as 192.168.0.1.

That seems, to be ok, but then again I'm new at this. I'm thinking that the problem must be that 192.168.0.102 (eth2) is not properly routing the packets to 192.168.0.1 (the router) Thanks for your insight.

The real question is not whether peace can be obtained, but whether or not mankind is mature enough for it...

I'm really thinking it has something to do with eth2 not forwarding the requests to the real router (192.168.0.1). Mainly, because my Laptop can ping everything under the sun except anything outside eth2 (192.168.0.102).

Anyone have a clue how to fix this? Thanks I appreciate all the excellent help!

The real question is not whether peace can be obtained, but whether or not mankind is mature enough for it...

Thanks for the pinging information. Based on this, I strongly suspect
you have forgotten to add routing information to your D-Link Router
(192.168.0.1).

Add routing information for the network 10.0.0.0/24 to your D-Link
Router and your problem will be solved (99% sure ). The D-Link
Router should sent packets for 10.0.0.0/24 to 192.168.0.102.

Reason: You can reach A.eth2 from B. If you want to ping any other
host in 192.168.0.0/24 except 192.168.0.102, on that particular
host, routing information are not available, therefore sent to the standard
gateway 192.168.0.1, which also does not know what to do.

Cheers

If the only tool you have is a hammer, you tend to see every problem as a nail.
(Abraham Maslow, Psychologist, 1908-70)

I am updateing this thread in case any one ever has the same difficulties that I had. However, I would first like to humbly thanks sec_ware, for whom without I would be totally lost on this.

Sec_ware's last post about the router being the issue would have been correct, however the router I was using (the D-Link) did not support static routes (a quick call to technical support confirmed this). Afterwards, sec_ware and I exchanged a total of 13 PMs trying to get this to work! And eventually we got it working just great!

Here's the short version of how we got this to work (without all the technical hurdles),

We needed a way for the D-Link router to think that the data from 10.0.0.99 was coming from 192.168.0.102 so it wouldn't get confused with the packet IP. Then we needed a way for 192.168.0.102 to be able to figure out how to forward the packets on to thier original sender on the alternate LAN. Setting up a proxy server did the trick just perfectly...

After this was done, I was finally able to access the internet via 10.0.0.99 by sucessfully doing a tracert to 194.109.137.218 (www.aboutdebian.com) however, when I tried doing a tracert to www.aboutdebian.com using it's domain name, no dice. This was obviously because something was wrong with the 10.0.0.99's DNS settings.

The solution to this in my case was to build a basic LAN, DNS server on 192.168.0.102. Which may sound difficult, but was probly one of the most easiest things I have ever done reguarding this project.