Switch – Inter VLAN – switch layer 3

When testing networking connections, don't use windows machines.

My firewall was set to allow ICMP traffic from any subnet on any domain profile yet it was still blocking the packets.

Turning the firewall off completely allowed the traffic through, so the routing is working.

Also, pings probably aren't the best way to test network connectivity.

For anyone looking to route between two VLANs on the Dell PowerConnect 5524, the commands on page 220 of the user guide are sufficient:

en
config

vlan database
vlan 100-101
exit

interface gi1/0/1
switchport access vlan 100
ip address 1.1.1.1 255.255.255.0
exit

interface gi1/0/2
switchport access vlan 101
ip address 2.1.1.1 255.255.255.0
exit

Basics

When you tag a VLAN on a port, it will send out the traffic on that port with the VLAN tag, when the port receives traffic it looks for the tag and places the traffic into that VLAN. You can have multiple tagged VLANs on one port (sometimes called trunk).

When you send out a VLAN untagged on a port it will not add the VLAN tag to the packet and when receiving packets without a VLAN tag it will be placed into that VLAN (on Netgear and others you have to set PVID (Primary VLAN ID))

To your problem

I think you are not far away... - Router port connected to Switch1 should have IP within VLAN 2220. - DHCP Server should have different IP from different Subnet! - Router port Connected to Switch2 should have IP in Subnet of DHCP Server - You should define a DHCP Helper on Router port connected to Switch1 so DHCP Request get forwarded to DHCP Server. Hot to do that is described here: http://kb.netgear.com/app/answers/detail/a_id/21990/~/how-do-i-configure-a-dhcp-l3-relay-using-the-web-interface-on-my-managed-switch%3F

Hope this helps you a little bit further. If not, please post a more detailed network diagram with VLAN IDs and IPs.