saunaG
asked on
is 192.1.1.x a public or private ip address?
A few years ago when we setup our office network the vendor made our network address 192.1.1.x with a subnet of 255.255.255.0
At the time he said this was reserved for private networks but when i look around it looks like 192.168.x.x is what we should be using as private network addresses.
Is 192.1.1.x private and are we going to run into any problems if we continue using it?
Thanks,
Tom
At the time he said this was reserved for private networks but when i look around it looks like 192.168.x.x is what we should be using as private network addresses.
Is 192.1.1.x private and are we going to run into any problems if we continue using it?
Thanks,
Tom
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In order to insure your network is not routable, you should change it.
192.168.X.X is the IANA reserved for private address range in the class C network space.
However, if you have had no issues, I wouldn't truly worry about it.
192.168.X.X is the IANA reserved for private address range in the class C network space.
However, if you have had no issues, I wouldn't truly worry about it.
...yeah it's 192.168.x.x not 192.x.x.x that's considered private
Wouldn't use that vendor again though ;)
ASKER
yeah.... its a private network...
no biggie, i don't think its worth the hassle to go to 192.168.x.x
no biggie, i don't think its worth the hassle to go to 192.168.x.x
Probably not unless you really need to get to 192.1.1.x addresses one day. Maybe if it was your supplier's website or something. Pretty low chance though as has been stated above.
Just worth bearing in mind I guess if you add anymore subnets or if ever you are changing the addressing.
Actually now I think of it in your other question https://www.experts-exchange.com/questions/21359119/Configuring-multiple-NICs-on-Win-2003.html you are following my recommendation to create a second subnet for the second card in your server. Might be a good idea to make it 192.168.2.100 instead of 192.1.2.100 now whilst it is easy.
Just worth bearing in mind I guess if you add anymore subnets or if ever you are changing the addressing.
Actually now I think of it in your other question https://www.experts-exchange.com/questions/21359119/Configuring-multiple-NICs-on-Win-2003.html you are following my recommendation to create a second subnet for the second card in your server. Might be a good idea to make it 192.168.2.100 instead of 192.1.2.100 now whilst it is easy.
Sunray