NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
crawbles
Jul 26, 2017Aspirant
S3300 inter-VLAN Routing Issue
I have just purchase an S3300-28X and S3300-52X and am getting to grips with all the features. Most features seem pretty straight forward so far, but I'm having real issues setting up inter-VLAN rout...
- Jul 27, 2017
I managed to solve the issue!
It turns out Windows Firewall blocks network traffic from different subnets by default. This being my first foray into VLAN's, I was so convinced I'd configured something incorrectly that I neglected to explore other potential causes.
If anyone else having the same issue comes across this, there's a TechNet article which explains how to create an ICMP rule which will allow inbound traffic from another subnet.
DanielZhang
Jul 27, 2017NETGEAR Expert
Hi Crawbles,
Welcome to NETGEAR community!:smileyhappy:
Your configuration is correct for inter-VLAN routing.
But S3300 is a smart switch and the inter-VLAN routing function disabled by default.
So maybe you need to enable ‘IP routing’ as following screenshot again try again.
May the solution help you.:smileyhappy:
crawbles
Jul 27, 2017Aspirant
Hi Daniel,
Thanks for taking the time to reply! :smileyhappy:
I already have IP routing enabled as per your screenshot, but still not having any success. I've taken some screenshots of my configuration; hopefully you'll be able to spot where I've gone wrong.
Here are the IP settings for the workstation on VLAN10. The workstation on VLAN20 is the same, but with the IP and Gateway set to 10.0.20.x instead.
The workstations can both ping either of the VLAN interfaces (10.0.x.1), which leads me to believe that inter-VLAN routing is working to an extent. But the workstations are unable to ping each other.
- crawblesJul 27, 2017Aspirant
I managed to solve the issue!
It turns out Windows Firewall blocks network traffic from different subnets by default. This being my first foray into VLAN's, I was so convinced I'd configured something incorrectly that I neglected to explore other potential causes.
If anyone else having the same issue comes across this, there's a TechNet article which explains how to create an ICMP rule which will allow inbound traffic from another subnet.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!