CIDR makes a network mask of anything a doable. (well except your subnet mask == fish or something)

you want a /23 CIDR network. (255.255.255.254.0 is th old stle associated with Class A B C stuff)

512 addresses total 510 usable.

Unless you have very bad ethernet "shared" hubs and have ZERO switches... you should be alraight.

Especially now a days with GigE uplinks and so on.

Old Netw-orking stuffs:

192.168.3.0 == network
192.168.3.255 == broadcast
255.255.255.0 == netmask
192.168.3.1 == default gateway

New netw-orking stuffs:

192.168.2.0 == network
192.168.3.255 == broadcast
255.255.254.0 == netmask
192.168.3.1 == default gateway

Eventually everything will be on the new stuff. Just make sure you change the servers and routers manually to the new netmask. It'll be a bit weird, but only for a bit.

And BTW, this will work despite what others tell you. It is never mentioned, mainly because it is messy to explain why it will work. The only reall thing you need to make sure happens is the default route stays the same value. Variable netmasks on the same network is supported by most networking gear made since CIDR has been around.

The only downside, is it'll be a bit chatty for a while.

Most everything else will correct themselves within a short time.

The thing about it is, change the DHCP server conf. Don't revoke the leases. Let them renew, or when Windows reboots (as seldom as that happens... ) as long as the DHCP server is responding... you are good to go.

One last thing, if the servers are on the 192.168.3 netowrk right now... do not put them on the 192.168.2 network until everything is settled.

SELECT * FROM scog WHERE ethics > 0;

0 rows returned.