locked
Routing IP traffic thru Windows XP Pro machine - question. RRS feed

  • Question

  • I have a Windows XP Pro SP3 system called "Micropress" that has 2 nics.  I have enabled IP routing on this system.
    Nic 1 has a single port that is connected to LAN1 with ip address of 10.1.1.37/24. 
    Nic 2 has 2 ports.  Nic2-portA (10.10.10.1/24) is connected to LAN2.  Nic2-portB(20.20.20.1/24) is connected to LAN3.
    I can ping from the Windows system to ip's on LAN1, 2, and 3 but I can't ping from LAN1 to LAN2, LAN2 to LAN3, etc.  
    What I am trying to do is successfully route traffic thru the Windows computer so that devices on each network can communicate with each other for file sharing, etc.  This is a corporate network running a Windows 2003 domain with internal DNS, etc.  In other words this ain't no workgroup configuration.  Please help.  I can't figure out what I am doing wrong.  I have a diagram at this link http://www.polyengineering.com/filedownload/Micropress-Diagram.jpg that will help give a picture of this environment.
    thanks.
    Thursday, March 31, 2011 2:34 PM

Answers

  •   That is correct. Traffic for your new subnets will never reach your XP router without some additional help. By default, traffic in 10.1.1 goes to the router at 10.1.1.1  This router does not know where your new subnets are or how to reach them. You need to give it static routes so that it knows to reach your new subnets through your XP router.

      eg  10.1.010.0    255.255.255.0   10.1.1.37

            20.20.20.0    255.255.255.0   10.1.1.37

     Your routing will then work.

     


    Bill
    • Marked as answer by Poly Admin Monday, May 9, 2011 1:48 PM
    Friday, April 1, 2011 3:21 AM

All replies

  •   That is correct. Traffic for your new subnets will never reach your XP router without some additional help. By default, traffic in 10.1.1 goes to the router at 10.1.1.1  This router does not know where your new subnets are or how to reach them. You need to give it static routes so that it knows to reach your new subnets through your XP router.

      eg  10.1.010.0    255.255.255.0   10.1.1.37

            20.20.20.0    255.255.255.0   10.1.1.37

     Your routing will then work.

     


    Bill
    • Marked as answer by Poly Admin Monday, May 9, 2011 1:48 PM
    Friday, April 1, 2011 3:21 AM
  • Yes.  Thank you.  I knew I was leaving something out.  I will add this route to our router and repost to let you know of the results.  thanks
    Friday, April 1, 2011 12:42 PM
  • Bill - Does everything else look correct?
    Friday, April 1, 2011 12:43 PM
  • That did it.  Now I can successfully ping devices on the 10.10.10.x and 20.20.20.x networks from our "regular" LAN.  All I had to do was add the static route entries into our router and it immediately started working.  My Windows XP machine was configured properly.

    Thanks, bill

    Friday, April 1, 2011 6:10 PM
  • It still is not working exactly like I need it to.  The reason for configuring this is to be able to scan from a fancy copier on the 10.10.10.x and 20.20.20.x networks to users computers on our company LAN (10.1.1.x).  I can scan to users computers if I use the ip address like \\ip-address\scans but it will not work if I do \\username\scans.  I have entered dns server addresses into the devices on the 10.10.10.x and 20.20.20.x networks.  What else could it be?  Thanks already for help.
    Friday, April 1, 2011 8:59 PM
  •  Netbios names won't work because of the router, which blocks LAN broadcasts. DNS should work.

     


    Bill
    Saturday, April 2, 2011 1:14 AM
  • It still is not working exactly like I need it to.  The reason for configuring this is to be able to scan from a fancy copier on the 10.10.10.x and 20.20.20.x networks to users computers on our company LAN (10.1.1.x).  I can scan to users computers if I use the ip address like \\ip-address\scans but it will not work if I do \\username\scans.  I have entered dns server addresses into the devices on the 10.10.10.x and 20.20.20.x networks.  What else could it be?  Thanks already for help.
    you need to add a DNS server into the picture of things.Since you'r on a domain environment already, configure a DNS server
    Tunde Abagun MCP,MCSA,MCTS,MCITP en p "for the love of Computers"
    Saturday, April 2, 2011 10:17 PM
  • In response to the last couple of posts, take another look at my last post & notice it says that I have already entered dns server addresses for the devices on the 10.10.10.x and 20.20.20.x networks.  That is why I cannot figure out why it isn't working. 

    Routing is working properly.  Now I just have to figure out why name resolution is not working.

    If anyone has any other items for me to check let me know.

    I will mark Bill's post as the "Answer" to this question after a couple more days.  When I figure it out I will re-post so that someone else may benefit from this troubleshooting.        thanks

    Monday, April 4, 2011 12:43 PM
  • check DNS configuration , and enable active directory integrated zones 
    Tunde Abagun MCP,MCSA,MCTS,MCITP en p "for the love of Computers"
    Monday, April 4, 2011 7:41 PM
  • We have two dns servers and I have entered their addresses into the devices on the 10.10.10.x and 20.20.20.x networks.  IP routing is working and we can scan to computers on the 10.1.1.x network if we use \\ip-address\sharename but not if we use \\computername\sharename.  I don't know what else to check.  I guess we may have to give up on it.  I will mark Bill Grants reply as the answer.  thanks
    Tuesday, April 5, 2011 12:43 PM