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.

 

[tfg13]

Take a look at your route table (from the command line, route print). This may point you in the right direction.

Another area, and I'm sure you've already checked this, ensure you only have 1 gateway (preferably the router's gateway address).

 

[msworld]

In an internetworking environment, make sure the next router can route back. This search result may help,

internetworking routing
Q: Internetworking Routing. Hello, need your help on this one, please. Setting: Network A: 192.168.1.0 mask 255.255.255.0 Win2k VPN Server A is: 192.168.1.5 ...

http://www.chicagotech.net/Q&A/vpn18.htm

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

 

[AllUserNamesAreTaken]

So my route table should be?

Destination 90.0.0.13
Subnet Mask 255.255.255.0
Gateway 192.168.0.21

?

 

[TheLad]

What default gateway have you got set on Server1?

--------------------------------------------------------------------------
"Who is General Failure and what is he doing on my computer?"
--------------------------------------------------------------------------

 

[AllUserNamesAreTaken]

Under the Connection Properties :

IP address: 192.168.1.1
Subnet Mask: 255.255.255.0
Default Gateway: none

Preferred DNS server: 192.168.1.1
Alternate DNS server: none

 

[TheLad]

OK, from Server1 can you ping 192.168.1.21 and get a valid response? If not, try setting the default gateway on Server1 to 192.168.1.21, If you get a valid response then you will need to configure a route on Exodus to allow traffic to go from the 192 NIC to the 90 NIC otherwise it doesn't know where to go.

--------------------------------------------------------------------------
"Who is General Failure and what is he doing on my computer?"
--------------------------------------------------------------------------

 

[AllUserNamesAreTaken]

Yes, I can get a valid response without entering anything into the default gateway in the NIC card - That's correct since it's on the same network.

In the Routing and Remote Access on Exodus, it says add static route.

Now it says:

Interface: NIC 1 or 2. (names of the connections)

Destination:
Network Mask:
Gateway:
Metric:

Can you help with the above details ?

 

[TheLad]

I would have thought that your route command on Exodus would need to look something like this (assuming NIC1 is the 192 card)

ROUTE ADD 90.0.0.210 MASK 255.255.255.0 90.0.0.210 METRIC 1 IF 1

Sorry if this is not right, maybe someone with more experience with routes can advise better.

--------------------------------------------------------------------------
"Who is General Failure and what is he doing on my computer?"
--------------------------------------------------------------------------

 

[AllUserNamesAreTaken]

The route addition failed: The specified mask parameter is invalid. <Destination & Mask> !=Destination"

That's the above error I get in DOS.

This is really infuriating!!!

 

[TheLad]

Try a mask of 255.0.0.0 - just a case of trial and error...

--------------------------------------------------------------------------
"Who is General Failure and what is he doing on my computer?"
--------------------------------------------------------------------------

 

[AllUserNamesAreTaken]

Trust me, I've trialed and error'd EVERY combination I can think of.

That doesn't work either, yet the service for the Routing and Remote Access is definately working. It's a clean install of Windows 2003 Server, so it MUST BE something I am doing wrong - Yet I can't find any walkthroughs on the net.

*sigh.

 

[TheLad]

Yeah I hate routes too lol. Assuming you have eliminated possible firewall issues on the server(s), you could always try the following:

Th NIC on the 90 network should have a default gateway and a mask set. Take this information and issue your route command as follows (replacing the details in <> with the required information:

ROUTE ADD <default gatway> MASK <mask> 90.0.0.210 METRIC 1 IF 1


--------------------------------------------------------------------------
"Who is General Failure and what is he doing on my computer?"
--------------------------------------------------------------------------

 

[AllUserNamesAreTaken]

Yes, both Server1 and Exodus have a fresh installation of Windows 2003 Standard R2 Edition installed. No firewalls, no third party software at all. No firewalls.

The NIC on the 90 Network has the following details:

IP address: 90.0.0.210
Subnet Mask: 255.255.255.0
Default Gateway: 90.0.0.13

Preferred DNS Server: 90.0.0.150
Alternate DNS Server: 192.168.1.1

Exodus works fine on the Internet (using the Gateway of 90.0.0.13, of course) and can ping both DNS servers, 90.0.0.150 and 192.168.1.1, so there's nothing actually wrong with the topology of the Network. The problem purely lies in the routing tables.

ROUTE ADD 90.0.0.13 MASK 255.255.255.0 90.0.0.210 METRIC 1 IF 1 - gives me the same error as before ("The route addition failed: The specified mask parameter is invalid. <Destination & Mask> !=Destination")

 

[PScottC]

Have you enabled RRAS on EXODUS? Windows Server does not bridge networks by default.

If you are going to do a static route to the internet, the command should be:
ROUTE ADD 0.0.0.0 MASK 255.255.255.255 90.0.0.13

But, you should already have that route because your default GW is set on the 90.0 NIC.

Also, the FW will need a route back. A static should be set up there saying that to get to 192.168.1.0/255.255.255.0 route packets to 90.0.0.210.

You will still need RRAS set up first.

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

 

[AllUserNamesAreTaken]

Now I'm just even more confused.

Yes RRAS is set up - probably not correctly I presume.

I have managed to get the Server1 and any PC on the 90 network to ping each other, still the Internet does not work.

I thought the Internet was 0.0.0.0 mask 0.0.0.0 <Interface> ?

I can ping the firewall on the normal 90 subnet, but not on the 192.168.0.1 subnet, ah, probably needs a route-back like you said, heh.

 

[AllUserNamesAreTaken]

Right.. ok..

Figured out (I think) how to route packets across subnets. I've got all PC's talking to all PC's on either network - However DNS names do not work. I can just add them manually, so that's not a problem.

However, I still can't get Internet Access to work on the 192.168.1.0 subnet. Only on the 90.0.0.0 subnet does it work (router IP 90.0.0.13).

Damn... any ideas? I can't even ping google !

 

[PScottC]

Ok.. run the following command on exodus and post the results...

route print


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

 

[AllUserNamesAreTaken]

Obviously I know buying a router would be the easiet option, but to do it manually feels as though I've actually accomplished something - now...

While I was playing around last night, my proxy server died at work, and I had no spare PC's to put a temporary server up, so I had to use Exodus... lol.

..Waiting for my new server to arrive on Monday then I'll set up Exodus again and do a route print.

Thanks for everybodys help in the meantime.

 

[PScottC]

Oh... One more question... Is your firewall a Windows box or something else?

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