Discussion Locked

NT Server Routing Problem

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

I am trying to set up an NT Server with Proxy Server and NAI's WebShield to expunge any viruses from incoming e-mails before they reach the users's desktops. My problem has to do with NT Routing. I have two NICS in the machine with the follwing Information:

3COM Etherlink 177.176.50.3, 255.255.0.0, 177.176.50.2; 3COM 3C905B 177.175.50.3, 255.255.0.0

I have IP Forwarding turned on. Currently I'm using static routing, i.e., I have not installed RIP protocol. The default Routing Table is as follows:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 01 02 cd 5f 2d ...... 3Com EtherLink PCI
0x3 ...00 a0 24 1a 5d 71 ...... ELNK3 Ethernet Adapter.

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 177.176.50.2 177.176.50.3 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
177.175.0.0 255.255.0.0 177.175.50.3 177.175.50.3 1
177.175.50.3 255.255.255.255 127.0.0.1 127.0.0.1 1
177.175.255.255 255.255.255.255 177.175.50.3 177.175.50.3 1
177.176.0.0 255.255.0.0 177.176.50.3 177.176.50.3 1
177.176.50.3 255.255.255.255 127.0.0.1 127.0.0.1 1
177.176.255.255 255.255.255.255 177.176.50.3 177.176.50.3 1
224.0.0.0 224.0.0.0 177.175.50.3 177.175.50.3 1
224.0.0.0 224.0.0.0 177.176.50.3 177.176.50.3 1
255.255.255.255 255.255.255.255 177.175.50.3 177.175.50.3 1

When I ping from a station on the 177.175.0.0 subnet with the gateway equal to 177.175.50.3, I am able to ping both NIC IP Addresses. However, I get a response timed out for any other station on the 177.176.0.0 subnet. How can I get this to work?

3 replies

by joshg

I think your Proxy is blocking the ping response from returning to your machine. Make sure the address tables in Proxy include all of your subnets. Run a tracert from both ends to see where the packets are getting lost at.

by aperkins

I had the Proxy software completely turned off while I was having this problem. It apparently was a problem with a NT System file. I solved the problem by adding a static route and then removing that same route. Once I did this, the routing function started working. Way to go Microsoft!!

This discussion is closed to new replies.