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
sm_billyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
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.
0
Pete LongTechnical ConsultantCommented:
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
0
lrmooreCommented:
While it is true that using NAT you can use virtually an network - public or private - on your local LAN, be aware that if you just pull a network out of your hat, like 198.133.219.0
Sounds pretty random, right? Well, if you were to use that particular network in your local lan, then you would never be able to go to http://www.cisco.com because it would always resolve to a local address...
Same if you picked something like 64.156.132.0, then you would never be able to get to http://www.experts-exchange.com ..

You would have to be careful to pick an IP address that nobody is using with a commercial web site that your users might want to visit some day. The IETF has taken that guesswork out of it by creating the set of "private" ip ranges as Pete has posted (see RFC 1918).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris DentPowerShell DeveloperCommented:

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
0
Pete LongTechnical ConsultantCommented:
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
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Broadband

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.