Getting no response when pinging VLAN

I have 2 router that are interconnected to each other. My problem is that they are not part of my private network and are located in two different buildings. I told myself to avoid putting a cable of 100m and dig under the earth to use a vlan. I took a laptop A with IP address 192.168.98.100 and I connected it on the switch of the building (Dell PowerConnect 5424) on port 14. I connected to the switch with the console cable, and created a VLAN of 200 computer and I tagged port 14 on that VLAN. This switch is connected to a fiber optic switch Dell PowerConnect 6224F on which I have done nothing. This switch is connected to another optical fiber that comes into my office on Dell PowerConnect 5424. I took a laptop B with IP address 192.168.98.101. I connected it on the switch port 4. I logged into the console switch, I created a VLAN of 200 computer and I tagged port 4 on that VLAN. I do a ping from laptop B to laptop A. There was no answer to it. Please note that the ping works normally on my network without VLAN. (No problem with antivirus, firewall ... etc.) What have I missed?

Well I do not even read all your content but what ever I read I didn't really understood what you are trying to say. However, looking at your question topic, according to me you are trying to have VLAN setup on your computer. What ever, however, you are doing will not work, simply because Windows does not know the 802.1Q (from vista only I think). You should not tag the VLAN PVID but force the port to the proper value.

So here is the principle that you should put in place in your network:

1. 3 Switch if that doesn't matter to you, you must create your LAYOUT Vlan 200 for it to be recognized throughout his career on the network (so it will be: Dell PowerConnect 5424 + Dell PowerConnect 6224F + DELL PowerConnect 5424 )
2. Then you must mark on what happens your fiber optic port and the latter for the 3 Switches.
3. Once you have done this, you must Tagged ports which is connected to your optical fiber.
4. Finally, you untagged Switch ports which are plugged into your laptops.

Normally, your ping should work. Good luck and do not hesitate to ask me if you need help.

Non-recognition of 802.1Q is more a problem of network card driver that of Windows. The high-end network cards are well aware of 802.1Q long run in a Windows environment, the cards usually know most basic reading frames Tagged (by enabling QoS in the driver properties for 802.1p uses the same frame format), however they can not issue a tagged frame.

Effectively with pilots type broadcom, intel etc. You can wear the 802.1Q but these cards are only available in server environment (given the cost). For laptops the drivers were never developed in this direction and as the OS (not server) do not support you forget for desktop PCs/notebooks. The only thing supported is the 802.1p since W2K through API GQoS but without the VLAN tag support (as 0). Show tagged frames arriving on the PC is absolutely unrelated to the OS/driver, and we know to do it with any hardware i.e. interpreting it is another thing ...

1. 3 Switch if that doesn't matter to you, you must create your LAYOUT Vlan 200 for it to be recognized throughout his career on the network (so it will be: Dell PowerConnect 5424 + Dell PowerConnect 6224F + DELL PowerConnect 5424 )

OK

2. Then you must mark on what happens your fiber optic port and the latter for the 3 Switches.

Found. but I have a question: If I tag like you say about my fiber optic switch with my vlans, this will have no impact on the default network?

3. Once you have done this, you must Tagged ports which is connected to your optical fiber.

Not done yet I await your response

4. Finally, you untagged Switch ports which are plugged into your laptops.

Normally this is already done. In fact what I'm missing is the part on my switch Tagged fiber optics. Compared to your diagram I feel like I tagged my entire network on the new VLAN (that scares me). In fact, just tag ports 1 & 2 mean only that the switch "knows" the default VLANs and MODEL?

As I said earlier, we should remember this when setting up VLANs on a network:

* One Tagged Manages all equipment (switch, router, etc.)
* all others are untagged unmanaged equipment (computer, workstation, printer)

Here in your case, you've got "tagged" the ports on which your fiber comes to pass different Vlans a switch to another. So this is what should resemble the configurations of your switches:

* Switch the PC that hosts the address 192.168.98.100 :

• Vlan 1 name "default"
  
  • Untagged ethernet 1-13-15-26
• Vlan 200 name "Model"
  
  • Untagged ethernet 14 (normal saw you behind your pc)
  • Tagged Ethernet 1 (port with FP)

* Switch that connects the 2 Switches :

• Vlan 1 name "default"
  
  • Untagged ethernet 1-26
• Vlan 200 name "Model"
  
  • Tagged Ethernet 1-2 (port with FP)

* Switch the PC that hosts the address 192.168.98.101 :

• Vlan 1 name "default"
  
  • Untagged ethernet 1-26
• Vlan 200 name "Model"
  
  • Untagged ethernet 4 (normal you behind your pc)
  • Tagged Ethernet 1 (port with FP)

Those with this kind of configuration, it must travel alone. Do not hesitate if there are things that are unclear or you have difficulty understanding