PING 127.0.0.1 - no response !

I’ve been unable to setup ‘file sharing’ on my 2 year old (intel) imac OSX 10.5.8
Whilst investigating I’ve noticed that I get NO response from a terminal PING 127.0.0.1
command!
However the imac successfully connects to the internet and is able to PING my router!
I have very little non-Apple installed other than VM Fussion which I notice has set up some network aliases.
Anyone any idea why loopback does not work ?
Thanks

You're right - I had enabled stealth mode (I remember doing it now in response some security flaw, which I hope was fixed long ago)
Thank you

Similar Messages

Execute ping from cmd prompt and analyze response

I found how to execute the ping command in a cmd prompt window. Is there any way to redirect the output so I can analyze the response?

What version of TestStand are you using? I don't know when this was added but in 4.2, the screen looks like the image below.
Message Edited by Dennis Knutson on 02-17-2010 01:28 PM
Attachments:
Step Settings.PNG ‏28 KB

PING - Unknown host 127.0.0.1, Unknown host localhost

Hello,
I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems:
1. When I execute the command ping, I get weird results:
bash-3.00$ usr/sbin/ping localhost
usr/sbin/ping: unknown host localhost
bash-3.00$ usr/sbin/ping 127.0.0.1
usr/sbin/ping: unknown host 127.0.0.1
bash-3.00$ usr/sbin/ping ip_address1
usr/sbin/ping: unknown host ip_address12. When I execute
bash-3.00$ svcs -x I get:
svcs: Could not bind to repository server: repository server unavailable. Exiting.3. When I try to sftp or ssh another machine
bash-3.00$ sftp ip_address1
bash-3.00$ ssh ip_address1I receive the message:
Host key verification failed.although I am able to ssh/sftp the machine as root
4. When I ftp another machine
bash-3.00$ ftp ip_address1I get
unknown host or invalid literal address5. If I telnet another machine:
bash-3.00$ telnet ip_address1I receive
ip_address1: service name not available for the specified socket typeI need to add that all these commands work perfectly for root. I probably didn't copy some of the necessary configuration files/programs to the chrooted directory. But which ones?
Regards,
Przemek

Przemek198 wrote:
Hello,
I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems:When something works as root and not as a regular user, I think "permission problems".
1. When I execute the command ping, I get weird results:
bash-3.00$ usr/sbin/ping localhost
usr/sbin/ping: unknown host localhost
Here it appears that hostname resolution is different. Since that happens in the /etc/inet/hosts file (or possibly the /etc/inet/ipnodes file), I'd examine those and see if they are only readable by root for some reason. (And this would be within the chroot environment, since that's where the problem is).
Darren

127.0.0.1 unreachable when networking is functional

After a lot of networking experiments using virtual machines, virtual networks, bridges, etc, I discovered that ping 127.0.0.1 is no longer responding. This is the only thing that does not work: I am posting this message from the PC, I can watch online videos,
play online games... Even ping localhost works (through IPv6 though). I can't tell precisely when this anomaly appeared.
I reverted all the changes I made, rebooted a lot, disabled the firewall, without fixing the issue. I returned to a very simple configuration which I list below:
D:\Users\admin>ipconfig /all
Configuration IP de Windows
   Nom de l'hôte . . . . . . . . . . : Dragon64
   Suffixe DNS principal . . . . . . :
   Type de noeud. . . . . . . . . . : Hybride
   Routage IP activé . . . . . . . . : Non
   Proxy WINS activé . . . . . . . . : Non
