VLAN Routing

We have two floors with different subnets (VLANs) , and  These two subnets is routed by our H3C 5130 switch and devices are pingable to each other.
We find that some devices (print, NAS) in .2 subnet can't be accessible in .1 subnet although they are pingable to each other. The routing doesn't go through router and there is no ACL rule. Any idea ??

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don JohnstonInstructorCommented:
The routing doesn't go through router
If the traffic doesn't go through some type of routing device, then there is no way for two subnets to communicate in the first place.

But assuming that is a typo, if the devices can ping each other but are unable to communicate otherwise, it's either an ACL on the routing device, a firewall (either a device or the host) or the host doesn't have the necessary software configured.

The most common cause when it's not the router is the windows firewall isn't configured to allow the type of traffic.
AXISHKAuthor Commented:
both are vlans create on s l3 switch
Don JohnstonInstructorCommented:
Layer 3 switches perform routing.

Are there any ACL's on the switch? Have you checked the hosts for firewall settings?
SolarWinds® VoIP and Network Quality Manager(VNQM)

WAN and VoIP monitoring tools that can help with troubleshooting via an intuitive web interface. Review quality of service data, including jitter, latency, packet loss, and MOS. Troubleshoot call performance and correlate call issues with WAN performance for Cisco and Avaya calls

AXISHKAuthor Commented:
no acl

one of the device is network printer
Check default gateway IP address on those devices (printers, hubs etc).
IP address of default gateway should be interface vlan IP address, since traffic out of own subnet is sent to default gateway. Devices with misconfigured default gateway address can communicate only with devices in the same subnet.
AXISHKAuthor Commented:
sure that the gateway has been set
Don JohnstonInstructorCommented:
Yeah, there's no way it could have been the gateway since you can ping the devices.

It's either going to be a software configuration or a host firewall issue.
How I understood (or misunderstood) question is that those specific devices (printer, NAS) are not pingable from other VLANs, but only from within the same VLAN.

If those devices are pingable from other VLANs, it is not default gateway problem. ACL make sense, but it is not configured. Firewall could be problem, but does not make much sense since usually there is no firewall on printers, except there is some hardware device in path.

If everything is pingable most likely that is not network problem, internetwork routing works OK (especially with no ACL configured, network can be eliminated as root cause). Maybe users have no permissions to access specific devices? That would make much more sense than network problem.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.