Can't ping localhost/or reach locally hosted domain
I can’t reach a locally hosted domain, and in testing I have discovered I can’t ping localhost or the actual IP either. The OS is Windows7 64bit, Pro.
DNS works, I can ping others on my network, they can ping me, and they can reach the hosted domain. The only problem I have found is that I can’t reach the locally hosted domains!
C:Usersian>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : leda
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hcs
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hcs
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethern
et Controller
Physical Address. . . . . . . . . : 00-23-54-7C-E2-2A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network #2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
Physical Address. . . . . . . . . : 08-00-27-00-88-4A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.205.215(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
C:Usersian>ping localhost
Pinging leda [127.0.0.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>ping coachmaster.leda.hcs
Pinging coachmaster.leda.hcs [192.168.0.12] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>
I can reach a hosted VM in VirtualBox and the VM can browse the hosted sites.
I’ve removed Zone Alarm and disabled Windows Firewall - same results.
So how can I browse my locally hosted sited? What could be blocking it?
windows-7 networking localhost
add a comment |
I can’t reach a locally hosted domain, and in testing I have discovered I can’t ping localhost or the actual IP either. The OS is Windows7 64bit, Pro.
DNS works, I can ping others on my network, they can ping me, and they can reach the hosted domain. The only problem I have found is that I can’t reach the locally hosted domains!
C:Usersian>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : leda
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hcs
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hcs
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethern
et Controller
Physical Address. . . . . . . . . : 00-23-54-7C-E2-2A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network #2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
Physical Address. . . . . . . . . : 08-00-27-00-88-4A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.205.215(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
C:Usersian>ping localhost
Pinging leda [127.0.0.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>ping coachmaster.leda.hcs
Pinging coachmaster.leda.hcs [192.168.0.12] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>
I can reach a hosted VM in VirtualBox and the VM can browse the hosted sites.
I’ve removed Zone Alarm and disabled Windows Firewall - same results.
So how can I browse my locally hosted sited? What could be blocking it?
windows-7 networking localhost
My old netgear router does that sometimes. All my computers can reach outside ip's but no internal ip's. I just pull the power out of it and wait 30s and then power it up again and the problem is gone (for a month or so).
– Nifle
Jun 20 '10 at 20:14
I tried the equivalent - turn everything off, restart the linux firewall, restart the rest. It helped me see all the correct machines. But I still can't ping the local machine's IP (192.168.0.?? or 127.0.0.1) from inside, yet others can ping me. Very strange.
– Ian
Jun 21 '10 at 21:31
Did you ever figure it out? If the others could reach it but not that one system, then the first thing to check would be thehosts
file.
– Synetech
Jan 6 '14 at 0:29
Try also showing routing table (netstat -nr). Can you ping 192.168.0.12 ? In school, I was taught to re-install the TCP/IP network stack to resolve if cannot ping 127.0.0.1 (although I don't recall having come across that).
– TOOGAM
May 27 '17 at 3:44
add a comment |
I can’t reach a locally hosted domain, and in testing I have discovered I can’t ping localhost or the actual IP either. The OS is Windows7 64bit, Pro.
DNS works, I can ping others on my network, they can ping me, and they can reach the hosted domain. The only problem I have found is that I can’t reach the locally hosted domains!
C:Usersian>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : leda
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hcs
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hcs
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethern
et Controller
Physical Address. . . . . . . . . : 00-23-54-7C-E2-2A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network #2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
Physical Address. . . . . . . . . : 08-00-27-00-88-4A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.205.215(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
C:Usersian>ping localhost
Pinging leda [127.0.0.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>ping coachmaster.leda.hcs
Pinging coachmaster.leda.hcs [192.168.0.12] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>
I can reach a hosted VM in VirtualBox and the VM can browse the hosted sites.
I’ve removed Zone Alarm and disabled Windows Firewall - same results.
So how can I browse my locally hosted sited? What could be blocking it?
windows-7 networking localhost
I can’t reach a locally hosted domain, and in testing I have discovered I can’t ping localhost or the actual IP either. The OS is Windows7 64bit, Pro.
DNS works, I can ping others on my network, they can ping me, and they can reach the hosted domain. The only problem I have found is that I can’t reach the locally hosted domains!
C:Usersian>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : leda
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hcs
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hcs
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethern
et Controller
Physical Address. . . . . . . . . : 00-23-54-7C-E2-2A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network #2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
Physical Address. . . . . . . . . : 08-00-27-00-88-4A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.205.215(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
C:Usersian>ping localhost
Pinging leda [127.0.0.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>ping coachmaster.leda.hcs
Pinging coachmaster.leda.hcs [192.168.0.12] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:Usersian>
I can reach a hosted VM in VirtualBox and the VM can browse the hosted sites.
I’ve removed Zone Alarm and disabled Windows Firewall - same results.
So how can I browse my locally hosted sited? What could be blocking it?
windows-7 networking localhost
windows-7 networking localhost
edited Feb 20 '15 at 21:27
JakeGould
31k1093137
31k1093137
asked Jun 20 '10 at 20:06
Ian
16126
16126
My old netgear router does that sometimes. All my computers can reach outside ip's but no internal ip's. I just pull the power out of it and wait 30s and then power it up again and the problem is gone (for a month or so).
– Nifle
Jun 20 '10 at 20:14
I tried the equivalent - turn everything off, restart the linux firewall, restart the rest. It helped me see all the correct machines. But I still can't ping the local machine's IP (192.168.0.?? or 127.0.0.1) from inside, yet others can ping me. Very strange.
– Ian
Jun 21 '10 at 21:31
Did you ever figure it out? If the others could reach it but not that one system, then the first thing to check would be thehosts
file.
– Synetech
Jan 6 '14 at 0:29
Try also showing routing table (netstat -nr). Can you ping 192.168.0.12 ? In school, I was taught to re-install the TCP/IP network stack to resolve if cannot ping 127.0.0.1 (although I don't recall having come across that).
– TOOGAM
May 27 '17 at 3:44
add a comment |
My old netgear router does that sometimes. All my computers can reach outside ip's but no internal ip's. I just pull the power out of it and wait 30s and then power it up again and the problem is gone (for a month or so).
– Nifle
Jun 20 '10 at 20:14
I tried the equivalent - turn everything off, restart the linux firewall, restart the rest. It helped me see all the correct machines. But I still can't ping the local machine's IP (192.168.0.?? or 127.0.0.1) from inside, yet others can ping me. Very strange.
– Ian
Jun 21 '10 at 21:31
Did you ever figure it out? If the others could reach it but not that one system, then the first thing to check would be thehosts
file.
– Synetech
Jan 6 '14 at 0:29
Try also showing routing table (netstat -nr). Can you ping 192.168.0.12 ? In school, I was taught to re-install the TCP/IP network stack to resolve if cannot ping 127.0.0.1 (although I don't recall having come across that).
– TOOGAM
May 27 '17 at 3:44
My old netgear router does that sometimes. All my computers can reach outside ip's but no internal ip's. I just pull the power out of it and wait 30s and then power it up again and the problem is gone (for a month or so).
– Nifle
Jun 20 '10 at 20:14
My old netgear router does that sometimes. All my computers can reach outside ip's but no internal ip's. I just pull the power out of it and wait 30s and then power it up again and the problem is gone (for a month or so).
– Nifle
Jun 20 '10 at 20:14
I tried the equivalent - turn everything off, restart the linux firewall, restart the rest. It helped me see all the correct machines. But I still can't ping the local machine's IP (192.168.0.?? or 127.0.0.1) from inside, yet others can ping me. Very strange.
– Ian
Jun 21 '10 at 21:31
I tried the equivalent - turn everything off, restart the linux firewall, restart the rest. It helped me see all the correct machines. But I still can't ping the local machine's IP (192.168.0.?? or 127.0.0.1) from inside, yet others can ping me. Very strange.
– Ian
Jun 21 '10 at 21:31
Did you ever figure it out? If the others could reach it but not that one system, then the first thing to check would be the
hosts
file.– Synetech
Jan 6 '14 at 0:29
Did you ever figure it out? If the others could reach it but not that one system, then the first thing to check would be the
hosts
file.– Synetech
Jan 6 '14 at 0:29
Try also showing routing table (netstat -nr). Can you ping 192.168.0.12 ? In school, I was taught to re-install the TCP/IP network stack to resolve if cannot ping 127.0.0.1 (although I don't recall having come across that).
– TOOGAM
May 27 '17 at 3:44
Try also showing routing table (netstat -nr). Can you ping 192.168.0.12 ? In school, I was taught to re-install the TCP/IP network stack to resolve if cannot ping 127.0.0.1 (although I don't recall having come across that).
– TOOGAM
May 27 '17 at 3:44
add a comment |
4 Answers
4
active
oldest
votes
Two things first is that you can't browse your locally hosted domain. If you are using a proxy server to reach the internet you need to tell your browser to ignore 192.168.0.0/24 inf Firefox or 192.168.0.* in IE. network or just try direct internet connection without your proxy. As for ping, I would normally assume that ICMP Echo is disabled hence no ping replies, but this is not the case as others are able to ping you.
Another good test is to open a telnet connection to port 80:
telnet 192.168.0.12 80
I don't know you mean by can't browse locally hosted domain - I can reach locally hosted websites in Win2K, WinXP, and Linux. But not this Win7 machine. All sites go direct - no proxy (NAT firewall). Ping is enabled, and telnet is not installed. Even more confusing - after waiting for 2 hours I can now reach the website, but still not ping localhost or domain. All I've changed is a backup script, and been browsing the internet.
– Ian
Jun 20 '10 at 22:52
add a comment |
ipconfig /release
ipconfig /renew
might help.
Thanks John - it made no difference :(
– Ian
Jun 21 '10 at 21:33
add a comment |
I would take it off the domain, reboot... set it to dhcp... put it back on the domain with dhcp. The "ipconfig /release" and "ipconfig /renew" mentioned by John above should have fixed the issue. I think there is another host using the defined ip...
add a comment |
not a real solution, but you can use "leda" instead of "localhost". the DNS cliente should translate to 192.168....
"localhost" name is managed by the DNS, but I understand the DNS client never request the address to the DNS but uses the local address instead.
This is very weird.
btw, the router has nothing to do with this, localhost is localhost, no outsidehost...
how is your host file? maybe is damaged, some viruses likes to modify hosts for disabling some AV features. windowssystem32driversetc
– Alex Angelico
Dec 17 '10 at 21:28
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f154778%2fcant-ping-localhost-or-reach-locally-hosted-domain%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Two things first is that you can't browse your locally hosted domain. If you are using a proxy server to reach the internet you need to tell your browser to ignore 192.168.0.0/24 inf Firefox or 192.168.0.* in IE. network or just try direct internet connection without your proxy. As for ping, I would normally assume that ICMP Echo is disabled hence no ping replies, but this is not the case as others are able to ping you.
Another good test is to open a telnet connection to port 80:
telnet 192.168.0.12 80
I don't know you mean by can't browse locally hosted domain - I can reach locally hosted websites in Win2K, WinXP, and Linux. But not this Win7 machine. All sites go direct - no proxy (NAT firewall). Ping is enabled, and telnet is not installed. Even more confusing - after waiting for 2 hours I can now reach the website, but still not ping localhost or domain. All I've changed is a backup script, and been browsing the internet.
– Ian
Jun 20 '10 at 22:52
add a comment |
Two things first is that you can't browse your locally hosted domain. If you are using a proxy server to reach the internet you need to tell your browser to ignore 192.168.0.0/24 inf Firefox or 192.168.0.* in IE. network or just try direct internet connection without your proxy. As for ping, I would normally assume that ICMP Echo is disabled hence no ping replies, but this is not the case as others are able to ping you.
Another good test is to open a telnet connection to port 80:
telnet 192.168.0.12 80
I don't know you mean by can't browse locally hosted domain - I can reach locally hosted websites in Win2K, WinXP, and Linux. But not this Win7 machine. All sites go direct - no proxy (NAT firewall). Ping is enabled, and telnet is not installed. Even more confusing - after waiting for 2 hours I can now reach the website, but still not ping localhost or domain. All I've changed is a backup script, and been browsing the internet.
– Ian
Jun 20 '10 at 22:52
add a comment |
Two things first is that you can't browse your locally hosted domain. If you are using a proxy server to reach the internet you need to tell your browser to ignore 192.168.0.0/24 inf Firefox or 192.168.0.* in IE. network or just try direct internet connection without your proxy. As for ping, I would normally assume that ICMP Echo is disabled hence no ping replies, but this is not the case as others are able to ping you.
Another good test is to open a telnet connection to port 80:
telnet 192.168.0.12 80
Two things first is that you can't browse your locally hosted domain. If you are using a proxy server to reach the internet you need to tell your browser to ignore 192.168.0.0/24 inf Firefox or 192.168.0.* in IE. network or just try direct internet connection without your proxy. As for ping, I would normally assume that ICMP Echo is disabled hence no ping replies, but this is not the case as others are able to ping you.
Another good test is to open a telnet connection to port 80:
telnet 192.168.0.12 80
answered Jun 20 '10 at 21:26
Ravi Chhabra
15017
15017
I don't know you mean by can't browse locally hosted domain - I can reach locally hosted websites in Win2K, WinXP, and Linux. But not this Win7 machine. All sites go direct - no proxy (NAT firewall). Ping is enabled, and telnet is not installed. Even more confusing - after waiting for 2 hours I can now reach the website, but still not ping localhost or domain. All I've changed is a backup script, and been browsing the internet.
– Ian
Jun 20 '10 at 22:52
add a comment |
I don't know you mean by can't browse locally hosted domain - I can reach locally hosted websites in Win2K, WinXP, and Linux. But not this Win7 machine. All sites go direct - no proxy (NAT firewall). Ping is enabled, and telnet is not installed. Even more confusing - after waiting for 2 hours I can now reach the website, but still not ping localhost or domain. All I've changed is a backup script, and been browsing the internet.
– Ian
Jun 20 '10 at 22:52
I don't know you mean by can't browse locally hosted domain - I can reach locally hosted websites in Win2K, WinXP, and Linux. But not this Win7 machine. All sites go direct - no proxy (NAT firewall). Ping is enabled, and telnet is not installed. Even more confusing - after waiting for 2 hours I can now reach the website, but still not ping localhost or domain. All I've changed is a backup script, and been browsing the internet.
– Ian
Jun 20 '10 at 22:52
I don't know you mean by can't browse locally hosted domain - I can reach locally hosted websites in Win2K, WinXP, and Linux. But not this Win7 machine. All sites go direct - no proxy (NAT firewall). Ping is enabled, and telnet is not installed. Even more confusing - after waiting for 2 hours I can now reach the website, but still not ping localhost or domain. All I've changed is a backup script, and been browsing the internet.
– Ian
Jun 20 '10 at 22:52
add a comment |
ipconfig /release
ipconfig /renew
might help.
Thanks John - it made no difference :(
– Ian
Jun 21 '10 at 21:33
add a comment |
ipconfig /release
ipconfig /renew
might help.
Thanks John - it made no difference :(
– Ian
Jun 21 '10 at 21:33
add a comment |
ipconfig /release
ipconfig /renew
might help.
ipconfig /release
ipconfig /renew
might help.
answered Jun 21 '10 at 14:04
John
961716
961716
Thanks John - it made no difference :(
– Ian
Jun 21 '10 at 21:33
add a comment |
Thanks John - it made no difference :(
– Ian
Jun 21 '10 at 21:33
Thanks John - it made no difference :(
– Ian
Jun 21 '10 at 21:33
Thanks John - it made no difference :(
– Ian
Jun 21 '10 at 21:33
add a comment |
I would take it off the domain, reboot... set it to dhcp... put it back on the domain with dhcp. The "ipconfig /release" and "ipconfig /renew" mentioned by John above should have fixed the issue. I think there is another host using the defined ip...
add a comment |
I would take it off the domain, reboot... set it to dhcp... put it back on the domain with dhcp. The "ipconfig /release" and "ipconfig /renew" mentioned by John above should have fixed the issue. I think there is another host using the defined ip...
add a comment |
I would take it off the domain, reboot... set it to dhcp... put it back on the domain with dhcp. The "ipconfig /release" and "ipconfig /renew" mentioned by John above should have fixed the issue. I think there is another host using the defined ip...
I would take it off the domain, reboot... set it to dhcp... put it back on the domain with dhcp. The "ipconfig /release" and "ipconfig /renew" mentioned by John above should have fixed the issue. I think there is another host using the defined ip...
answered Apr 25 '15 at 17:15
Logman
3,26711127
3,26711127
add a comment |
add a comment |
not a real solution, but you can use "leda" instead of "localhost". the DNS cliente should translate to 192.168....
"localhost" name is managed by the DNS, but I understand the DNS client never request the address to the DNS but uses the local address instead.
This is very weird.
btw, the router has nothing to do with this, localhost is localhost, no outsidehost...
how is your host file? maybe is damaged, some viruses likes to modify hosts for disabling some AV features. windowssystem32driversetc
– Alex Angelico
Dec 17 '10 at 21:28
add a comment |
not a real solution, but you can use "leda" instead of "localhost". the DNS cliente should translate to 192.168....
"localhost" name is managed by the DNS, but I understand the DNS client never request the address to the DNS but uses the local address instead.
This is very weird.
btw, the router has nothing to do with this, localhost is localhost, no outsidehost...
how is your host file? maybe is damaged, some viruses likes to modify hosts for disabling some AV features. windowssystem32driversetc
– Alex Angelico
Dec 17 '10 at 21:28
add a comment |
not a real solution, but you can use "leda" instead of "localhost". the DNS cliente should translate to 192.168....
"localhost" name is managed by the DNS, but I understand the DNS client never request the address to the DNS but uses the local address instead.
This is very weird.
btw, the router has nothing to do with this, localhost is localhost, no outsidehost...
not a real solution, but you can use "leda" instead of "localhost". the DNS cliente should translate to 192.168....
"localhost" name is managed by the DNS, but I understand the DNS client never request the address to the DNS but uses the local address instead.
This is very weird.
btw, the router has nothing to do with this, localhost is localhost, no outsidehost...
answered Dec 17 '10 at 21:24
Alex Angelico
557512
557512
how is your host file? maybe is damaged, some viruses likes to modify hosts for disabling some AV features. windowssystem32driversetc
– Alex Angelico
Dec 17 '10 at 21:28
add a comment |
how is your host file? maybe is damaged, some viruses likes to modify hosts for disabling some AV features. windowssystem32driversetc
– Alex Angelico
Dec 17 '10 at 21:28
how is your host file? maybe is damaged, some viruses likes to modify hosts for disabling some AV features. windowssystem32driversetc
– Alex Angelico
Dec 17 '10 at 21:28
how is your host file? maybe is damaged, some viruses likes to modify hosts for disabling some AV features. windowssystem32driversetc
– Alex Angelico
Dec 17 '10 at 21:28
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f154778%2fcant-ping-localhost-or-reach-locally-hosted-domain%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
My old netgear router does that sometimes. All my computers can reach outside ip's but no internal ip's. I just pull the power out of it and wait 30s and then power it up again and the problem is gone (for a month or so).
– Nifle
Jun 20 '10 at 20:14
I tried the equivalent - turn everything off, restart the linux firewall, restart the rest. It helped me see all the correct machines. But I still can't ping the local machine's IP (192.168.0.?? or 127.0.0.1) from inside, yet others can ping me. Very strange.
– Ian
Jun 21 '10 at 21:31
Did you ever figure it out? If the others could reach it but not that one system, then the first thing to check would be the
hosts
file.– Synetech
Jan 6 '14 at 0:29
Try also showing routing table (netstat -nr). Can you ping 192.168.0.12 ? In school, I was taught to re-install the TCP/IP network stack to resolve if cannot ping 127.0.0.1 (although I don't recall having come across that).
– TOOGAM
May 27 '17 at 3:44