cancelar
Mostrando los resultados de 
Buscar en lugar de 
Quiere decir: 
cancel
518
Visitas
3
ÚTIL
13
Respuestas

Problem with LAN HTTP server

andrew005
Level 1
Level 1

I have a host (eg 33.33.33.254) unable to reach HTTP server 192.168.0.3 (PUBLIC), but they are pinged.

1 SOLUCIÓN ACEPTADA

Soluciones aceptadas
13 RESPUESTAS 13

@andrew005 

 Ping is very helpful but limited to connectivity. If you are trying to reach a HTTP server you need to check if the service is enabled on the target server, if there is no firewall or ACL in the path preventing you from get to the HTTP port on the server. 

I don't know how to do it. I tried using ACL (on another project) to configure access to port 80, but nothing ever started working. Please help me with this.

what is it? PacketTracer? Or real device? 

andrew005
Level 1
Level 1

 PacketTracer.Sorry, I forgot to add the project

@andrew005 

The problem is that you have two networks 192.168.0.0/24 on the topology. when you try to access the 192.168.0.3, HTTP server, the traffic is going to FILIA_1 and not to MAIN BULDING

You need to change the IP address in one of those segment.

 

FlavioMiranda_0-1731529935757.png

 

andrew005
Level 1
Level 1

I deleted network with similar ip, but it still doesn't work.

This one was interesting. Let me explain exactly what I have done.

First there was a connectivity problem. You have a default route on Rmb sending everything to 11.11.11.14 but you dont have dynamic routing protocol running between ISP1 and Rmb, so, the ISP1 router 5 does not know how to get to 192.168.0.0/24.

 What I had to do is add a static route on ISP1 R5 sending the 192.168.0.0/24 to Rmb.

ip route 192.168.0.0 255.255.255.0 11.11.11.13

But now, you need to tell the rest of your router that the network 192.168.0.0/24 is on Rmb. So far, I only told to ISP1 router 5 about that.

For that, I did a redistribute static on OSPF in ISP1

router ospf 1

redistribute static subnets

This way, ISP1 advertized to the other routers where is the network 192.168.0.0/24.

Connectivity problem solved. But, it will not work yet. It turns out that you have NAT on the Rmb Router for exit traffic.

By doing the NAT, the routing does not work as expected. So, I remove the network 33.33.33.0 from NAT by denying the network on the NAT Access List. Bingo!! it works now.

 

ip access-list extended FOR-NAT

deny ip 192.168.0.0 0.0.0.255 192.168.1.0 0.0.0.255

deny ip 192.168.0.0 0.0.0.255 33.33.33.0 0.0.0.255

permit ip 192.168.0.0 0.0.0.255 any

!

!

 

 

Screenshot_1.pngScreenshot_2.png

 

 

Still doesnt work.

@andrew005 

 Make sure the config was not lost during the transfer. It is working for me.

 

FlavioMiranda_0-1731533659007.png

 

Please write "Write memory" on router and send me it again. Cuz i tried to write it in and it doesnt work

check this one

Thank you very much!

andrew005
Level 1
Level 1

Here