I could do these things all day long and if you don't like the results you will ask me to try something else. I am not the one having issues, nor did I come here seeking help. I have done everything above before and when I upgraded to Lion Server the mail stopped working for some odd reason. Spent hours on the phone with Apple 3rd level support, and nothing could be found wrong. The mail server just started working again the next day after no changes. I get all of the correct name resolutions and such, so I don't see what the big deal here is that everyone feels the need to probe my network? When I do what is asked and provide screen shots, I am told it is not working right, yet I am having no issues and have had no issues, so why the concern really?
You're making assumptions and, likely so, because you know you're wrong. You provided little detail and I'm willing to admit I'm wrong, if you can prove it. That's all any of us are saying. If you can prove what you're saying, then we'll accept it and will have learned something new!
You're providing incorrect information on how to troubleshoot the issue. Someone else may have issues similar to this in the future and read your posts and believe what you're saying. But it is simply not true.
Since you feel like providing incorrect information and won't back it up, I'll do the work for you.
Here's an example from my 10.7.2 machine:
man ping said:The ping utility uses the ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
ECHO_REQUEST datagrams (``pings'') have an IP and ICMP header, followed by a ``struct timeval'' and then an arbitrary number of ``pad'' bytes used to fill out the packet.
And a ping test:
Code:
mini:~ user$ ping 172.16.6.254
PING 172.16.6.254 (172.16.6.254): 56 data bytes
64 bytes from 172.16.6.254: icmp_seq=0 ttl=255 time=0.641 ms
64 bytes from 172.16.6.254: icmp_seq=1 ttl=255 time=0.410 ms
^C
--- 172.16.6.254 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.410/0.525/0.641/0.115 ms
mini:~ user$ ping 172.16.6.254:80
ping: cannot resolve 172.16.6.254:80: Unknown host
mini:~ user$ ping 172.16.6.254:443
ping: cannot resolve 172.16.6.254:443: Unknown host
This is pinging one of my local devices which has TCP 80 and 443 open. Note the error message "Unknown host". This is proving that it is trying to resolve it as a string and not connect to a port. You are using OpenDNS too. How do I know? Because reverse DNS on the IP you list in your ping stats points there.
Since my DNS provider doesn't provide extra services (actually I use OpenDNS too, have registered, and disabled this feature), such as helping you find what you're looking for when you make a typo, it simply returns "Unknown host".
Thus your statement about using ping to resolve port issues is clearly not accurate.
Last edited: