A better solution - that would not have helped in your position though - when you need more than fluidity across a subnet is to use a Class B private address range which goes from 172.16.0.0 - 172.31.255.255 and subnet of 255.240.0.0 giving you just over 1 million hosts, or even freer rein is use a Class A private address range which is 10.0.0.0 with a subnet mask of 255.0.0.0 giving you millions of hosts - this is the range normally used corporately. For completeness Class C is 192.168.0.0 through to 192.168.255.255 with a mask of 255.255.0.0 giving 65k addresses.
It is very important that only these address ranges are used because they are 'unroutable' over the internet and they cannot 'escape' the edge into the public domain - this is important to ensure that we can have addresses to identify kit at home (and in the office) but still leave addresses for IP traffic (we have actually ran out, hence a new system called IPv6 which is now being used)
It is a very complex subject, suffice to say that there are very good reasons why the 192.168.x.x is used for consumer equipment and most manufacturers are clever and either use DHCP (preferred solution) although some use 'smart ip' static addresses (which are similar to DHCP - ish).
Unfortunately I think that some people and companies try to make things difficult by using static addresses Lenz, Roco and Digikeijs being good examples in our world and none of them providing decent instructions to help the consumer who then have to fall back on what they find online, and that isn't always the best of advice - I cannot count the number of home networks I have had to rescue due to very poor advice having been given down the pub by the local 'expert'
but yiu are sorted and hopefully a few have learned a bit to help themselves along the way