Carte Ethernet Connexion au réseau local :
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
   Adresse physique . . . . . . . . . . . : 6C-F0-49-00-B1-27
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.0.3(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Bail obtenu. . . . . . . . . . . . . . : mercredi 24 décembre 2014 22:05:06
   Bail expirant. . . . . . . . . . . . . : dimanche 4 janvier 2015 11:24:03
   Passerelle par défaut. . . . . . . . . : 192.168.0.254
   Serveur DHCP . . . . . . . . . . . . . : 192.168.0.254
   Serveurs DNS. . . . . . . . . . . . . : 212.27.40.241
                                       212.27.40.240
   NetBIOS sur Tcpip. . . . . . . . . . . : Activé
Carte Tunnel isatap.{2936FE01-175A-43BC-A487-3484A508BE76} :
   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
Carte Tunnel Teredo Tunneling Pseudo-Interface :
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
   Adresse IPv6. . . . . . . . . . . . . .: 2001:0:9d38:90d7:3056:35ba:3f57:fffc(préféré)
   Adresse IPv6 de liaison locale. . . . .: fe80::3056:35ba:3f57:fffc%14(préféré)
   Passerelle par défaut. . . . . . . . . : ::
   NetBIOS sur TCPIP. . . . . . . . . . . : Désactivé
D:\Users\admin>route print
===========================================================================
Liste d'Interfaces
11...6c f0 49 00 b1 27 ......Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Carte Microsoft ISATAP
14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Table de routage
===========================================================================
Itinéraires actifs :
Destination réseau    Masque réseau Adr. passerelle   Adr. interface Métrique
          0.0.0.0          0.0.0.0    192.168.0.254      192.168.0.3     20
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1 255.255.255.255         On-link         127.0.0.1    306
127.255.255.255 255.255.255.255         On-link         127.0.0.1    306
      169.254.0.0      255.255.0.0         On-link       192.168.0.3     30
169.254.255.255 255.255.255.255         On-link       192.168.0.3    276
      192.168.0.0    255.255.255.0         On-link       192.168.0.3    276
      192.168.0.3 255.255.255.255         On-link       192.168.0.3    276
    192.168.0.255 255.255.255.255         On-link       192.168.0.3    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link       192.168.0.3    276
255.255.255.255 255.255.255.255         On-link         127.0.0.1    306
255.255.255.255 255.255.255.255         On-link       192.168.0.3    276
===========================================================================
Itinéraires persistants :
Aucun
IPv6 Table de routage
===========================================================================
Itinéraires actifs :
If Metric Network Destination      Gateway
14     58 ::/0                     On-link
1    306 ::1/128                  On-link
14     58 2001::/32                On-link
14    306 2001:0:9d38:90d7:3056:35ba:3f57:fffc/128
                                    On-link
14    306 fe80::/64                On-link
14    306 fe80::3056:35ba:3f57:fffc/128
                                    On-link
1    306 ff00::/8                 On-link
14    306 ff00::/8                 On-link
===========================================================================
Itinéraires persistants :
Aucun
D:\Users\admin>ping 127.0.0.1
Envoi d'une requête 'Ping' 127.0.0.1 avec 32 octets de données :
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Statistiques Ping pour 127.0.0.1:
    Paquets : envoyés = 4, reçus = 0, perdus = 4 (perte 100%),
D:\Users\admin>ping 192.168.0.3
Envoi d'une requête 'Ping' 192.168.0.3 avec 32 octets de données :
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Statistiques Ping pour 192.168.0.3:
    Paquets : envoyés = 4, reçus = 0, perdus = 4 (perte 100%),
D:\Users\admin>ping google.com
Envoi d'une requête 'ping' sur google.com [173.194.40.133] avec 32 octets de données :
Réponse de 173.194.40.133 : octets=32 temps=39 ms TTL=49
Réponse de 173.194.40.133 : octets=32 temps=38 ms TTL=49
Réponse de 173.194.40.133 : octets=32 temps=38 ms TTL=49
Réponse de 173.194.40.133 : octets=32 temps=37 ms TTL=49
Statistiques Ping pour 173.194.40.133:
    Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
    Minimum = 37ms, Maximum = 39ms, Moyenne = 38ms
The tests I made seem to indicate that the local IPv4 services (I mean applications that do a listen) are not functional.
Even if I could live with this anomaly, or if I can restore a backup to fix it, I would really like to understand how this is possible and how to fix it properly.
Philippe

Hi,
Ping localhost is a loopback process to verify the TCP/IP is configured correctly on the local computer. So, the TCP/IP configuration or stack contains a corruption, first, I would suggest you check you check you TCP/IP settings, reset the
TCP/IP stack by using NetShell
http://support.microsoft.com/kb/299357
Since the Ping is timeout via ipv4 but Ok via Ipv6, so it's also recommended to just reset the ipv4 setting via the following command and check the result
netsh interface ipv4 reset
Yolanda Zhu
TechNet Community Support

Problem with ping

I am using isReachable method of InetAddress class for checking if the host is alive or not. This method returns false. But if i invoke ping using Runtime class I get response from that host ....also if i try to do ping from command line even then I get reply for this host? Why isReachable is returning false??? Any ideas?? that host is not behind any firewall......pls help...

So presumably the ping command doesn't do the same thing as what the isReachable method does. The documentation says what isReachable does, so now you have to compare that to what ping does.

Flood ping of loopback device gives 20% packet loss!

While trying to diagnose a problem with my Airport Express (high packet loss even with a strong signal), I noticed that my Macbook cannot reliably flood ping its own loopback device!
bash-3.2$ $ sudo ping -f 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
....^C
--- 127.0.0.1 ping statistics ---
994 packets transmitted, 750 packets received, 24% packet loss
round-trip min/avg/max/stddev = 0.012/0.017/0.103/0.007 ms
As the loopback interface is internal, I get precisely the same result whether Airport is turned on or off.
This seems completely crazy to me! Anyone have any idea what might be going on?
Message was edited by: zzz Matt Taylor (replaced ping output with one with linebreaks to avoid excessively wide post)

Can't help you specifically with that, but just last night my Atheros AR5008 adapter starting dropping 40%-80% of the packets to my router. It's unusably slow now. I had this problem with the 2.6.38 kernel and was able to solve it by passing the nohwcrypt option to the ath9k module, but that doesn't work anymore.
I'm now on the 3.0.4 kernel, Arch x64. Last updates that MAY be relevant were dbus-sharp, dbus-sharp-glib, and gnutls. I started having problems the day after upgrading these packages. I'm connecting in 802.11n mode.
I've been looking for evidence of related bugs but so far nothing. I wonder if this is a broader issue affecting more than just the Atheros or Ralink drivers?
EDIT: downgrading gnutls from 3.0.3-1 to 3.0.2-1 reduced my packet loss to about 15%, so the internet is now basically usable. I also tried downgrading glib-networking (which I updated to version 2.28.7-5 a few days back), but that didn't seem to help.
Last edited by rsking84 (2011-09-22 01:32:59)

SIP Options Ping

Cisco CME to Cisco UBE Options ping no-worky....
Did anyone get SIP options pings working on a pure Cisco router (UBE to UBE and UBE to CME) environment? I have a pure Cisco 15.1 network that we are playing with option pings on. I see pings go out and 200 OK responses, but dial-peers are still busying out. Have tried both default and example settings from Cisco UBE deployment guides. Routers are working with options pings from external ITSPs, so know options replies are working and are supported. So, what's the magic sauce on Cisco IOS 15.1 for SIP options-keepalive?
dial-peer voice 40221 voip
corlist outgoing peer-internal
description \\\ 4385 - 4389 \\\
translation-profile outgoing ToCUCME_NANP_PrefixedE164
preference 1
destination-pattern 438[5-9]
session protocol sipv2
session target ipv4:10.5.5.1
voice-class sip early-offer forced
voice-class sip options-keepalive up-interval 12 down-interval 65 retry 3
dtmf-relay rtp-nte
fax-relay ecm disable
no fax-relay sg3-to-g3
fax rate 14400
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-throug
no vad

There are no firewalls or NAT between and when using "debug ccsip message" we see option sent and received and replies on both sides.

Portfast case ping transmit failed general failure

Hi
today i add a host in a vlan, but it can't ping itself and get ping transmit failed general failure unless remove the spaning portfast command. i try difeerent vendor PC, IBX... ,HX..,DXl..., all host can't ping itself.
the reason is the portfast? but portfast isn't only fotr host pc,
the following is same our command about spaning.sorry for i can't past all command because our com private.
errdisable recovery cause udld
errdisable recovery cause bpduguard
errdisable recovery cause security-violation
errdisable recovery cause channel-misconfig
errdisable recovery cause pagp-flap
errdisable recovery cause dtp-flap
errdisable recovery cause link-flap
errdisable recovery cause gbic-invalid
errdisable recovery cause l2ptguard
errdisable recovery cause psecure-violation
errdisable recovery cause dhcp-rate-limit
errdisable recovery cause unicast-flood
errdisable recovery cause vmps
errdisable recovery cause storm-control
errdisable recovery cause arp-inspection
errdisable recovery interval 30
power redundancy-mode redundant
no file verify auto
spanning-tree mode pvst
spanning-tree loopguard default
spanning-tree portfast bpduguard default
spanning-tree extend system-id

what do you see under "show interface status" of the switch when the issue occurs?
do you see input/output rate on that interface when the issue occurs?
what is the spanning-tree state of that port?
when you say you get "ping transmit failed", are you getting that error when you try to ping the PC's IP address from the PC?
are you able to ping 127.0.0.1?
and, what does the PC's network connection say?

Ping doesn't work as root

I did a fresh install today, and spent several hours trying to figure out why dns wasn't working.
It turned out that it was just that ping was broken. No other programs seems to have any trouble resolving host names.
# ping google.com
ping: unknown host google.com
# ping localhost
ping: unknown host localhost
# ping 127.0.0.1
(replies)
On the other hand, if i log in as a user, everything works perfectly. It seems to be just the ping utility when I am logged in as root.
What can be the cause of this?
I've copied /etc/hosts and /etc/nsswitch.conf from another arch machine where everything is working.
EDIT: I'm using dhcpcd, btw.
Last edited by bobbaluba (2013-08-06 03:38:48)

I have the same problem (after the last update). As user also has stopped working.
If your network uses the domain, try ping with domain suffix (etc. ping machinename.domainname).
I temporally added to the "/etc/resolvconf.conf" and after run "resolvconf -u"
search_domains=my_domain_name.local
PS: I'll wait for the normal solution of the problem.

Ping: cannot resolve localhost: Unknown host

Anybody have an idea on how to resolve this issue???? It just happened in the last week and I apparently cannot connect to a certain program....

Ok try this on the terminal:
sudo nano /private/etc/hosts
You will need your password to see the host table.
Mine looks like this .. as you see localhost points to the ping address that you used and worked. You may be missing that and therefore "ping localhost" fails why "ping 127.0.0.1" works:
# Host Database
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1             localhost
fe80::1%lo0     localhost

Extremely high ping times only fixed via restart

I have 2 BR350 in bridge to a remote tower that has an AP350 providing access to customers. The customers will call in with complaints of very slow access. I have been onsite to see that a user can login to the AP350(web) fine but the BR350 at the tower is slow and the BR350 at the far tower is for most purposes dead. The link still shows up around 65% to 75% signal strength. By restarting either BR350 the link will come back fine. I have been using Ping Plotter to keep track of the ping times and see that the response times sometime slow grow or instantly grow to around 2000ms to 4000ms. Ping times from the customer to the AP350 on the tower remain below 10ms during all of this.
I have had a similar problem with an AP350 in another city thats ping time do the same thing and require a reboot. It's ping time from the client side can range form 4ms to 800ms on regular usage as well. This customer has an average of 80% signal strength from the Workgroup Bridge.
How can I find out what is causing that strange high ping time on these situations.
All units running firmware 12.00
Thanks for the help.
MV

Normally ,the first thing to do is to check the software version used. Here,in your case you are using the latest software release(12.00T). So now the problem can be isolated to other issues. Bridge software provides tools to show you the types of problems and where the bridge is encountering the problems. Two of the most helpful tools are the Throughput statistics and the Error statistics screen.You can get the procedure for collecting the error statistics using the following URLs:
http://www.cisco.com/warp/public/102/wlan/br-ts-22950.shtml#conn
http://www.cisco.com/warp/public/102/wlan/errors.html

Cannot ping the gateway

Hi
Network:
One firewall where the IP address is the gateway for all the internal computers and server
From one if the internal computers I can ping the the gateway
From the server I can ping all the internal computers but I cannot ping the gateway
On the server I can ping:
- 127.0.0.1,
- the IP address on the server
- All the internal computers
A hint would be nice
Best Regards
John B

Arp -a
Interface: 10.0.0.2 on Interface 0x1000003
Internet Address      Physical Address      Type
10.0.0.1              10-7b-ef-3a-58-09     dynamic
10.0.0.26             00-01-e6-b4-e1-fe     dynamic
Ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : krogh01
Primary DNS Suffix . . . . . . . : Krogh.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Krogh.local
Ethernet adapter Inside:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7760 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-0B-CD-1C-7C-D9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.2
                                     212.242.40.3
                                     212.242.40.51
Ping 10.0.0.1
Pinging 10.0.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.0.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ping 10.0.0.26
Pinging 10.0.0.26 with 32 bytes of data:
Reply from 10.0.0.26: bytes=32 time=1ms TTL=64
Reply from 10.0.0.26: bytes=32 time<10ms TTL=64
Reply from 10.0.0.26: bytes=32 time<10ms TTL=64
Reply from 10.0.0.26: bytes=32 time<10ms TTL=64
Ping statistics for 10.0.0.26:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
I can ping every computer on internal network without any problems, it is only the gateway I have problem with.
I have now made a ping session from a computer on the internal network:
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.
C:\Users\lh>ipconfig /all
Windows IP-konfiguration
   Værtsnavn. . . . . . . . . . . . . . . . . . : NUC-lone
   Primært DNS-suffiks. . . . . . . . . . . . . : Krogh.local
   Nodetype . . . . . . . . . . . . . . . . . . : Hybrid
   IP-routing aktiveret . . . . . . . . . . . . : Nej
   WINS-proxy aktiveret . . . . . . . . . . . . : Nej
   Søgeliste for DNS-suffiks. . . . . . . . . . : Krogh.local
Ethernet-netværkskort LAN-forbindelse:
   Forbindelsesspecifikt DNS-suffiks. . . . . . :
   Beskrivelse. . . . . . . . . . . . . . . . . : Intel(R) Ethernet Connection I
218-V
   Fysisk adresse . . . . . . . . . . . . . . . : C0-3F-D5-61-7A-3A
   DHCP aktiveret . . . . . . . . . . . . . . . : Ja
   Automatisk konfiguration aktiveret . . . . . : Ja
   Link-local-IPv6-adresse . . . . . : fe80::5c7a:dcbe:f8:7de7%11(Foretrukken)
   IPv4-adresse . . . . . . . . . . . . . . . . : 10.0.0.113(Foretrukken)
   Undernetmaske. . . . . . . . . . . . . . . . : 255.255.255.0
   Rettigheden opnået . . . . . . . . . . . . . : 12. december 2014 03:15:59
   Rettigheden udløber. . . . . . . . . . . . . : 19. december 2014 08:05:30
   Standardgateway. . . . . . . . . . . . . . . : 10.0.0.1
   DHCP-server. . . . . . . . . . . . . . . . . : 10.0.0.1
   DHCPv6 IAID . . . . . . . . . . . : 247480277
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-40-6D-C9-C0-3F-D5-61-7A-3A
   DNS-servere. . . . . . . . . . . . . . . . . : 10.0.0.2
212.242.40.3
212.242.40.51
   NetBIOS over Tcpip . . . . . . . . . . . . . : Aktiveret
Tunnel-netværkskort isatap.{B46FAFD6-A60A-48D9-967D-4081FAE7F6AE}:
   Medietilstand. . . . . . . . . . . . . . . . : Mediet afbrudt
   Forbindelsesspecifikt DNS-suffiks. . . . . . :
   Beskrivelse. . . . . . . . . . . . . . . . . : Microsoft ISATAP-netværkskort
   Fysisk adresse . . . . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiveret . . . . . . . . . . . . . . . : Nej
   Automatisk konfiguration aktiveret . . . . . : Ja
Tunnel-netværkskort Teredo Tunneling Pseudo-Interface:
   Medietilstand. . . . . . . . . . . . . . . . : Mediet afbrudt
   Forbindelsesspecifikt DNS-suffiks. . . . . . :
   Beskrivelse. . . . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interf
ace
   Fysisk adresse . . . . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiveret . . . . . . . . . . . . . . . : Nej
   Automatisk konfiguration aktiveret . . . . . : Ja
C:\Users\lh>ping 10.0.0.1
Pinger 10.0.0.1 med 32 byte data:
Svar fra 10.0.0.1: byte=32 tid=1ms TTL=64
Svar fra 10.0.0.1: byte=32 tid=1ms TTL=64
Svar fra 10.0.0.1: byte=32 tid=1ms TTL=64
Svar fra 10.0.0.1: byte=32 tid=1ms TTL=64
Ping-statistikker for 10.0.0.1:
    Pakker: Sendt = 4, modtaget = 4, tabt = 0 (0% tab),
Beregnet tid for rundtur i millisekunder:
    Minimum = 1ms, Maksimum = 1ms, Gennemsnitlig = 1ms
C:\Users\lh>
A hint would be nice :-)
Best Regards
John B

Webpages stop loading, can still ping

Hi,
I had BT Infinity installed on Thursday and attain speeds of around 55mb down and 14mb up during the daytime, dropping to around 30mb down and 10mb up during evenings and overnight (congestion? contention?)
All is fine apart from the fact that after a few hours, I can't connect to webpages at all. I can ping the servers and the ping times are < 20ms, but the pages themselves will either not load at all, will partly display after several minutes (e.g. the text but no stylesheets or images) or the browser will just time out.
It seems that when this happens, the only cure is to reboot the Openreach modem. I tried waiting to see if pages would start working again but after 2 hours I gave up. Rebooting the Home Hub makes no difference, it has to be the Openreach modem that is rebooted at which point the webpages load blazingly fast again. I've had to do this several times already and I'm worried about the long term effect it will have on my IP Profile (which is currently 57.3 down and 20.0 up). When the pages aren't working it's impossible to conduct a speed test.
Is it normal for this to happen during the 10 day training period? I know it says that the internet can go down during this training period, but I assumed that it referred to DLM resyncing. At no time does the router lose sync (and pings are still successful with < 20ms response times) so the actual connection seems OK. Could it be a faulty modem? This affects all computers whether connected via ethernet or wireless.
What should I do? Thanks.

That sounds like a strange issue indeed, although if you can ping websites but just not access them via a browser it may indicate a DNS problem? Have you tried browsing by IP address as opposed to URL, or have you tried any other DNS servers on the off-chance that this fixes the problem?
Dean
BTCare Community Mod
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Weird ping thing

