[X] My Assistant

[Tesheiner]

Another idea, not to solve but at least to isolate the problem.

Do you have a dynamic IP address? In such a case, have a look at it when you have connection and when you haven't. I'm wondering if it could be something related to blocked addresses or routing issues.

[djellison]

There are 5 blocked IP addresses currently, for people, how shall we put this, 'unwilling to participate in an mature and acceptable manor'

They are ( with the end two numbers removed for privacy )

24.88.something
69.141.something
61.11.something
61.17.something
65.121.something

If they coincide with anyone who's having trouble - I'll unblock and see what happens.

Doug

[Guest_Analyst_*]

I have the same problems: It works at work, it doesn't at home. I have no idea what to do.

Analyst

[DFinfrock]

Same problem here. I read UMSF at work while eating dinner each evening. At home, on AOL, I have no luck signing on. It hasn't always been this way. When I first discovered UMSF last September I would read from home, and bookmarked it as one of my "favorites". But now I have virtually given up trying to get home access. But after reading this thread I tried again yesterday, and this morning and could not sign on from home.

David

[Bjorn Jonsson]

I would be very interested in seeing a 'tracert' from those who cannot access UMSF from home (like me). For those who don't know what I'm talking about, in Windows simply open a Command Prompt (aka 'DOS Prompt') and type the following:

tracert www.unmannedspaceflight.com

Then post the result here (and needless to say, do this from a machine that cannot access UMSF).

You should get something that looks like what I posted in http://www.unmannedspaceflight.com/index.p...opic=2170&st=28

If it ends as my tracert (at gig0-1.l3-atl-5.gnax.net [209.51.131.94]) it might be time for Doug to complain to the company hosting UMSF because in that case it looks (to me at least) that someone is (probably inadvertently) preventing some specific traffic from reaching UMSF.

[djellison]

tracert's people - tracert - then I can submit them to the hosting firm - lets find a common trouble-'node' and figure it out

Doug

[Guest_Analyst_*]

I will do, now I know what you're talkig about "tracert". But it's friday, I won't be at work before monday. Doug please post an e-mail adress or send me a PM with the adress. I will send you the "tracert" from home. I can't otherwise, it's the nature of this problem.

Analyst

[djellison]

I will do, now I know what you're talkig about "tracert". But it's friday, I won't be at work before monday. Doug please post an e-mail adress or send me a PM with the adress. I will send you the "tracert" from home. I can't otherwise, it's the nature of this problem.

Analyst

Yup - please do - doug@rlproject.com


D

[Guest_Analyst_*]

Any news? I have sent you a tracert, Doug.

[djellison]

There's a common node that's causing trouble, but no news yet.

Doug

[DFinfrock]

I would be very interested in seeing a 'tracert' from those who cannot access UMSF from home (like me).

Here's what I found on my tracert:

Tracing route to unmannedspaceflight.com [72.9.234.170] over a maximum of 30 hops:

1 * * * Request timed out.
2 48 ms 47 ms 47 ms iptfarma-rtc-ve3.proxy.aol.com [152.163.104.30]
3 48 ms 48 ms 82 ms wc2-rtc-ae0.router.aol.com [172.30.81.12]
4 48 ms 48 ms 48 ms dar2-rtc-ge-4-0-0.net.aol.com [172.31.9.65]
5 49 ms 48 ms 48 ms pop2-vie-P2-0.atdn.net [66.185.145.9]
6 49 ms 49 ms 48 ms bb2-vie-P1-0.atdn.net [66.185.139.130]
7 48 ms 48 ms 48 ms pop1-vie-P1-0.atdn.net [66.185.139.83]
8 139 ms 53 ms 48 ms Level3.atdn.net [66.185.139.86]
9 49 ms 49 ms 49 ms ae-2-52.bbr2.Washington1.Level3.net [4.68.121.33]
10 61 ms 62 ms 61 ms as-2-0.bbr1.Atlanta1.Level3.net [64.159.1.1]
11 62 ms 62 ms 61 ms ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
12 61 ms 62 ms 61 ms 4.78.210.6
13 67 ms 80 ms 79 ms 209.51.149,101
14 62 ms 62 ms 62 ms 13-atl-5.gnax.net [209.51.131.98]
15 62 ms 62 ms 62 ms star.dnsprotect.com [72.9.234.170]

Trace complete.

That note about "Request timed out" certainly doesn't look good. But I will leave it to the computer experts to decipher the problem.

David

[Bjorn Jonsson]

Hmmm... this looks like a trace from a computer that can access UMSF.

There's a common node that's causing trouble, but no news yet.

Doug

Any news yet ? I still cannot access UMSF from home.

[djellison]

Nothing - they've said they're investigating it, but because the vast majority are having no trouble at all, they're working hypothesis is that it isnt their end, it's elsewhere.

Doug

[djellison]

I've submitted 3 more tracert's to the host. Flicking between my internet connection and a neigbours internet connection ( Plunet ADSL and NTL Cable ) - mine works, the neigbours doesnt. Who know how many people have just given up on the place - and the coincidence of this problem first appearing with a drop in total visit numbers for Feb is too much to leave un-attended - so I'm going to keep hacking at the hosting firm till they correct it.

Doug

[Bjorn Jonsson]

This is great news. I contacted my ISP and (as I was sure of beforehand) apparently no problem on their end. The person I spoke to even was able to access UMSF. Even though this doesn't prove anything I am sure the problem is not with my ISP. UMSF is the only website I have had problems accessing from home and I visit lots of websites regularly. Also I am not the only one having this problem.

BTW this problem has persisted for over a month now. For the first 10 days or so there were intermittent brief periods when I was able to access UMSF from home but this problem has been continuous from roughly February 10.