OT: FTP problems

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 51926
interpreted = N
texte = I really don't want to bother the list with a problem that has very little to do with WebDNA, but it's been going on for almost a week, and I'm beginning to get really desperate now.Last Sunday I lost ftp connection with my site and it stil isn't back.Everything else works fine... *http connection: no problems *ftp to other sites: just fine *other people seems to be able to get ftp connection with the server *The sys-op at my host can't find any problems with the server *I can't find anything wrong with my own setupSo it's almost certainly a problem with one of the routers between me in Norway and that particular part of the US network.A traceroute (with Interarchy) stops at AT&T, sometimes at 12.123.24.209, usualy at 12.123.24.213. This isn't absolute positive proof, of course, but I happen to know that AT&T were working on that part of their network, desperately trying to save it from the cisco bug just when this happened. So it seems prety obvious where the source of the problem lies. (OTOH: I got a friend in the US to try an ftp connection to my site a few days ago. She seemed to get through (at least to the point where she was asked for the password) but couldn't trace the route beyond 12.123.24.209 either.)What can I do about it???I can't contact AT&T - since I'm not a customer there myself, they won't let me anywhere near the contact info/support functions at their site. My host doesn't seem to be able to help me. My ISP - well it was hard enough to *explain* the problem in a way ther "support" staff could understand. I guess there's not much help to hope for there. I suppose if I asked my host nicely, I could do some urgent site updates done through email, but that's not an alternative in the long run. I don't want to change ISP or host. I'm quite satisfied with the company that hosts my site, and as for ISP, it seems the others we have here in Norway are even worse. Seems none of them are to blame for this problem anyway. Besides, changing the route might fix the problem now; how much guranteee do I have it doesn't come back?Eventually I decided the only thing I could do was wait. Surely AT&T would discover and fix the problems on their own sooner or later. Well, it's getting later fast now, and nothing's happened yet.Does anybody here have *any* idea what to do about it? And: isn't this exactly the kind of things that are supposed to be impossible on the internet?Frank Nordberghttp://www.musicaviva.com-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: OT: FTP problems ( Alain Russell 2003)
OT: FTP problems ( Frank Nordberg 2003)

I really don't want to bother the list with a problem that has very little to do with WebDNA, but it's been going on for almost a week, and I'm beginning to get really desperate now.Last Sunday I lost ftp connection with my site and it stil isn't back.Everything else works fine... *http connection: no problems *ftp to other sites: just fine *other people seems to be able to get ftp connection with the server *The sys-op at my host can't find any problems with the server *I can't find anything wrong with my own setupSo it's almost certainly a problem with one of the routers between me in Norway and that particular part of the US network.A traceroute (with Interarchy) stops at AT&T, sometimes at 12.123.24.209, usualy at 12.123.24.213. This isn't absolute positive proof, of course, but I happen to know that AT&T were working on that part of their network, desperately trying to save it from the cisco bug just when this happened. So it seems prety obvious where the source of the problem lies. (OTOH: I got a friend in the US to try an ftp connection to my site a few days ago. She seemed to get through (at least to the point where she was asked for the password) but couldn't trace the route beyond 12.123.24.209 either.)What can I do about it???I can't contact AT&T - since I'm not a customer there myself, they won't let me anywhere near the contact info/support functions at their site. My host doesn't seem to be able to help me. My ISP - well it was hard enough to *explain* the problem in a way ther "support" staff could understand. I guess there's not much help to hope for there. I suppose if I asked my host nicely, I could do some urgent site updates done through email, but that's not an alternative in the long run. I don't want to change ISP or host. I'm quite satisfied with the company that hosts my site, and as for ISP, it seems the others we have here in Norway are even worse. Seems none of them are to blame for this problem anyway. Besides, changing the route might fix the problem now; how much guranteee do I have it doesn't come back?Eventually I decided the only thing I could do was wait. Surely AT&T would discover and fix the problems on their own sooner or later. Well, it's getting later fast now, and nothing's happened yet.Does anybody here have *any* idea what to do about it? And: isn't this exactly the kind of things that are supposed to be impossible on the internet?Frank Nordberghttp://www.musicaviva.com-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Frank Nordberg

DOWNLOAD WEBDNA NOW!

OT: FTP problems

2003

Top Articles:

Related Readings: