Routing : A really simple question 1

[AllUserNamesAreTaken]

This question should be simple, yet I've become a retard overnight and can't figure out this little problem.

Ok, check out my network:

http://www.bradgate.co.uk/upload/jpg1.JPG

I am trying to get Server1 to browse the Internet. Simple?

Exodus has Windows Server 2003 R2 installed on it.

Can anyone give me the advice I'm looking for? - I've tried using static routes etc. I just must be doing something wrong like subnetting?

Regards,

Ian.

 

[AllUserNamesAreTaken]

The firewall as in 90.0.0.13 (Gateway)? Yes -

It runs Otisis Winproxy - which is a NAT program (If you didn't already know)

I'm just installing Windows 2003 Server on Exodus again, found some bits lying around so built up a new server, heh.

Give me 30 mins and I'll have the routing tables up.

 

[AllUserNamesAreTaken]

Right, let's start again.

I've got two networks.

Such as this:

One is on the 90.0.0.X range
One is on the 200.1.1.X range

Any PC on the 90.0.0.X range has no problem accessing the Internet, which is a Windows box on 90.0.0.13, using a NAT program called Winproxy.

A Windows 2003 Server box hosts the "route" between the two networks, called "Exodus".

Exodus has 2 static NIC IP's -

90.0.0.210 and 200.1.1.5

There is only 1 other PC on the 200.1.1.X subnet called "Server1" which is a DC. IP address:

200.1.1.1

So, here's the problem...

I can get any PC on the 90 subnet to ping anything on the 200 subnet, and visa versa. Internet works on any PC on the 90 subnet.
Internet does NOT work on "server1".
PC's on the 200 subnet and 90 subnet cannot do DNS lookups of each other. ie. I cannot ping "server1" but I can ping it's IP.

Here are the routing tables for Server1 and Exodus, respectively.

Server1:

Exodus:

- Routing is turned on on Exodus, but no static routes have been entered into the table, as I'm unsure what to do, so I've just left it turned on.

If anyone can advise me what to do here (except buy a router !) I'd be mostly grateful.

Or if anyone needs to know any other IP addresses etc, please, just ask.

Cheers,

Ian.

 

[tfg13]

I think on server1, you'll need a persistant route telling it where it needs to go.

route -p add 90.0.0.0 mask 255.0.0.0 200.1.1.5 metric 1

I could be wrong though. I've never actually tried to do something like this (without a router/bridge). Give it a try....

 

[PScottC]

It looks like everything is set up correctly. Can you ping from the FW to Server1? I believe that you are missing a route on the FW.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[Supergrrover]

Just an observation,
In Server1's routing table there is
90.0.0.0/24 gateway of 200.1.1.20
but the default gateway (0.0.0.0) is 200.1.1.5.
In Exodus' there is a
200.1.1.20 routed back to the loopback, but there is no 200.1.1.5.
It looks like the domain1 ip of Exodus is 200.1.1.20 and not 200.1.1.5. This would explain why you can get to the 90.0.0.0/24 and not out to the internet. Do an ipconfig on Exodus and double check the IPs and make sure DHCP didn't intervene.



Brent
Systems Engineer / Consultant
CCNP

 

[AllUserNamesAreTaken]

Yeah, you are right. I changed the gateway to .20 and it still doesn't work. Whethever I've got the correct forwarders etc on the DNS server now I don't know.

I guess what I'm really trying to say is that I don't really know if I've got every option correct - maybe there's something I'm missing, anyway.... I think I'm just going to bite the bullet and buy a router because this isn't working...

Thanks for everybodys help in the meantime.

 

[AllUserNamesAreTaken]

Ignore the above message, I've figured it.

Nobody told me I had to enter the IP address of my proxy server in Internet Explorer - LOL!

Amazing what a weekend of alcohol does to you..

Now it's working, thank's to all - now I've just gotta figure how to do DNS lookups !! heh!

 

[AllUserNamesAreTaken]

Ok sorted that too with a bit of playing about.

Seems all is well now.

Add your "local" domain in the DNS settings and put your DNS server IP address - Simple. (when you know how)

 

[PScottC]

Somehow I missed the fact that your FW was a proxy. Glad you found it.

Good Luck!

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers