Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot Find 2nd NIC

Status
Not open for further replies.

techshoot

Programmer
Aug 25, 2001
173
US
I have a NT4 (SP6a) server with 2 NIC cards installed:
IP#1 10.127.1.2 / 255.255.255.0 (To Domain Network)
IP#2 10.127.5.2 / 255.255.255.0 (To DSL Router)

I can ping both from a command prompt at this server but cannot ping NIC #2 from any of the other clients and obviously cannot utilize the DSL line for internet access from any clioent as well. Any idea as to what I need to do?
 
Did you enable IP forwarding? That would be critical, and the most likely problem. Otherwise, you might start trying to ping the DSL router's internal interface from your internal clients instead of trying to ping the DSL-side NIC in your server. Have you checked your routing table, and rechecked all your numbers? Typos can really hide from you sometimes.

ShackDaddy
 
IP Forwarding is enabled, cannot ping the internal router interface. I am not sure of how to do the route table properly, which may be my problem.

Current Table (route print)
DEST MASK GATEWAY INTERFACE MTRC
0.0.0.0 0.0.0.0 10.127.1.2 10.127.5.2 1
0.0.0.0 0.0.0.0 10.127.5.1 10.127.5.2 1
0.0.0.0 0.0.0.0 10.127.5.2 10.127.1.2 1
10.127.1.0 255.255.255.0 10.127.1.2 10.127.1.2 1
10.127.1.2 255.255.255.255 127.0.0.1 127.0.0.1 1
10.127.5.0 255.255.255.0 10.127.5.2 10.127.5.2 1
10.127.5.2 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.127.5.2 10.127.5.2 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
255.255.255.255 255.255.255.255 10.127.5.2 10.127.5.2 1
 
I see the problem in your routing table. The first entry in your table is screwed up. It's saying that the default gateway for your system is 10.127.1.2, but that to get to it, it should sent packets out the DSL-side interface.

You probably want to:
'route delete 0.0.0.0' and then
'route add 0.0.0.0 MASK 0.0.0.0 10.127.5.1 1'
then check it. The gateway and the interface should be on the same network. One way you might have gotten into this mess is by using the 'IF' parameter when you were creating a route. You then specified the wrong adapter number after the 'IF'.

Hope this was helpful...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top