Oh and a couple of little ancillary things.

One, networks these days are written in the style of (to use examples from above) 10.134.75.0/24 and 10.134.0.0/16 or even 10.134.75/24 and 10.134/16. The number after the slash indicates the number of leading ones in the binary representation of the subnet mask. Subnet masks can be other than /8, /16, and /24, too, if you weren't aware of that.

Two, because of the way I've described them working before, subnet masks between two computers on the same segment can be mismatched and still work as long as both of their addresses are within the subnet of the more restrictive one. That is a computer configured as 10.134.75.4/24 and another as 10.134.75.5/16 can still communicate, but ones configured as 10.134.75.4/24 and 10.134.64.5/16 cannot. In fact, in the second case, the latter can talk to the former, but the former cannot talk back correctly, as it would be sending its response to its router. Now, its router might actually figure it out and pass it along or it might not, depending on configuration, and I've encountered this before and it couses quite the netowrk slowdown. In most cases, the default configuration will not allow the response to work at all, though. But simplex communication will work. Keep in mind that all TCP connections require duplex communication, though.