Help with problem - can't ping localhost

Forums › Microsoft Windows › Help with problem - can't ping localhost

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 137974 15-Dec-2013 18:41

I'm having a weird problem. I noticed it because my MySQL backup failed (it's for XMBC). I can't ping localhost. I can ping other local addresses, I can use the internet, I just can't ping localhost.

I've reset my hosts file back to normal, that didn't do anything. My TCP settings are all set to automatic, IP4 only, IP6 disabled. Astrill VPN is installed but isn't currently loaded or running.

Any ideas? I'm stumped how to fix such a low level problem. Win 7-64, newly restored from a good system image to a new SSD after my last SSD failed, maybe 2 weeks ago. This backup was working fine last week.

ping localhost
Ping request could not find host localhost. Please check the name and try again.

ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

ping 192.168.1.10
Pinging 192.168.1.10 with 32 bytes of data:
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64

sfc /scannow
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 17% complete.

Windows Resource Protection could not perform the requested operation.

freitasm

BDFL - Memuneh
64691 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 952637 15-Dec-2013 18:44

It seems name resolution is affected, seeing that ping to 127.0.0.1 works.

Are you sure the hosts file has a line 127.0.0.1 localhost?

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 952650 15-Dec-2013 18:50

I ran a Microsoft fixed tool that reset my hosts file to this. The bold part is my emphasis.

# Copyright (c) 1993-2006 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handle within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

freitasm

BDFL - Memuneh
64691 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 952652 15-Dec-2013 18:53

Correct. I was wondering if there was a line perhaps pointing localhost to another IP - that was silly because if that was the case the IP would show up when doing ping.

Perhaps run Housecall?

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 952676 15-Dec-2013 19:34

This isn't good... housecall64 can't sense my internet connection. It says to connect to the internet and try again. Housecall32 started to run, but hit an error and can't get past about 20 seconds in.

I'm also running Spybot and MSE. Any other suggestions?

freitasm

BDFL - Memuneh
64691 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 952687 15-Dec-2013 20:04

Updated network driver lately?

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 952691 15-Dec-2013 20:16

Nope. Spybot tells me I have a trojan, Win32.downloader.gen. It says it can remove it, but I'm getting malware bytes too.

I installed OpenOffice today, nothing else I can think of recently. Damn.

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 952727 15-Dec-2013 21:20

Ok, virus fixed, and the following line is in my hosts file. I still can't ping localhost. Any other ideas? Thanks for the virus check idea, turned out to be a red herring but valuable.

127.0.0.1 localhost

gstarkey

74 posts

Master Geek

# 952748 15-Dec-2013 21:55

One person supports this post

Is the hash at the start of this line in you hosts file correct ??:
# 127.0.0.1 localhost
I thought that made the line a comment, try removing the hash

yitz

1403 posts

Uber Geek

# 952755 15-Dec-2013 22:00

Why would resolution of 'localhost' be handled by DNS??
As above, it's not working because you've modified the hosts file.

freitasm

BDFL - Memuneh
64691 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 952804 15-Dec-2013 22:45

My own hosts file has a comment in front of 127.0.0.1 localhost. It's how Windows works now.

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

alexx

635 posts

Ultimate Geek

# 952834 16-Dec-2013 02:10

Is there any particular reason IPV6 is disabled and how was it disabled?
I suspect your system might still be trying to use IPV6 to reach localhost.

Perhaps this helps?
http://bobstrand.com/totm/2010/04/hey-dude-wheres-my-localhost/

#include <standard.disclaimer>

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 952847 16-Dec-2013 07:21

I've tried with and without the hash in front of the "127.0.0.1 localhost" line. IP6 has been disabled for a year.

I'll try enabling IP6 in case it's Microsoft having done something silly with their updates, thanks. Doesn't sound like it.

I may just have to tweak the configuration of things to use 127.0.0.1, MySQL especially.

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 953946 17-Dec-2013 21:06

Well I still can't connect to localhost, regardless of whether IP6 is enabled. This could be related to the VPN client, I'll try uninstalling that tomorrow.

For now though, the reason I found the problem is the mysql backup problem.

C:\wamp\bin\mysql\mysql5.5.16\bin\mysqldump -h 192.168.1.10 -P 3306 -uroot -premoved xmbcmusicdatabase32 > xmbcmusicdatabase32.sql

mysqldump: Got error: 2004: Can't create TCP/IP socket (87) when trying to connect

Why is it trying to connect to port 87? I've tried it with and without the -P parameter. There's nothing on 87, but MySQL works fine on 3306.

Puzzling.

timmmay

15255 posts

Uber Geek

Trusted

Subscriber

# 956564 23-Dec-2013 13:43

One person supports this post

I tracked down the problem - it was the Astrill VPN software. Once I uninstalled that the ping worked, and it kept working after I reinstalled Astrill. Strange.