
|
View Full Version : Can ONE single user encounter download difficulties with ONE site only?
Our site (www.vendelcommunications.com) is hosted by Yahoo. Previously, we had no problems to download/view the site ourselves. About a week ago, it became virtually impossible. All of a sudden, it took forever, or stalled completely.
We're having no problems what so ever with any other site.
At the same time, our e-mail accounts with Yahoo (POP and SMTP) became unstable. We've set our client side e-mail apps to connect to the server every 3 minutes, and about every 10 times, the app can not connect at all. This never happened before.
First, I approached Yahoo and told them something was wrong with their stuff. They claimed not.
Then, I mailed our ISP. They said they couldn't find anything wrong in their equipment.
Then, I pinged and traced the site. The pings didn't come back. The trace showed that it stalled near Yahoo somewhere (unknown.Level3.net 209.245.56.18).
I have had friends with other ISP:s open the site, and they say it's coming down nicely and not slower than any other site....
Questions: Is it possible that ONLY WE can have problems with ONE SITE (ours) only? How often will a route stay the same (I thought it changed about every time I connected to a site)?
Can someone enlighten this ingoramus?
Thanks
Ask someone to traceroute your home IP, or ping you.
certify 09-13-2001, 08:47 AM Your site is working over at my end.
Well, the catch is that I'm in Sweden, and the host is in US, so I assume that a ping and/or tracer wouldn't say very much?
If someone reading this, sitting in US right now and has a few minutes to spare, pls ping and trace me. My IP is 217.215.23.26
But I (with very limited knowledge about this...) doubt it'll clear up the matter.
BTW: To show the guys at Yahoo, I took screen snaps of both ping and tracer results. Since they don't accept attachments to e-mails, I had to post the results at my site for them to view.
If it can help someone to diagnose, go to http://www.vendelcommunications.com/yahoo/index.html
BTW 2: Due this mess, I'm looking for a new host. Must have a lot of pre-installed scripts for e.g. passwords, chat, message board, mail, etc. Suggestions welcome...
Dan
spock 09-13-2001, 10:13 AM I live in Sweden too, and have no problems accessing your site. There have been a lot of problems like this from Telia clients recently, and it does indeed look like you are using their services. I suspect there are some glitches with the (recently upgraded?) transatlantic connectivity from Telia's network, but I haven't tried to verify that.
Hej du,
Good to know that SOMEONE can view the site without problems. I just had a meeting with a prospective client at their office, and they sat down to check out my site while I was there. Of course it didn't f----g download!!!! Very embarassing....
No, my ISP is BoNet, not Telia. I used to have them (with ISDN) until 3months ago, when I became fed up with their non-existing service.
And of you check out the tracer result, you'll see that the routes through Telia is not the problem (I think...?).
spock 09-13-2001, 10:44 AM Well, from your traceroute it's obvious the traffic goes over Telias transatlantic line, and I still suspect there's where the problem lies. Pinging your IP from a host in Canada shows reasonable round-trip times but 30-50% packet loss. Here's a traceroute from Yahoo:
traceroute to 217.215.23.26 (217.215.23.26), 30 hops max, 40 byte packets
1 v998-snv-io-rtr1.corp.yahoo.com (216.145.48.2) 0.251 ms 0.200 ms 0.176 ms
2 ge-0-2-0.pat1.pao.yahoo.com (216.115.100.97) 1.719 ms 1.518 ms 1.538 ms
3 gigabitethernet2-1.ipcolo1.SanJose1.Level3.net (63.209.0.225) 2.360 ms 2.372 ms 2.358 ms
4 ae0-52.mp2.SanJose1.level3.net (64.159.2.33) 2.788 ms 2.912 ms 2.660 ms
5 so-2-0-0.mp1.NewYork1.level3.net (64.159.0.234) 99.230 ms 99.142 ms 99.245 ms
6 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 99.320 ms 99.268 ms 99.161 ms
7 unknown.Level3.net (209.244.160.178) 99.590 ms 99.327 ms 99.727 ms
8 kbn-bb2-pos1-0-0.telia.net (213.248.64.14) 181.822 ms 181.937 ms 183.309 ms
9 s-bb2-pos0-1-0.telia.net (213.248.64.42) 192.341 ms 192.342 ms 192.006 ms
10 s-b3-pos4-0.telia.net (213.248.66.10) 191.468 ms 191.406 ms 191.417 ms
11 fre-b1-pos10-0.telia.net (213.248.66.22) 191.694 ms 194.727 ms 191.695 ms
12 213.64.62.122 (213.64.62.122) 199.163 ms 199.171 ms 199.570 ms
13 g-br-d2-geth3-0.se.telia.net (213.64.49.90) 199.151 ms 199.268 ms 200.411 ms
14 bonet-gbg.k.telia.net (194.236.189.226) 200.014 ms 199.819 ms 199.741 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Thanks all for looking into this. I really, really appreciate your efforts!
Spock: I have to go for ärtsoppa. Will be back later tonight. can you e-mail me at vendel@vendelcommunications.com to exchange phone numbers? If you don't want that, I understand.
D
regier 09-13-2001, 06:38 PM I would almost guarantee that you have a personal firewall installed on your computer. Please correct me if I am wrong though.
Disable it for now and try your site and I'm sure it will work. You can then start it again and modify it not to block your site.
Sometimes when uploading with ftp, an ftp server can send a response that some firewalls don't like. They then block you from accessing your site.
Regier:
Thanks for suggestion.
Yes, I'm behind a firewall. But one of the first things I did, was to disable that since I had the same theory as you. But the site was as impossible as before. Further on, it has never been any problems previously. The last time I uploaded new files was about a month ago. After that, no problems at all. It all started all of a sudden last week.
A client of mine also tried to view it yesterday; same difficulties. Whereas another friend I asked to check didn't have any problems at all.
I think the suggestion from "Spock" is close to it.
However, I just tried to view the site again, and what do you know?! It's coming down like charm, slams into the screen within seconds as it used to do!!!! Whatever the glitch was, someone has fixed it.
All of you, thanks again for suggestions!
|