Server 2003 as a rip router

Hi all,

I am desperatly trying to make my W2003 server acting as a rip router.

I've followed all the steps MS (RRAS setup) is giving on the web site but it still not routing. Looking at the routing table everything's fine. I have all the routes present

Here's the setup:

Station1

(192.168.0.0)----W2003 Router----(192.168.1.0)

Station2

Quite simple huh?

Can ping interfaces that are on the same subnet, but Station1 cannot ping Station2. There are no ports or whatever filtering

Somebody has a clue or a procedure that I could try? Ah, forgot to mention: it is working when the router is working as a NAT router, that doesn't help --> RIP is not working

Any help greatly appreciated
Glenus

Find more posts tagged with

Comments

sprkymrk

How are the clients set up? What is their default gateway? Did you run the setup wizard and select network router? Is the firewall on or off on the server?

Just some random thoughts....

SanKuKaï

How are the clients set up? What is their default gateway?

Add and DG on both clients --> DHCP from server

Did you run the setup wizard and select network router?

Yes I ran the wizard. Is that correct to select VPN set up? There is no choice for router... What would you choose?

Is the firewall on or off on the server?

This I will check

Thanks for your reply

bighornsheep

In this case, there's no RIP routing, you only have 1 router, as long as both station1 and station2 uses the ip of the interface that's facing them as their default gateway, they should be able communicate.

SanKuKaï

bighornsheep wrote:

In this case, there's no RIP routing, you only have 1 router, as long as both station1 and station2 uses the ip of the interface that's facing them as their default gateway, they should be able communicate.

Fine. I know there is no routing with 1 router. But I tried with static routes, doesn't work neither. I suppose this is a set up problem but I am not (for the time being

) a W2003 expert and I can't solve that problem!

Thanks for your help guys

doom969

glenus wrote:

Fine. I know there is no routing with 1 router. But I tried with static routes, doesn't work neither. I suppose this is a set up problem but I am not (for the time being ) a W2003 expert and I can't solve that problem!

Actually there's routing, just no RIP.

Do a route print command in a dos window and show us the output so we can see what your routing table looks like.

sprkymrk

glenus wrote:

How are the clients set up? What is their default gateway?

Add and DG on both clients --> DHCP from server

Did you run the setup wizard and select network router?

Yes I ran the wizard. Is that correct to select VPN set up? There is no choice for router... What would you choose?

Is the firewall on or off on the server?

This I will check

Thanks for your reply

So on your W2K3 server, you do have 2 nics, correct? One for each network? And your clients using the nic facing them for their DG?

bighornsheep

doom969 wrote:

Actually there's routing, just no RIP.

Do a route print command in a dos window and show us the output so we can see what your routing table looks like.

Actually, there's no routing either, only routed routes.
Routing vs. routed protocols, remember?

doom969

bighornsheep wrote:

Actually, there's no routing either, only routed routes.
Routing vs. routed protocols, remember?

I dont mean to contradict you but i'm not sure I do . (I did not study ccna, so maybe thats why I dont get it.)

So, there will be packets routed from one network to antoher isnt that routing, plain and simple ?

I know theres no routing protocols, because there's only one router (who could he advertise to ?), but there's definitly routed protocols (ie.: IP, snmp, sntp, rpc, etc...) So as long as protocols are routed, there is routing right ?

Thx for your answer

doom969

(sry, sometimes my english sucks)

sprkymrk

bighornsheep wrote:

Actually, there's no routing either, only routed routes.
Routing vs. routed protocols, remember?

Just because no routing protocols are involved does not mean that there is no routing going on. A router that is aware of multiple networks (as in directly attached) does not need a routing protocol to route packets between those networks, and if it is passing traffic between those networks, it is indeed "routing".

bighornsheep

That's right....I meant to say that there is not only no rip routing, but there is no routing protocol that is used, routing is taking place through the routes between the interfaces.

sprkymrk

bighornsheep wrote:

That's right....I meant to say that there is not only no rip routing, but there is no routing protocol that is used, routing is taking place through the routes between the interfaces.

That makes more sense.

You had me and doom969 confused for a minute there!

Not speaking for doom, but I get confused rather easily.

bighornsheep

sprkymrk wrote:

Not speaking for doom, but I get confused rather easily.

No problem....I guess I have to watch the confusion as it comes with aging....btw..your birthday is coming up right?

sprkymrk

bighornsheep wrote:

sprkymrk wrote:

Not speaking for doom, but I get confused rather easily.

No problem....I guess I have to watch the confusion as it comes with aging....btw..your birthday is coming up right?

Yes, it's less than a year away. :P

In March actually - I'll be 40.

SanKuKaï

Ok, Ok, Ok...

Stop arguing there! As it is written everywhere, setting up a W2003 server is very easy, and it actually is!! I found the problem... Maybe you will laugh, maybe not.

By default the wizard sets up a VPN right? The solution to use your server as a simple router is: uncheck Enable security on the selected interface by setting up static packet filters.

Now it is working fine!

Hope this will help for my 291 next year

Thanks for your help
Glenus