Computing.Net > Forums > Windows NT > NT as a router ... again

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

NT as a router ... again

Reply to Message Icon

Name: Ana Cristina Almeida
Date: February 24, 2000 at 05:04:05 Pacific
Comment:

Hi all!
I'm trying to set a NT as a router, with 2 NIC's.
One NIC has the IP 192.168.10.30, mask 255.255.255.0. Another, has the IP 192.168.20.1, mask 255.255.255.0, gateway 192.168.10.30 (the first NIC).
The option IP FORWARD is enabled.
The workstations, in subnet 192.168.20.0, have, as gateway, the NIC 192.168.20.1. They can ping the NIC 192.168.10.30, but can't ping anothers hosts in subnet 192.168.10.0.
I set static routes like,
route -p add 192.168.10.0 mask 255.255.255.0 192.168.10.30, but it seems not working.
If I do a traceroute from a workstation in subnet 192.168.20.0, it passes 192.168.20.1, but stops... there was no response from the NIC 192.168.10.30.
I don't know what is wrong.
Can you help me???
Best regards.

Ps.1: Mu NT is version 4.0, and SP 5.
Ps.2: sorry by my english...:-)



Sponsored Link
Ads by Google

Response Number 1
Name: Anthony
Date: February 24, 2000 at 06:26:26 Pacific
Reply:

You should not get a response from the second nic when you do your trace route. You will only get a response from the first nic that it passes through. You said that you tried to ping a workstation on the 192.168.10.0 network from a workstation on the 192.168.20.0 network right? Do the hosts on network 192.168.10.0 have 192.168.10.30 set up as their default gateway? If they don't here is what is happening. A host on network 192.168.20.0 sends out a ping message. This will be directed at it's default gateway of 192.168.20.1. The first NIC will recieve it and pass it to the second NIC of 192.168.10.30. The second NIC will broadcast it on it's subnet because it will know that the target host is on it's subnet based on the dest address and net mask. The target host will hear the broadcast that is addressed to it and it will issue a reply. This is where the trouble is... It will direct the reply at it's default gateway. It will also broadcast it on the local subnet but routers ignore broadcasts. If the default gateway is not 192.168.10.30 then it will go to whatever the address is of what if does have as configured for the default gateway... ie a differnet router. Now this router will examine the packet and try to route it accordingly. If that router doesn't have a route entry pointing back at 192.168.10.30 then the packets will be lost. On a Cisco router the entry would look something like this: ip route 192.168.10.0 255.255.255.0 192.168.10.30. So I believe this is why your pings are not working. It sounds like the NT computer you set up is correct.


0

Response Number 2
Name: De Carver
Date: February 24, 2000 at 06:36:19 Pacific
Reply:

I will try to help; Try setting your gateway to the proxy servers addy or if you have none leave it blank

Does that help?


0

Response Number 3
Name: Jimmy Xiao
Date: February 24, 2000 at 10:37:28 Pacific
Reply:

basicly you are connecting two subnets together via a NT server, in order to have hosts in different subnet to communicate, you could have two different gateways to default their packets to it's gateway, and also you could have only one gateway.
example:IP address 192.168.10.30 mask 255.255.255.0 you can make the gateway as 192.168.10.210
the 2nd NIC, you could set the gateway as 192.168.20.210 or leave that blank.
Anyhow, you have to have RIP installed as routing protocol besides TCP/IP or any other protocols.


0

Response Number 4
Name: Anthony
Date: February 24, 2000 at 11:59:54 Pacific
Reply:

You don't have to use RIP that is only if you want your routes to be dynamic. Static routing will work just fine in this case as long as the routers upstream have static route entries for the 192.168.10.0 network.


0

Response Number 5
Name: Ana
Date: February 25, 2000 at 04:15:10 Pacific
Reply:

I did the following:
Put another NT server in subnet 192.168.10.0, with IP 192.168.10.8, default gateway 192.168.10.30. I added the static route : 192.168.20.0 mask 255.255.255.0 192.168 10.30.
In the NT server, acting as a router, I set the NIC 192.168.10.30, with default gateway, the other NIC 192.168.20.1. And, the NIC 192.168.20.1, has as default gateway, the 192.168.10.30.
And tried to ping a workstation in subnet 192.168.20.0, from the NT server 192.168.10.8. It didn't worked. I can ping the NIC 192.168.20.1, but can't ping any host in subnet 192.168.20.0....

I think NT is not good enough to work as a server. I'll try to set a linux server... I think it will work better...

Thanks a lot for your help...

Best regards...

Ana ;-)


0

Related Posts

See More



Response Number 6
Name: leon
Date: February 27, 2000 at 13:11:43 Pacific
Reply:

i set up a wins server and dhcp. both nics refering to themselfs as the gateway. it works fine


0

Sponsored Link
Ads by Google
Reply to Message Icon

shutdown problem Right click



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows NT Forum Home


Sponsored links

Ads by Google


Results for: NT as a router ... again

Windows NT as a router??? www.computing.net/answers/windows-nt/windows-nt-as-a-router/22605.html

how to configure NT server as a router www.computing.net/answers/windows-nt/how-to-configure-nt-server-as-a-router/13582.html

Seting Up NT Server Box as a Router www.computing.net/answers/windows-nt/seting-up-nt-server-box-as-a-router/9280.html