increase IP hosts

  • Thread starter Thread starter tray
  • Start date Start date
T

tray

I've got about 220+ hosts on a private network of 192.0.0.x (the Company's
major vendor set up IP range - before my time). *Not* DHCP. We will never
grow very large, but with switches, network printers, etc max size should be
approx 280 hosts. (private network is behind NAT/Firewall)

Company doesn't want to use any routers.

I've seen people talking about super netting, using a class B network mask,
such as just using 255.255.0.0 as SubnetMask. Will that work?

If I use network mask of 255.555.254.0 will that allow me to use IPs from
192.0.0.1 - 192.0.1.254, effectively doubling my existing hosts(although I
don't need double)?

Thanks,
Tray
 
tray said:
I've got about 220+ hosts on a private network of 192.0.0.x (the
Company's
major vendor set up IP range - before my time). *Not* DHCP. We will never
grow very large, but with switches, network printers, etc max size should
be
approx 280 hosts. (private network is behind NAT/Firewall)

Company doesn't want to use any routers.

I've seen people talking about super netting, using a class B network
mask,
such as just using 255.255.0.0 as SubnetMask. Will that work?

If I use network mask of 255.555.254.0 will that allow me to use IPs from
192.0.0.1 - 192.0.1.254, effectively doubling my existing hosts(although I
don't need double)?

Thanks,
Tray
correct
Click to expand...
 
tray said:
If I use network mask of 255.555.254.0 will that allow me to use IPs from
192.0.0.1 - 192.0.1.254, effectively doubling my existing hosts(although I
don't need double)?
Click to expand...

Yes.

But you will never be able to access any Internet sites that use the same
IP#. You should consider a plan to eventually change to an RFC Private IP
Set.
 
Phillip Windell said:
Yes.

But you will never be able to access any Internet sites that use the same
IP#. You should consider a plan to eventually change to an RFC Private IP
Set.
Click to expand...

Arhh missed that one, privte range is 192.168.x.x
 
Thanks!

Reference the Private IP range (and DHCP); I have tried to plan a move to
both an RFC Private IP Set and installing a DHCP server. Answer to both from
the powers-that-be is:
If it can be made to work staying with 192.0.0.x and no DHCP, then whats the
problem?
Tray
 
tray said:
................. Answer to both from
the powers-that-be is:
If it can be made to work staying with 192.0.0.x and no DHCP, then whats the
problem?
Click to expand...

But that is just it,...it doesn't work properly, they just aren't aware of
it well enough to know that is isn't. Since they use an IP block they don't
actually "own",...there is somebody out there in Internet Land who does own
them,...there is probably multiple "somebodys" out there because not many
ISP customers would have a whole block of 254 hosts. If at anytime you try
to access any type of Internet resource that DNS resolves to an address
within 192.0.x.x it will be unreachable to you because your system will
interpret it to be a destination on your own LAN.

You could start with them by listing the people who do own those addresses
if you can locate them.

http://ws.arin.net/cgi-bin/whois.pl?queryinput=! NET-192-0-0-0-1
 
Back
Top