+ 0 Votes Try this test NetMan1958 3 years ago If you go to the computer at 192.168.175.130 and run a traceroute to 192.168.25.38, is the first hop IP Address the same IP that is assigned to the subinterface on the router that is assigned to the VLAN for 192.168.175.130? + 0 Votes you should be able to ping hosts whether it's copiers CG IT 3 years ago computers, access points and whatnot. the network card should respond to arp and ping[icmp] requests. the wrong default gateway would account for no return messages.... Glad you got it worked out..... + 0 Votes You MUST think more binary! TobiF 3 years ago The subnet mask tells each host (computer) on an IP network, what addresses should be directly available. Although we're used to represent these addresses as 4 numbers, divided by dots, the IP address is, in fact, a binary number, consisting of 32 binary digits. The subnet mask must begin with only binary "ones", and must finish with only binary "zeroes". Most convenient, is to split the subnet part of the address at 8, 16 or 24 digits. In the usual notation, this will give us typical masks, like 255.255.255.0 etc. Also, in any subnet, two addresses are reserved for special use, namely "all zeroes" and "all ones". The smallest possible subnet will have an address space of 2 bits, i.e. 4 addresses, out of which 2 addresses are reserved. So this network can cater only for a connection between two hosts. If you want to have space for 25 addresses in each subnet, then a subnet with 16 addresses (4 bits) is too small, but a subnet of 32 addresses (5 bits) could work. This will give you the following structure: 192.168.x. 0 --31 32 -- 63 64 -- 95 96 -- 127 128 -- 159 160 -- 191 192 -- 223 224 -- 255 And remember, that you can't use the first and the last address in each subnet. Oh, and the subnet mask shall be 255.255.255.224 + 0 Votes each subnet should have it's own subinterface for router on a stick CG IT 3 years ago what's your route table look like? router has to know how to handle the frames.... + 0 Votes Issue is put to rest mcooper 3 years ago Thanks to everyone for replying to my problem so quickly! I really appreciate it! The problem was not in the routing or design, it is in the devices themselves (actually it was a picnic error, but blaming the devices is easier) Netman1958 told me to disable the firewalls on bother devices and try again. I should have already thought of that since that always caught me years ago in my CCNA courses. Anyway, I found that all the devices have something in common, they are all not computers - they are copiers, WAPs, NAS, etc. If I plugg in a laptop to their switch port, configure it to have the other devices IP address, I can successfully ping. I did not expect this to be the issues and I really did not think copiers would have a firewall (and on that note, I did not see anything like that in the configuration of the copier). Thanks again for all the help everyone.