SENA

GRD 748830-1

TROUBLESHOOTING

Instructor: Javier Mejia

Apprentice: Guillermo Salamanca

1
 TROUBLESHOOTING
The following activity is performed taking into account the following network
topology.

We must first verify accessibility from our Windows Server and client devices Debian. In this moment
our Debian have another IP addres, so we need to change that.

DEBIAN SERVER 8.3.1

Correctly configure the IP address that must be assigned to the Debian server. IP you must have is
192.168.20.10/24 , according to the topology.

Now we stop and start a network interface to make changes and verify again.

2
Verify that the DNS server correspond to ours we have in our LAN in my case are the following.

So in our device Debian we have to put the same DNS server IP

Now that we have configured correctly we must verify whether our device were to have connection
with their respective LAN. 192.168.20.1/24.

In this case we have not received a response from our request, according to the network system is
unreachable, obviously there is a configuration problem in R2.

WINDOWS SERVER 2012

Correctly configure the IP address that must be assigned to the Windows server. IP you must have is
192.168.30.10/24 and DNS IP Server, according to the topology.

Check the connection to the corresponding gateway.

Obviously there is also a configuration error in the router 3 because our windows servr not find the
Network.
So far we have verified that our Windows Server and Debian server devices are properly configured,
however they haven't connection even with your gateway, so we will continue with our verification
routers 2 and 3.

3
 ROUTER 2
The first thing to do is verify the configuration of network interfaces, in this case G 1/0 and G 2/0.

The first mistake we identified is that the interfaces are administratively down and also the interface IP
interface does not correspond G 1/0 and G 3/0 interface has the IP that you must have the G 2/0
interface. We will correct this errors, we will raise the interfaces and verify the configuration again our
Router 2.

Now we test the connection from Debian Server to its gateway.

Our ping was successfully this time. Now we will check connectivity between R2 and Debian server
and R1, remember that the enrutamient of this network is by means OSPF, so also will verify that the
settings are properly OSPF and DNS Server, and allow the router DNS lookups.

Was successfully. OK

4
When we do a ping R1 weren't get no response. To solve it we must verify R1

For now we verify that our R1 allows DNS lookups and DNS server name you have.

R1 configuration does not allow searches and DNS server name at this time is mis-configured, so we
will correct them and verify the configuration again.

Now R1 if allow DNS lookups and look through the name that we set, in this case 200.75.51.132
See OSPF settings. But in this moment can't see another neigborgs, but the configuration is OK.

But not seeing any network, verify the configuration of OSPF currently.

After checking the settings we show that this properly, so we have to verify R1, that is where time takes
us to the verification.
At the moment we have configured R2, however still we do not have connectivity to R1, which we will
verify below.

ROUTER 1
As in R2 first thing we do is check the configuration of network interfaces.

5
The first thing we see is that the interfaces are down so the first thing we do is turn on the interfaces G
1/0 G 2/0 and G 3/0, In addition we see that the IP should be assigned by DHCP is static, thus not have
access to the external network in this case.

After the IP interface configuration we verify the configuration we have currently running on your
router, and we show that the interface also must be outside as inside is therefore correct this as well.

6
We will verify connectivity with R2, in this case was successfully.
Now we have connectivity with R2 and networks 192.168.0.0/24 and 10.0.0.0/30, let's see now R3
connectivity.

In this case we see that there is no connectivity with the Interfas connected directly, although the above
network interface can not communicate with the IP 10.0.0.6/30, as we have verified the settings in R1
we conclude that the error is in R3.

7
Now we will verify that we have access to the Internet from the router, which provides us with Internet
connection to our LAN topology. Let's see NAT settings we have right now.

The first error detect it is that the configuration of Nat and lists of nat access do not match, so we must
correct it immediately, otherwise you can not get out to the Internet, because it should be the same list
that we set in NAT overload in access lists.
We also find that the static default route does not point to our Internet gateway, in this case the
192.168.0.1/24, so we will also correct and we will check the connection to google.com.

Ping to google.com unsuccessfully, but in this case the mistake is the configuration of DNS name
server an DNS lookup, so we should to change this parameters.

We check the router configuration has no configured DNS server name and does not allow DNS
lookups.

We make the necessary corrections and make another ping google.com. Okay

8
And finally we verify the OSPF configuration, which must match the R2 and R3.

For the moment R1 only can see to the network 192.168.20.0 trought of 10.0.0.2 in the interface G 2/0.

ROUTER 3
Similarly in R1, R2 will perform joins verification R3 interface configurations first.

We note that the interfaces are turned off, so proceed to initiate and we will probe the connection again

9
In the same way we verify the name-server configuration and DNS lookup, which also have to correct
it, because the current configuration does not match.

After making the respective corrections test the connectivity to Internet

But it hasn't connection to google.com, so we have to show the configuration that is running.

As shown in the above image there is a default route that sends all requests to the IP 192.168.30.10,
which is the same interface G 2/0, what we do is remove this route and try again.

Now that we have the correct settings, test connectivity between devices, both among the same LAN,
as did Internet in all devices.

10
Now to finish must verify that effectively Debian Server and Windows Server have connectivity
between them and to the Internet.

The connectivity are OK into devices, so now we go to check the conection whit Internet using a web
browser.

The connectivity are OK

11
Likewise from debian server.

And if we accede to Internet whit w3m

The connectivity are OK

12