Well, I gave Verizon more credit than they deserved. Still having timeout problems due to their network issues. So basically hereâs what my routine looks like now:
Work on client website
Open Apple preferences and turn off Ethernet
Publish website
Turn Ethernet network back on
Upload website using Transmit (I can no longer reliably upload my files from within Freeway Pro)
If it makes you feel any better, Iâm having similar problems here. Not convinced itâs a Freeway or Action problem, though. Might be a Lion thing, might be a Google thing.
Walter
On May 24, 2012, at 2:29 PM, RavenManiac wrote:
Well, I gave Verizon more credit than they deserved. Still having timeout problems due to their network issues. So basically hereâs what my routine looks like now:
Work on client website
Open Apple preferences and turn off Ethernet
Publish website
Turn Ethernet network back on
Upload website using Transmit (I can no longer reliably upload my files from within Freeway Pro)
Come to think of it, everything seemed fine a few weeks ago BEFORE the Mac 10.7.4 update on May 7th. But then again, Iâve been wrong about this issue before. Sorry youâre having problems as well. Let me know if you find a solution.
On a side note, I wonder if constantly turning my Ethernet port on and off will damage it. I really canât afford a new MacPro right now.
Come to think of it, everything seemed fine a few weeks ago BEFORE the Mac 10.7.4 update on May 7th. But then again, Iâve been wrong about this issue before. Sorry youâre having problems as well. Let me know if you find a solution.
Itâs all working now, after they rebuilt my connection on the ISP side.
On a side note, I wonder if constantly turning my Ethernet port on and off will damage it. I really canât afford a new MacPro right now.
Thatâs just not possible. All youâre doing is toggling a software âswitchâ here, nothing physical is happening at all.
Plus, since itâs a Pro, you have two built-in ports you can use, and you have plenty of PCI-X card slots where you can put in a $10 card.
Hereâs the latest. Everything from sequence 4 and below is Verizon FIOS equipment. Nice.
Ping has startedâŚ
PING googleapis.l.google.com (173.194.75.95): 56 data bytes
64 bytes from 173.194.75.95: icmp_seq=0 ttl=48 time=26.743 ms
64 bytes from 173.194.75.95: icmp_seq=1 ttl=48 time=23.082 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 173.194.75.95: icmp_seq=5 ttl=48 time=24.368 ms
64 bytes from 173.194.75.95: icmp_seq=6 ttl=48 time=23.465 ms
64 bytes from 173.194.75.95: icmp_seq=7 ttl=48 time=24.796 ms
Request timeout for icmp_seq 8
64 bytes from 173.194.75.95: icmp_seq=9 ttl=48 time=23.160 ms
â googleapis.l.google.com ping statistics â
10 packets transmitted, 6 packets received, 40.0% packet loss
round-trip min/avg/max/stddev = 23.082/24.269/26.743/1.271 ms
I doubt itâs you. But youâre mistaking what you see here. When you ping without any arguments, it pings continuously, and each ping is given a sequence number. So what youâre seeing there is just which pings are not making it through. What you may be confusing this with is traceroute. There, you see each âhopâ on the way from your Mac to the target server, and you are correct â there you would see each layer, and beyond a certain point, youâre outside of your networks and onto theirs.
Yes, you are right. Just for fun, hereâs the trace route:
Traceroute has startedâŚ
traceroute to googleapis.l.google.com (173.194.75.95), 64 hops max, 72 byte packets
1 10.0.1.1 (10.0.1.1) 0.543 ms 0.246 ms 0.244 ms
2 l100.nrflva-vfttp-10.verizon-gni.net (72.84.93.1) 4.991 ms 4.389 ms 4.977 ms
3 p0-2-0-4.nrflva-lcr-22.verizon-gni.net (130.81.58.78) 5.248 ms 4.576 ms 4.762 ms
4 p14-0-0.nrflva-lcr-02.verizon-gni.net (130.81.151.4) 27.463 ms 11.858 ms 12.231 ms
5 p12-0-0.nrflva-lcr-01.verizon-gni.net (130.81.27.136) 12.484 ms 11.836 ms 12.479 ms
6 so-15-0-2-0.res-bb-rtr1.verizon-gni.net (130.81.29.40) 12.473 ms 12.105 ms 12.476 ms
7 0.so-2-0-1.xl3.iad8.alter.net (152.63.30.2) 12.508 ms
0.so-2-0-0.xl3.iad8.alter.net (152.63.37.117) 14.369 ms
0.so-2-0-1.xl3.iad8.alter.net (152.63.30.2) 11.851 ms
8 tengige0-4-0-0.gw7.iad8.alter.net (152.63.37.150) 17.522 ms
tengige0-6-0-0.gw7.iad8.alter.net (152.63.32.190) 24.847 ms
tengige0-6-2-0.gw7.iad8.alter.net (152.63.37.78) 14.373 ms
9 google-gw.customer.alter.net (152.179.50.62) 14.371 ms * 13.653 ms
10 72.14.238.214 (72.14.238.214) 12.437 ms 11.989 ms 12.486 ms
11 209.85.243.114 (209.85.243.114) 27.494 ms 34.560 ms 24.968 ms
12 216.239.48.183 (216.239.48.183) 69.945 ms *
216.239.48.159 (216.239.48.159) 24.084 ms
And hereâs the ping:
Ping has startedâŚ
PING googleapis.l.google.com (173.194.75.95): 56 data bytes
64 bytes from 173.194.75.95: icmp_seq=0 ttl=48 time=30.555 ms
64 bytes from 173.194.75.95: icmp_seq=1 ttl=48 time=27.356 ms
64 bytes from 173.194.75.95: icmp_seq=2 ttl=48 time=23.668 ms
64 bytes from 173.194.75.95: icmp_seq=3 ttl=48 time=25.664 ms
64 bytes from 173.194.75.95: icmp_seq=4 ttl=48 time=35.193 ms
64 bytes from 173.194.75.95: icmp_seq=5 ttl=48 time=24.004 ms
64 bytes from 173.194.75.95: icmp_seq=6 ttl=48 time=30.311 ms
64 bytes from 173.194.75.95: icmp_seq=7 ttl=48 time=27.124 ms
64 bytes from 173.194.75.95: icmp_seq=8 ttl=48 time=26.464 ms
64 bytes from 173.194.75.95: icmp_seq=9 ttl=48 time=25.521 ms
--- googleapis.l.google.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 23.668/27.586/35.193/3.343 ms