How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.
How to change 'localhost' ip address on workstation
Hello Experts
This is a very easy one.
Can someone please show me how to change the ip address of the 'localhost' on my pc.
I believe there is somekind of 'host' or 'winhost' file that I need to change.
At the moment if I ping localhost it comes up with 127.0.0.1, which we all know is the loopback address. I want to change it to specific ip address.
Cheers
Carlton
This is a very easy one.
Can someone please show me how to change the ip address of the 'localhost' on my pc.
I believe there is somekind of 'host' or 'winhost' file that I need to change.
At the moment if I ping localhost it comes up with 127.0.0.1, which we all know is the loopback address. I want to change it to specific ip address.
Cheers
Carlton
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I recommend against changing localhost to any other IP address. You don't know how many other applications depend on that. Instead, find the IP address of your machine and use that. Here are two methods of finding your IP address: http://www.ehow.com/how_5621076_ip-address-windows-7.html
You need to take ownership of the %windir%\system32\drivers\
Then make a shortcut on your desktop with a target of
%windir%\notepad.exe "%windir%\system32\drivers
Start in: %windir%
and named HOSTS.
Then you can just open that shortcut when you want to make changes to HOSTS.
However, I don't really think you can change 'localhost' from 127.0.0.1 with HOSTS, as it's hard-coded... in fact ALL 127.x.x.x addresses are reserved for loopback, so if you ping 127.100.100.100 you will get a reply whether it's in HOSTS or not; if you change the loopback entry in HOSTS to
127.100.100.100 localhost
flushdns/registerdns and/or reboot, then do
ping -a 127.100.100.100
it will still not resolve to "localhost"
Then make a shortcut on your desktop with a target of
%windir%\notepad.exe "%windir%\system32\drivers
Start in: %windir%
and named HOSTS.
Then you can just open that shortcut when you want to make changes to HOSTS.
However, I don't really think you can change 'localhost' from 127.0.0.1 with HOSTS, as it's hard-coded... in fact ALL 127.x.x.x addresses are reserved for loopback, so if you ping 127.100.100.100 you will get a reply whether it's in HOSTS or not; if you change the loopback entry in HOSTS to
127.100.100.100 localhost
flushdns/registerdns and/or reboot, then do
ping -a 127.100.100.100
it will still not resolve to "localhost"
Doesn't it work the other way around, ping -a will resolve names to IPs but not the other way around? On this machine, 'localhost' resolves to '::1' which is the IPV6 version.
No... DNS resolves names to IPs.
Names are not needed at all to run a ping... when you ping a domain name it gets the IP from DNS and every hop along the path actually uses the IP address, not the name.
If you ping a reachable IP address no domain name is displayed; ping -a essentially does a reverse DNS lookup.
Names are not needed at all to run a ping... when you ping a domain name it gets the IP from DNS and every hop along the path actually uses the IP address, not the name.
If you ping a reachable IP address no domain name is displayed; ping -a essentially does a reverse DNS lookup.
what are you actually trying to achieve here, please?
Localhost is *supposed* to be the loopback address:
http://en.wikipedia.org/wiki/Localhost
If you can describe the actual problem, we can widen the scope of the answers.
Localhost is *supposed* to be the loopback address:
http://en.wikipedia.org/wiki/Localhost
If you can describe the actual problem, we can widen the scope of the answers.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial