Windows Forum

Ask something
Discussion Locked

Routing with Windows 2000

0 helpful
5 replies

by danerdo

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have installed two NICs with two private IPs. One is 192.168.40.1 that is intended for my internal network. The second is 192.168.100.1 for another segment that connects to a cisco router that goes to the internet.

This is being tested within the above conditions for a lab session. Eventually, I will run this scenario where the 192.168.100.1 segment will go directly to a DSL router. I am doing this to ensure all traffic is controlled through the Windows server versus directly to the dsl router.

Under this lab, I have attempted to use the wizard from RRAS to connect with a network to network and internet connection server using NAT (won't work I know).

At the server after RRAS is configured, I can ping either side of the segments with no problem. However, on the 192.168.100.1 segment, I am unable to ping beyond the far side of my Cisco router that connects to the Internet.

On the 192.168.40.1 side, my connected test workstation can ping the Windows 2000 server with no problems. However, there is no traffic going across the nics with routing.

Any suggestions would be appreciated.

5 replies

by frobo

Hi ,

are U shure that the default Gateway on both Nic?s are configured right ? If you want that all traffic goes from inside to outside than look at routing table with Route print.
The entry for 0.0.0.0 should point on the nic for your DSL-router.

Frobo

by mshavrov

To have routing in this scenario your DSL router should have ethernet interface configured with address in 172.168.100.0 segment. Another way, if you don't have access to DSL router, is to configure ISP-provided IP address to "external" NIC. For sure your "external" NIC should have default gateway pointing to ethernet interface of DSL router.

This discussion is closed to new replies.