How can I route network traffic between two network adapters being both installed on the same server?

Description:
I have a server running Windows Server 2003 with two network adapters installed. That's the way they are configured:

   Host Name . . . . . . . . . . . . : server1
   Primary Dns Suffix  . . . . . . . : testnet.net
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : testnet.net

Ethernet adapter Local Area Connection:
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.49.182.137
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.49.182.1
   DNS Servers . . . . . . . . . . . : 10.32.17.13

Ethernet adapter Local Area Connection 2:
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.0.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 10.32.17.13

The first adapter is connected to our corporate network and has access to our domain testnet.net, DNS, AD, etc.. Now I would like to directly connect a client to the second network adapter (using ip 192.168.0.2, mask 255.255.255.0 and gateway 192.168.0.1) and be able to reach testnet.net. But this doesn't work.

I can only successfully ping 192.168.0.1 and 10.49.182.137 which are the both network adapters installed in my server. I think I must configure a routing but don't know how.

Can anybody please help me?

Thanks in advance
MiFeo
mifeoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bradleys40Commented:
route add 192.168.0.0 255.255.255.0 192.168.0.1 -p

see this site for explanation
http://gentoo-wiki.com/HOWTO_add_a_static_route
0
cammjCommented:
Alternatively you can use Routing and Remote access for a bit more control.
0
mifeoAuthor Commented:
Thanks a lot for your replies... but this didn't help me.
I added the route with the command.

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 90 27 3c 25 a8 ...... Intel(R) PRO/100+ PCI Adapter
0x20004 ...00 60 97 72 a3 bb ...... 3Com 3C900COMBO-based Ethernet Adapter (Generic)
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      10.49.182.1    10.49.182.137     20
      10.49.182.0    255.255.255.0    10.49.182.137    10.49.182.137      1
    10.49.182.137  255.255.255.255        127.0.0.1        127.0.0.1     20
   10.255.255.255  255.255.255.255    10.49.182.137    10.49.182.137     20
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
        224.0.0.0        240.0.0.0    10.49.182.137    10.49.182.137     20
  255.255.255.255  255.255.255.255    10.49.182.137    10.49.182.137      1
  255.255.255.255  255.255.255.255    10.49.182.137            20004      1
Default Gateway:       10.49.182.1
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      192.168.0.0    255.255.255.0      192.168.0.1       1
      10.49.182.0    255.255.255.0    10.49.182.137       1

I can ping 10.49.182.137 but not 10.49.182.1.
0
Redefining Cyber Security w/ AI & Machine Learning

The implications of AI and machine learning in cyber security are massive and constantly growing, creating both efficiencies and new challenges across the board. Join our webinar on Sept. 21st to learn more about leveraging AI and machine learning to protect your business.

bradleys40Commented:
you may not be able to ping 10.29.182.1 becuase it will not respond deliberatly. is it a firewall server that is your gateway to the internet ?
the way i read the wuestion is that you wanted to connect to the subnet 192.168.0.0 can you ping something in that subnet
0
mifeoAuthor Commented:
From my server with ip 10.49.182.137 I can ping 10.49.182.1 or 10.49.182.91. I would be able to ping this two ips from a client in the network 192.168.0.x.
0
bradleys40Commented:
I think i understand
you want to connect from the 192.168.X.X network to the 10.49.182.x network

what have you set the default gateway to on the machines on the 192 side
0
mifeoAuthor Commented:
Yes, that's right... sorry, maybe my english is not good enough but I try to explain my problem as good as I can...

My network configuration on the client is:
ip 192.168.0.2
mask 255.255.255.0
gateway 192.168.0.1

no dns servers defined...
0
bradleys40Commented:
if you want to connect to testnet.net from 192.168.0.2 you need to edit the host file
enter line in you host file that pints to the domain
ie
10.x.x.x testnet.net

replace the 10.x.x.x with the ip address you need to resolve to testnet.net
0
cedarghostCommented:
cammj is on the right track. Install Routing and Remote Access, add the adapters and either use Static routes or RIPV2 (your choice).  Then on your clients set the gateway as the IP address of the network card on the server that is in the same subnet. No need to edit host files. Just simple routing.
0
mifeoAuthor Commented:
Hello cedarghost
Thank you for your reply...

I now installed Routing and Remote Access... can you guide me through the configurations I have to make?
0
cedarghostCommented:
First right click your server icon and select configure routing and remote access.
When the wizard starts, select next, then Custom Configuration.
Next select LAN Routing, hit next and then Finish.
The Wizard will  ask you if you want to start the service. Select yes.
Next Select Network interfaces in the left pane and make sure all your interfaces are showing up in the right pane. If they are not, Right click General Routing and select New Interface and add all your interfaces (Network Cards).
Next Right Click General and select New Routing Protocol and for the Protocol select RIP Version 2. Hit OK.
 Now that RIP is showing up under the routing header on the left side, right click the RIP heading and select new interface and add the interfaces you want to route between.
Select OK to the default options for that interface when it pops up.
That is pretty much it. Restart the RRAS service and it should begin routing.
As an alternative, you could just add Static Routes by right clicking Static Route and selecting New Static Route. In the configuration box for the static route remember that once you select the interface you want to route from, the destination is the network address of the other interface and the gateway is the IP address of the other interface.
0
Rob WilliamsCommented:
A)You need to enable routing on the server
B)One way or another add a route to the 192.168.0.2 client.
C)You need to add the return route to the 10.49.182.x PC's

A) Enable RRAS and make sure you use the LAN routing option as described by cedarghost. You do not necessarily need to add RIP. The server will be well aware of the 2 attached subnets.

B)To add the route to the client there are 3 options
-if the server's IP of 192.168.0.1 is the default gateway for the 192.168.0.2 PC, there is no need to add a route, it will default to that route
-add a static route to the 192.168.0.2 PC. If only one PC this is the easiest
route -p add 10.49.182.0 mask 255.255.255.0 192.168.0.1
to delete:
route delete 10.49.182.0
-add the route or routing protocol to the router/gateway (assuming one exists) on the 192.168.0.x subnet. You can add the same static route as above, or enable RIP v2 on the router and the server which will automate the routing.

C)The above 'B' options apply to the 10.49.182.x subnet as well. The route would be:
route -p add 192.168.0.0 mask 255.255.255.0 10.49.182.137
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mifeoAuthor Commented:
Thanks to both of you... I'll give a try.
0
mifeoAuthor Commented:
Don't know why, but the server doesn't route the traffic the way I want it...
I did all the steps cedarghost described, but it doesn't work.
Any suggestions?
0
Rob WilliamsCommented:
Rip/Rip v2  will only work if it is also installed on the routers/default gateways for each network, as per directions I provided. RIP shares routing tables between routing devices, not PC's.
0
mifeoAuthor Commented:
I think I'll let it be... it's to complicated for me.
0
Rob WilliamsCommented:
It's not bad. Just enable RRAS and routing, then add the routes to the PC's on either side of the router.
0
Rob WilliamsCommented:
Personally I do not believe "it's to complicated for me" is an acceptable reason for deletion. Several people invested quite a bit of time here.
Just voicing my opinion, and more than happy to abide with moderators decision upon reviewing.
--Rob
0
Rob WilliamsCommented:
Though it sounds like a conflict of interest on my part, I would say ID:20786456 is the only complete answer. All steps are necessary for it to work. Open to other recommendations.
--Rob
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Hardware-Other

From novice to tech pro — start learning today.