[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Help with Network routing issue on Windows 2008

Posted on 2009-12-18
12
Medium Priority
?
271 Views
Last Modified: 2012-05-08
I'm wondering if someone can help me.  I'm working on some training using Microsoft E-Learning.  They have provided me a lab, but the lab does not seem to be working as intended.  That is, the instructions for my various exercises do not seem to be correct in that I keep hitting road blocks.  At any rate, I'm trying to get a firm grasp on the subject matter, so I'm taking it upon myself to try and figure out "how to make the instructions work!".  Heavy handed task I know.

At any rate, I have 3 servers with the following configurations.
---------------------------------------------
Server1

IP: 10.10.0.10
SM: 255.255.0.0
GW: 10.10.0.1
---------------------------------------------
Server2 (Windows-based router)

IP1:  10.10.0.1
SM: 255.255.0.0
GW: none

IP2:  10.11.0.1
SM: 255.255.0.0
GW: none
---------------------------------------------
Server3

IP1: 10.11.0.24
SM: 255.255.0.0
GW: 10.11.0.1

IP2: 10.12.0.24
SM: 255.255.0.0
GW: none
---------------------------------------------

Server2 has RRAS installed with the LAN Router role.  It's routing table seems to be correct (routes for both 10.10.0.0 and 10.11.0.0).

Server1 can ping 10.11.0.1.  

Server1 can NOT ping 10.11.0.24.  Why?  I imagine it's due to the next issue.

Server2, itself, can NOT ping 10.11.0.24.  Why?  

Server3 can NOT ping 10.11.0.1 (its gateway).  Why?

It is my understanding that Server2 and Server3 should be able to ping each other as they both have interfaces on the 10.11.0.0 network.  I assume once this gets fixed, the other issues will be corrected as well.

Any advice would be helpful!

Thank you,
Matthew
0
Comment
Question by:MMcDonald
  • 5
  • 4
  • 3
12 Comments
 
LVL 5

Assisted Solution

by:valheru_m
valheru_m earned 2000 total points
ID: 26084644
you are correct in that servers 2 & 3 should be able to ping each other with no routing involvement provided that they are physically connected to the same network. I dont know how your lab is set up (virtual, physical, etc) but other than a physical connectivity problem, the only thing that would keep those two from hitting each other would be a software firewall on one or both of those servers.  Make sure that no software firewall is running on either of those machines and then make sure that the physical network connections are both correct.

Also, this can be helpful when troubleshooting such connections...  Try pinging Server3's IP address from server 3 itself.  I know it seems obvious, but often if there are physical connectivity problems or other local connection problems such as drivers not being loaded properly, the box wont evn be able to hit it's local IP address.  If it can ping itself, then try troubleshooting external factors, but if it can't, you know the box itself is the problem.
0
 
LVL 16

Expert Comment

by:memo_tnt
ID: 26084667
hi

it's a routing issue>>
you need to route both networks to each other ..

0
 
LVL 5

Expert Comment

by:valheru_m
ID: 26084702
actually, per his diagram, both networks ARE routed to each other.  There's only one router, server2, and it has the RRAS role installed.  since it has interfaces on both networks and he already stated that the routing tables looked correct, I would say that part is fine.

The problem is the broken connection between servers 2 & 3, since they are on the same subnet and can't ping each other.  NO matter how well your router is configured, it can't route traffic to a box that it can't hit.
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
LVL 16

Expert Comment

by:memo_tnt
ID: 26084769
hi

make tracert to 10.11.0.24 from server 2 .. am sure it will go through 10.10.0.1
and do it from server 1

also tracert to 10.11.0.1 from server 3

and send results





0
 

Author Comment

by:MMcDonald
ID: 26084781
Thanks valheru_m.

It's funny that you mentioned firewall.  Because originally, Server1 could not ping 10.11.0.1.  In my troubleshooting for that issue, I ended up disabling the firewalls entirely on all systems and that resolved that issue.  So now, I have no firewalls running, and my aforementioned issues persist.

I agree that there may be a physical connectivity issue somewhere.

The lab was provided to me by MS and it is completely virtual.  I'm thinking they have something messed up on the back end with the virtual network.  I just wanted to make sure I wasn't missing anything integral.

@memo_tnt
I will try your instructions and will report when I have the results.  My lab timed out and I have to set it up again.
0
 

Author Comment

by:MMcDonald
ID: 26084834
Here's something interesting.  Server3 is originally configured with an IP of 10.10.0.24 with GW: 10.10.0.1.  In this configuration, it can ping 10.11.0.1 fine.

When I follow instructions to change the IP to 10.11.0.24 with GW: 10.11.0.1, I can no longer ping 10.11.0.1.

Could it be something to do with the way server2 is configured?  Neither NIC on server2 has a gateway defined.  Maybe it's getting confused with the routes to 10.10.0.0 and 10.11.0.0?

-------------------------------
Results from Memo's request
-------------------------------
Tracert to 10.11.0.24 from Server2
   1     [10.11.0.1] reports:  Destination host unreachable

Tracert to 10.11.0.1 from Server3
    1    [10.11.0.24] reports:  Destination host unreachable

-------------------------------
Routing table from Server2 (attached as I can't copy/paste from lab)
-------------------------------

server2-routeprint.jpg
0
 
LVL 16

Expert Comment

by:memo_tnt
ID: 26084876
hi

what's your default route ,, it's not appear in your route table??


0
 

Author Comment

by:MMcDonald
ID: 26084900
Server2 *IS* the router, thus there is no default route.  Neither interface has a gateway.
0
 
LVL 16

Expert Comment

by:memo_tnt
ID: 26084945
sorry i meant server 3 but didn't mention that ..

anyways, does server two has two NICs or you are using two IPs for the same NIC
???

try remove network 10.10.0.0 and check the other one

??
0
 

Accepted Solution

by:
MMcDonald earned 0 total points
ID: 26084957
AAAHHH... I figured it out!

They have the NICs/virtual networks configured backwards on Server3.  On Server3, I configured NIC2 with 10.11.0.24 (GW: 10.11.0.1) instead of NIC1 and now everything works.  *sigh*  I don't know why I didn't try this the first time.

On a side note, maybe I should just do my own troubleshooting for a longer period of time as almost every question I've asked ended up being resolved myself.  I'm not giving you guys a chance!!  haha (sorry about that).

I appreciate the attempts to assist though!  I'll award you the points though, valheru_m, as you basically answered my question originally, which is what I was truly after.  The issue was due to physical connectivity issue on the backend.
0
 
LVL 5

Expert Comment

by:valheru_m
ID: 26085107
Thanks and good luck with your training!
0
 

Author Comment

by:MMcDonald
ID: 26085859
Thanks valheru_m!
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the hope of saving someone else's sanity... About a year ago we bought a Cisco 1921 router with two ADSL/VDSL EHWIC cards to load balance local network traffic over the two broadband lines we have, but we couldn't get the routing to work consi…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question