Netware 6.5 sp7, TCP 6.81.06, WSPIP 6.23.06, and BX2.lan version 3.41
(although b57 and c1000 do the same thing)
I can communicate just fine with everything.
However, when I ping the network identifier address of the server network
(i.e server address is 192.168.4.1, and I ping 192.168.4.0), I will get
anywhere from 3 to 30 simultaneous responses.
My MS servers, Cisco routers and switches and ASA, and my workstations do
not do this. Only my netware servers. Linux do not do it either.
Just curious if there is something to this that I don't know.
Tom

I thought the broadcast address was on the other end, ie 192.168.4.255?
Tom
>>> Haitch<[email protected]> 10/4/2008 10:30 AM >>>
Tom,
> However, when I ping the network identifier address of the server network
> (i.e server address is 192.168.4.1, and I ping 192.168.4.0), I will get
> anywhere from 3 to 30 simultaneous responses.
You're pinging the subnet broadcast address and every device on that
subnet will potentially respond - resulting in the the 3 - 30 replies.
Your other ping implementations just report the success/failure response
of the ping - netware responds with all the responses.
H.

Ping a wired Mac to stop Airport dropout

All my wireless Macs at home are experiencing the horrid intermittent Airport dropouts that seem to be caused by a recent Apple update.
I've found that pinging a wired computer on the network magically restores the Airport connection on the wireless ones... for a little while.
The only reliable way I've been able to keep the connection active is:
1. open two terminal windows and in one type ping -i 2 nameofwiredmachine.local. This will ping that computer every two seconds.
2. In the second window type ping -i 3 nameofwiredmachine.local. Wait until a half-second or so after the first window responds with a successful ping before hitting enter.
Between these two windows, you should be able to keep your connection active as long as your Airport card deigns to acknowledge that there is, in fact, a signal being received.
If your Airport card goes into signal denial, then you're stuck waiting until it comes back. Note that one window does not reliably keep your connection active. The dropout will frequently happen in-between pings and stall a single ping process.
Every once in a while, a stall will happen while both ping windows are waiting for a response. In that case, you can focus on one of the ping windows, type ctrl-c, then hit the up key and press enter. That ping process will kick-start the other one.
your pal,
- kevin

Turn on the wireless card in the older Mac if it has one. However, it should not make any difference on a local network. You should be able to communicate even though one is wireless. So, I would look at your Sharing setup.

PING 127.0.0.1 - no response !

Similar Messages

Maybe you are looking for