We actually have one client with a Class B (255.255.0.0) network and I have to say...we really like it. Gives us a LOT of flexibility in our addressing. 172.23.x.x is their scheme. 172.23.1.x are servers, 172.23.2.x, 172.23.22.x and 172.23.222.x are workstations served up by their DHCP servers. 172.23.3.x are printers and other network attached devices, etc..
Of course, that network was set up that way from the beginning. I'm not sure I'd want to have to go back thru and readdress everything that way on an existing network, but I'd think about it at least. Ben M. Schorr Chief Executive Officer ______________________________________________ Roland Schorr & Tower www.rolandschorr.com <http://www.rolandschorr.com/> b...@rolandschorr.com From: Jeff Johnson [mailto:jjohn...@hydraflowusa.com] Sent: Thursday, December 17, 2009 11:15 AM To: NT System Admin Issues Subject: RE: Need more IP addresses I thought about that, but then I also thought that opening a network that large would cause other problems. The following is a good approximation of my network. All are located in one building with future expansion to across the parking lot in 5+ years. 175 DHCP assigned PC's 15 Static ip PC's 10 Servers with Static IP's 12 Printers with static IP's 15 Network devices (switches/AP's) with reserved addresses. 20 Static IP "Other" devices Jeff Johnson Systems Administrator 714-773-2600 Office 714-773-6351 Fax From: John Aldrich [mailto:jaldr...@blueridgecarpet.com] Sent: Thursday, December 17, 2009 1:05 PM To: NT System Admin Issues Subject: RE: Need more IP addresses Why not just change your netmask to 255.255.0.0? That should be more IPs than you will EVER use! J From: Jeff Johnson [mailto:jjohn...@hydraflowusa.com] Sent: Thursday, December 17, 2009 3:49 PM To: NT System Admin Issues Subject: Need more IP addresses I am in need of more IP addresses on my network. My current network looks like this: 192.168.1.x 255.255.255.0 I am using 248 IP's currently, so I have very little expansion available. I do see the potential to increase in the following year, so I had better get my butt thinking about this soon. Plus I have Christmas and New Year's holidays that I could work with no one on our network for 3 full days. I am thinking about changing my subnet to something like 255.255.254.0 or 255.255.252.0. Would this be a good way, or would I be better adding an additional router and just creating a new 255.255.255.0 network on 192.168.2.x? I guess my question is which is the "correct" way? Jeff Johnson Systems Administrator 714-773-2600 Office 714-773-6351 Fax ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<image001.jpg>>
<<image002.jpg>>
<<image003.jpg>>
