i have a wired router now and today I by-passed it and it made no difference and I shut off the mcafee and it made no difference, it seems that cable has a connection at 68.86.80.37 that is between nj and mewyork that goes to 100 on the pl% and them goes to err, they say it doesn't show up on their screen but it shows on mine and I changed the address by a couple numbers but it was still chicago and it was the same connection going bad the cable tech googled the address and it went to a forum that was about voip and they were all having trouble with it and he was trying to solve the problem from the forum he siad it was a voip forum so it wouldn't help me but it makes sense that since comcast started pushing the phone I have had troubles
I pinged that one and it work good, what are those timed out ones at 17 and 18 thats what I get when i go to the 66.150.110.86
I pinged globalfutures.com and got timed out 4 times I pinged rjofutures.com and it went thru no troubles, its a different ipo beginning on the address 198. the pingplotter says that its a problem between plianfield nj and newyork global says its comcast and comcast says its global how can I find out who is the problem? without going crazy, the dsl will take a week to set up and I want to trade in and out the rest of the week without fear of a crazy fill and having to wait for a 40 point move in the ym just to be safe
If a particular node (be it a router or an actual server) is configured to not respond to icmp packets then you arent going to get back ping or traceroute results from that nodes. Those timed out entries in the traceroute are hops that dont respond - there is nothing more you can do about those, they have made the decision not to respond to icmp.
All that means is that globalfutures.com has elected to not respond while rjofutures.com does - do not read into it anymore then that. You can't ping cisco.com either but you can bet their site is up and running just fine... To find out the source of your problem leave ping plotter up and running 24 x 7 with a fairly short delay between pings, say 15 seconds. When a glitch does occur that affects you check out where pingplotter shows the packet loss. Not sure what you plan on doing with the information, you can't choose the route your packets take and if a intermediate AT&T or level3 router is causing the problem its not like you can call them up and complain about it. You only control one (maybe two) variables - where your packets enter the internet from. Changing ISP's changes that. The only other thing you can do is change destination (by changing brokers). Everything else is out of your hands.
thats what i'm trying to figure out, do I change brokers or do I change cable to highspeed dsl, they say its up to 3.0 mbps so i'm going to try the cable verses dsl first since its easy and its a 30 day deal with a money back guarentee, i'll post if anything gets better with verizon I was hoping the cable could route it a different way
Its very likely that changing ISP's from cable to DSL will change the route since different ISP's connect to the internet backbones in different ways. You could also do traceroutes from different places on the internet (http://www.traceroute.org/#USA) to see if there is any common problem but that would only be helpful if the problem was readily reproducible which doesnt sound like its the case.
Joe, I may be off, and I know GTS knows alot more than I, so maybe he can chime in..... You are on the East Coast right? Global is in LA that I know for sure. If you use a trading application that has to connect to their server, if, you would have to all the way accross the country and then all the way back to Chicago or NY, depending on what you trade. We are talking miliseconds, but if the above scenario is correct I would suggest an East Coast broker. I like both Velocity and TransAct, both are East Coast, although Velocity does have a data center in Houston. Once again we are talking miliseconds, but it may help. I agree with GTS though, the problem is most likely an ISP issue, but having to go East to West to East does nothing to help. I ran ping plotter, easy once I took the time to read it and I came back with all good reads and under 85milliseconds, Denver to Chicago.
Right dandxg, when I traceroute to globalfutures.com using a site that lets you select different source points (ex: http://www.cogentco.com/htdocs/glass.php) I end up with these results: Looking Glass Results: Los Angeles -------------------------------------------------------------------------------- Query: trace Addr: globalfutures.com trace globalfutures.com Translating "globalfutures.com"...domain server (66.28.0.45) [OK] Tracing the route to globalfutures.com (64.80.155.66) 1 g10-0-224.core01.lax01.atlas.cogentco.com (66.250.4.5) 32 msec 16 msec 80 msec 2 p6-0.core01.lax04.atlas.cogentco.com (154.54.6.242) 4 msec 4 msec 0 msec 3 vl3805.na21.b002695-2.lax04.atlas.cogentco.com (38.20.33.194) 4 msec 4 msec 0 msec 4 PAETEC_Communications_Inc.demarc.cogentco.com (38.112.26.166) 0 msec 4 msec 0 msec 5 66.251.30.44 0 msec 0 msec 0 msec 6 64.80.120.74 8 msec 8 msec 4 msec 7 * * * Looking Glass Results: Washington, DC -------------------------------------------------------------------------------- Query: trace Addr: globalfutures.com trace globalfutures.com Translating "globalfutures.com"...domain server (66.28.0.45) [OK] Tracing the route to globalfutures.com (64.80.155.66) 1 f0-9.na01.b005944-0.dca01.atlas.cogentco.com (66.250.56.189) 0 msec 0 msec 4 msec 2 g6-0.3807.core02.dca01.atlas.cogentco.com (66.28.6.189) 0 msec 0 msec 4 msec 3 t4-3.mpd01.dca01.atlas.cogentco.com (154.54.5.57) 4 msec 0 msec 4 msec 4 t3-1.ccr01.clt01.atlas.cogentco.com (154.54.5.53) 80 msec 76 msec 76 msec 5 * t2-3.mpd01.iah01.atlas.cogentco.com (154.54.7.145) 76 msec 76 msec 6 t2-1.mpd01.lax01.atlas.cogentco.com (154.54.3.38) 268 msec 88 msec 184 msec 7 g2-0-0.core01.lax01.atlas.cogentco.com (154.54.2.101) 76 msec 80 msec 80 msec 8 p6-0.core01.lax04.atlas.cogentco.com (154.54.6.242) 80 msec 80 msec 76 msec 9 vl3805.na21.b002695-2.lax04.atlas.cogentco.com (38.20.33.194) 80 msec 80 msec 76 msec 10 PAETEC_Communications_Inc.demarc.cogentco.com (38.112.26.166) 80 msec 80 msec 80 msec 11 66.251.30.12 80 msec 80 msec 80 msec 12 64.80.120.74 84 msec 84 msec 104 msec 13 * * * 14 * * * 15 * * * 16 * * *