It might not seem like much, but the Muni Wifi latencies are *significantly* higher than the Comcast set - approximately 3-5 times as high per hop. That's not good.
Kurt On Tue, Nov 18, 2008 at 9:02 PM, Sam Cayze <[EMAIL PROTECTED]> wrote: > Thanks for chiming in, > Well, I can browse to the other servers behind the same router/firewall > just fine, and download files from them fast. > > Also, I can download a 12 MB file from the HTTP of server from Muni at > 200Kbps, and Comcast at 500Kbps. Not much of a difference.. > > Muni Wifi > 1 <1 ms <1 ms <1 ms 192.168.1.1 > 2 35 ms 30 ms 39 ms 67.220.14.129 > 3 36 ms 26 ms 40 ms 206.55.180.131 > 4 23 ms 28 ms 27 ms 206.55.180.35 > 5 30 ms 24 ms 28 ms 206.55.180.17 > 6 48 ms 26 ms 37 ms 65.46.169.45 > 7 41 ms 25 ms 35 ms 65.46.168.82 > 8 34 ms 22 ms 44 ms 216.183.114.12 > 9 * * * Request timed out. > 10 * * * Request timed out. > 11 * * * Request timed out. > > Comcast > 1 8 ms 6 ms 7 ms 73.236.168.1 > 2 6 ms 7 ms 8 ms ge-9-1-ur01.swmpls.mn.minn.comcast.net > [68.85.165.65] > 3 14 ms 9 ms 11 ms te-8-1-ur02.smpls.mn.minn.comcast.net > [68.86.232.110] > 4 7 ms 7 ms 10 ms te-2-1-ur01.smpls.mn.minn.comcast.net > [68.86.232.113] > 5 7 ms 7 ms 8 ms > te-9-1-ar02.roseville.mn.minn.comcast.net [68.86.232.122] > 6 16 ms 18 ms 17 ms > te-0-2-0-5-cr01.chicago.il.ibone.comcast.net [68.86.91.141] > 7 17 ms 17 ms 17 ms xe-10-3-0.edge1.Chicago2.Level3.net > [4.71.248.9] > 8 18 ms 16 ms 17 ms vlan51.ebr1.Chicago2.Level3.net > [4.69.138.158] > 9 22 ms 17 ms 17 ms ae-6.ebr1.Chicago1.Level3.net > [4.69.140.189] > 10 19 ms 19 ms 19 ms ae-13-51.car3.Chicago1.Level3.net > [4.68.101.7] > 11 17 ms 17 ms 17 ms XO-COMMUNIC.car3.Chicago1.Level3.net > [4.71.100.46] > 12 17 ms 20 ms 21 ms 65.106.1.90.ptr.us.xo.net [65.106.1.90] > 13 19 ms 17 ms 19 ms 65.106.1.89.ptr.us.xo.net [65.106.1.89] > 14 28 ms 26 ms 27 ms 71.5.171.30.ptr.us.xo.net [71.5.171.30] > 15 27 ms 27 ms 27 ms 64.1.4.70.ptr.us.xo.net [64.1.4.70] > 16 29 ms 30 ms 27 ms > ip65-46-168-82.z168-46-65.customer.algx.net [65.46.168.82] > 17 27 ms 27 ms 26 ms minir2-vl-1.sgns.net [216.183.114.12] > 18 * * * Request timed out. > 19 * * * Request timed out. > > > > > -----Original Message----- > From: Kurt Buff [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 18, 2008 12:06 AM > To: MS-Exchange Admin Issues > Subject: Re: RPC / Outlook Anywhere Slow.... And fast! > > Do a traceroute from your box to the Exchange server. I bet you'll find > that there's a router or three in there with really bad latency... > > On Mon, Nov 17, 2008 at 9:58 PM, Sam Cayze <[EMAIL PROTECTED]> > wrote: >> Terrible wait time for Outlook Anywhere on one of my ISPs... Curious > why. >> >> 3 ISPs right now: >> >> 1 Comcast 8Mbps (Speedtest.net = 16 Mbps) >> 2 Muni Wfi 6Mbps (Speedtest.net = 9 Mbps) >> 3 Sprint EVDO Rev. A (Work laptop) (Speedtest.net = <1 Mbps) >> >> Exchange box is hosted on a 10 Mbps uplink. >> Tested with XP, Vista, Outlook 2003, 2007, all Cached Mode. >> >> When I am on my Comcast or Sprint connection, and I open up Outlook, I > >> am instantly greeted with the password dialog box, and I can connect >> to the server instantly upon entering my password. Perfect. >> >> If I switch to the Muni Wifi connection, Outlook hangs, and I have to >> wait over 60 seconds for the password dialog box to appear. Once I >> finally connect, Outlook is sluggish at first... then normal. It >> doesn't seem like a speed issue, because the Muni is MUCH faster than >> the EVDO connection, and I don't have this issue on the EVDO >> connection at all... Even using the EVDO card on roam at my cabin I > don't see this issue. >> >> I'm not much of a networking guru, so I am not sure where to start >> looking... Did my due diligence and looked at some KB articles, >> results below. >> >> I am a Beta tester on the MuniWiFi, so I have a little closer access >> to their advanced support staff, so I want to take the time and > research this. >> Some of our emloyees might end up using this MuniWiFi, and I am >> debating if I should keep it and ditch Comca$t. >> >> >> >> RPCPing results: >> Comcast: >> RPCPinging proxy server mail.rollouts.com with Echo Request Packet >> Sending ping to server Response from server received: 200 Pinging >> successfully completed in 530 ms >> >> MuniWifi: >> RPCPinging proxy server mail.rollouts.com with Echo Request Packet >> Sending ping to server Response from server received: 200 Pinging >> successfully completed in 499 ms >> >> Any pointers would be great! Thanks, >> >> Sam >> >> >> >> Sam Cayze >> Information Technology Administrator >> ROLLOUTS >> ONSITE * ON DEMAND >> 952.279.6218...Direct Dial >> 612.386.3946...Mobile >> www.Rollouts.com >> www.e-Technicians.net >> >> CONFIDENTIALITY NOTICE: This email and any attachment(s) are intended > only >> for the designated recipient(s). Rollouts Incorporated prohibits > use, >> distribution or transmittal by or to an unintended recipient without >> Rollouts' express written approval. If you are not the intended >> recipient, please delete this email and notify Rollouts. >> >> > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~ http://www.sunbeltsoftware.com/Ninja ~ > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~ http://www.sunbeltsoftware.com/Ninja ~ > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
