asked on

Using private ip for a server!

Hi there.

I want to know what are the consecuences of using a private ip address like 192.168.x.x for a server.
and also what happens if someone use public IP for a private network?

thanks

Lee W, MVP

Public IP for a private network is fine, but not recommended. You can use a private IP for a server, but no one on the internet will be able to access it unless you use NAT or a Proxy server and forward the ports for the services you want public.

Pete Long

correct private ranges like

192.168.x.x
172.16.x.x
10.x.x.x
169.254.x.x

are unable to be routed (without NAT or PAT as outlined above) My servers have Private IP's and public IP's simply because Ive got three registered class C networks - these days thats not an option so people use "whatever they want" and simply NAT/PAT it on a router or firewall

ASKER CERTIFIED SOLUTION

Les Moore

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Chris Dent

Just wanted to add a really minor point.

The 169.254 range should really be avoided really, that one is the default address range for DHCP clients (the one they get if no DHCP is available). So there's some potential for IP Conflicts there.

That still leaves three ranges (Class A, B and C) to play with, giving you an impressive total number of addresses to use (as Pete posted).

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

Pete Long

Chris is correct

but you wont get a conflict if you use this range staticly - any AIPA compliant machine will check a 169.254 IP address is not in use before it awards it to itself