Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 1 down vote favorite

I have a big problem on my Windows Server 2008 Enterprise x64 SP2 non-R2:

There is no ping to 127.0.0.1: Request timeout. Ping to ::1 (localhost on IPv6) is still alive.

I mean, server has no interface 127.0.0.1 at all! So ping absence is just a tip of an iceberg..

I found that problem appears after starting Routing and Remote Access service (RRAS). I have next configuration there:

  • 1 NIC called LAN (10.0.0.0)
  • 1 NIC called WAN (192.168.112.0)
  • and a persistent PPPoE connection to internet over it called Inet

And one static route making Inet to be default route: 0.0.0.0 mask 0.0.0.0 metric 1

After starting server, 127.0.0.1 can be pinged. After starting RAS server - not.

Has anybody the same problem? How can it be fixed? I was asking the same question on TechNet but got no answer.

Here is route print -4 output: http://pastebin.com/d767d7c5a

share|improve this question
Can you post the full output of route print? Is it possible to ping the server from another system? What are the firewall settings like? – pehrs Jan 1 '10 at 13:56
Granted that you should be able to ping 127.0.0.1, but why is it such a big problem? 127.0.0.1 is a loopback address and shouldn't affect networking on the server otherwise. – joeqwerty Jan 1 '10 at 16:27
1  
I need localhost because many server applications binds themselves to 127.0.0.1:port, e.g. MySQL, Tomcat in VMware Server, etc – abatishchev Jan 1 '10 at 19:40
Thanks for interesting in my question. I have edited my post. Only default Windows Firewall. Turning it off doesn't helped. Pinging all other interfaces (::1, 10.0.0.1, 192.168.112.45, 81.200.116.70) goes fine! o_O – abatishchev Jan 1 '10 at 19:44
joeqwerty, the number of things that rely on the loopback interface is massive, MySQL and Tomcat are just two of them. – Mark Henderson♦ Jan 1 '10 at 22:06
show 3 more comments

2 Answers

up vote 0 down vote accepted 
netsh int ip reset

has fixed the issue!

share|improve this answer
up vote -1 down vote

The interface 127.0.0.1 can come from your hosts file. It's well worth checking to see if it exists. I don't quite know how RRAS would change this, but it still deserves checking.

Open up the file %SYSTEMDRIVE%\windows\system32\drivers\etc\hosts in notepad and see if there is a line:

127.0.0.1       localhost

If there isn't add it. It might fix all your problems. It's not ideal, but it should be a sufficient bandaid.

share|improve this answer
Hi. Thanks for answer. I think it's better to say that name localhost comes from the hosts file. Without it only IP addresses exists. But I can be wrong. Hosts file on the server contains both records. I have already checked it. – abatishchev Jan 2 '10 at 22:19
Sorry, you're right about the wording. The 'name', not the interface. My mistake! – Mark Henderson♦ Jan 3 '10 at 0:01

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.