Solucionado: Re: VLAN 10,20,30 not connect to dns and http

OGUZZZ · ‎05-02-2023

hii ,

I can't connect to the dns and http server on my network.

can you help, thanks

Flavio Miranda · ‎05-03-2023

Of course the vlan will communicate with each other. That's the whole idea of networking. If you want to segregate the network you need to use either a firewall or Access List.

Button line here my friend, to finish this conversation. Your topology was not working, at least on the first file you attached and now, at least on the file I have in my machine, it is fully functional.

You did not say anything about vlan can not communicate until now. But, it is up to you of course. I wish you all the best on your study and I hope I could contribute a little bit with that.

Make the changes you need, explore and good learning to you.

cheers!

Ver la solución en mensaje original publicado

Julio E. Moisa · ‎05-02-2023

Hi

Can you answer the following questions?

- Have you configure inter vlan routing? you can enable it through ip routing command on the core switch.

- Have you configured the interface vlan (SVI) for each VLAN on the core routing? example:

interface vlan 10
ip address 192.168.10.1 255.255.255.0
no shutdown

* Remember it will be the default gateway for each computer over a specific VLAN.

Example:

For computer on VLAN 10 must configure something like:

ip address 192.168.10.100
subnet mask 255.255.255.0
default gateway 192.168.10.1

Similar for the other computers in other VLANs.

- Have you configure a default gateway on each computer?

- Have you created the VLANs on each switch? And if the access switches are connected to the Core switch through Trunk interface?

- Http and DNS are enabled on the server?

>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

OGUZZZ · ‎05-02-2023

thanks for your answer,

vlans are working

native vlan 1 192.168.88.1 255.255.255.192

vlan 10 192.168.88.65 255.255.255.192

vlan 20 192.168.88.129 255.255.255.192

vlan 30 192.168.88.193 255.255.255.192

DHCP is working no problem,

but dns server and http not connect,

ROUTER CONF

spanning-tree mode pvst
!
!
!
!
!
!
interface FastEthernet0/0
no ip address
duplex auto
speed auto
!
interface FastEthernet0/0.1
encapsulation dot1Q 1 native
ip address 192.168.88.1 255.255.255.192
!
interface FastEthernet0/0.10
encapsulation dot1Q 10
ip address 192.168.88.65 255.255.255.192
!
interface FastEthernet0/0.20
encapsulation dot1Q 20
ip address 192.168.88.129 255.255.255.192
!
interface FastEthernet0/0.30
encapsulation dot1Q 30
ip address 192.168.88.193 255.255.255.192
!
interface FastEthernet0/1
description server interface
ip address 10.10.10.1 255.255.255.0
duplex auto
speed auto
!
interface Vlan1
no ip address
!
ip classless
!
ip flow-export version 9
!

-------------------------------------

MULTİLAYER SWİTCH

ip routing

!

spanning-tree mode pvst

!

interface FastEthernet0/1

switchport trunk encapsulation dot1q

switchport mode trunk

!

interface FastEthernet0/2

switchport trunk encapsulation dot1q

switchport mode trunk

!

interface FastEthernet0/3

switchport trunk encapsulation dot1q

switchport mode trunk

!

interface FastEthernet0/4

!

interface FastEthernet0/5

switchport trunk encapsulation dot1q

switchport mode access

switchport nonegotiate

!

interface FastEthernet0/6

!

interface FastEthernet0/7

!

interface FastEthernet0/8

!

interface FastEthernet0/9

!

interface FastEthernet0/10

!

interface FastEthernet0/11

!

interface FastEthernet0/12

!

interface FastEthernet0/13

!

interface FastEthernet0/14

!

interface FastEthernet0/15

!

interface FastEthernet0/16

!

interface FastEthernet0/17

!

interface FastEthernet0/18

!

interface FastEthernet0/19

!

interface FastEthernet0/20

!

interface FastEthernet0/21

!

interface FastEthernet0/22

!

interface FastEthernet0/23

!

interface FastEthernet0/24

!

interface GigabitEthernet0/1

!

interface GigabitEthernet0/2

!

interface Vlan1

ip address 192.168.88.1 255.255.255.192

ip helper-address 192.188.88.2

!

interface Vlan10

mac-address 0040.0bb1.a101

ip address 192.168.88.65 255.255.255.192

ip helper-address 192.168.88.2

!

interface Vlan20

mac-address 0040.0bb1.a102

ip address 192.168.88.129 255.255.255.192

ip helper-address 192.168.88.2

!

interface Vlan30

mac-address 0040.0bb1.a103

ip address 192.168.88.193 255.255.255.192

ip helper-address 192.168.88.2

!

ip classless

!

ip flow-export version 9

!

line con 0

!

line aux 0

!

line vty 0 4

login

!

thank you

Julio E. Moisa · ‎05-02-2023

Hi

If the sub interface are configure on the router you dont need SVI interface vlans on the switch, just configure a trunk interface on the core switch to connect to the router. You dont neet to enable ip routing on the Core switch (multilayer switch), the router will do the intervlan routing through the router-in-a-stick scheme.

The computer must use the IP address of the specific sub interface as default gateway.

A quick test is:

make ping from the router to the server or telnet, example:

ping (server´s ip) source interface (sub interface vlan10 or 20 or 30

telnet (servers´s ip) (Specific port)
also
telnet (servers´s ip) (Specific port) /source-interface

*im not sure if you will be able to run the latest commands on packet tracer but you can test ping.

Regards.

>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Flavio Miranda · ‎05-02-2023

Hi

I had to change a few things in order to work but the file attached is working

First, you never use the same IP address on different devices. Each device must have its own IP address.

Second, you dont create interface vlan on layer2 switches, that why you have layer3 switches

Three, if you have a layer3 switch on the topology, you dont need to setup the router in a stick like you did. Just setup a transit connection between them in layer3

If you have a server connected to the layer3 switch, better use a layer 3 interface no layer2

On your router you create subinterface uncessary and you used wrong IP address 192.168.89...while the rest of network is 192.168.88.x

OGUZZZ · ‎05-02-2023

Thank you for the answer

my vlans are working, there is no problem, those structures may be old, I watched many videos but I couldn't find a solution, it may be left from them

thank you for your interest,

but also in the topology you sent

pc0,1,2,3,4,5,6,7,8 ie vlan10,20,30 still can't connect to dns and http

Julio E. Moisa · ‎05-02-2023

Remove the following configs from the multilayer switch and just be sure that the default gateway used on the computers is the IP of the sub interfaces on the router.

interface Vlan10

mac-address 0040.0bb1.a101

ip address 192.168.88.65 255.255.255.192

ip helper-address 192.168.88.2

!

interface Vlan20

mac-address 0040.0bb1.a102

ip address 192.168.88.129 255.255.255.192

ip helper-address 192.168.88.2

!

interface Vlan30

mac-address 0040.0bb1.a103

ip address 192.168.88.193 255.255.255.192

ip helper-address 192.168.88.2

Can you make ping from the computers to the server?

>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

OGUZZZ · ‎05-02-2023

hello,

Thank you for the answer

pc0,1,2,3,4,5,6,7,8 not pinging dhcp

but DHCP SUCCES getting ip address

Flavio Miranda · ‎05-02-2023

It was on my machine. Make sure when you open the file, the PCs is getting IP addtess.

OGUZZZ · ‎05-02-2023

dhcp is working no problem, but dns and http not connecting

Flavio Miranda · ‎05-02-2023

Right, you mean, you are opening a browser on the PC and typing the http server ip addtess and you get nothing?

But you can ping, right?

Flavio Miranda · ‎05-02-2023

You are testing wrong. You HTTP server is 10.10.10.3 and not .4. The .4 is the DNS server and it will not open a browser.

Testing to 10.10.10.3 you can get response.

OGUZZZ · ‎05-03-2023

hello, when I do what you did for pc 0, when I do it for the other switch, vlan 10 and vlan 20 communicate,

While doing one, the other one breaks down. That's my main problem.

thanks

Flavio Miranda · ‎05-03-2023

Now, all PCs should be working. Test please.

The problem with my last file was that I did not remove the IP address from the switches Layer2.

A bit of explanation about your topology. As you are studying, I think this might be helpful. The first 3 switches in the red circle, we call Layer2 switches. They dont need to worry about IP address for PCs. They only offer physical connectivity to the network. And they delivery the traffic to the Layer3 switch in the second red circle left hand side.

The Layer3 switch need to have IP address for all vlans. He is the gateway of the network. And he needs to have routing.

As you can see, I put a route on it like this "ip route 0.0.0.0 0.0.0.0 10.10.11.1", which means, everything you dont know about, you sent to the router.

On the router I also added a route like this "ip route 192.168.0.0 255.255.0.0 10.10.11.2" which means, if you received a packet in which the source is 192.168.x.x, you send it back to Layer3 switch. Cause Layer3 switch have IP address on this network and will know how to handle the packets.

OGUZZZ · ‎05-03-2023

i really appreciate your help, but vlans are communicating with each other i don't want that,

vlan 10 connects to vlan 20 or vlan 30.

I don't understand what we are missing here
When we enter the ip address on the layer 2 switches, the vlans work properly, this time the dns is not connected

for example, it is pinging vlan 20 pc with vlan 10 pc now
I dont want this.