forums.naturalpoint.com

Ah Window XP's internal fire wall. That could be it, but I'l be dammed if I cam remember how to get to it and check!

Any one care to help?

Thanks

UPDATE: I figured it out. It was not enabled. There goes that idea.

[ November 18, 2003, 07:45 PM: Message edited by: Jaeger ]

Hi Birch, below you will find a couple of tracerts to the urls you asked for. In both cases it stops dead at 206.58.252.67 which a whois tells me is a server belonging to Verio, Inc. I had written to Jim Richardson about this problem last week with this info, he said you guys used to do business with Verio but not anymore, and maybe they had outdated routing info for you. Don't think this means anything though, I can access all sites fine at work, and a tracert from work drops dead at 206.58.252.67 there as well.

I'm no networking genius (in fact I know next to nada about it...) but I'm convinced it has GOT to be a routing problem. Somewhere in the routes shown below, I'm thinking one of the servers is passing along some bogus info. I can get to your sites fine from work, my friends can get there from home and work, my ISP's tech rep can get there. The only noteworthy difference I can think of is going to be the route taken. I *can* tell you it is NOT a browser config problem, or any other problem on my computer. I have tried both IE 6 and Netscape 7 on my main computer with same results - and on my backup system I've tried IE 5 and Netscape 4.78 and cannot connect to your sites no matter what. I'm behind a Linksys router and ZoneAlarm, and dumped both of those to make sure they weren't causing the problem - no difference at all

I *was* able to connect on 11/4/2003, when I ordered TrackIR2. Also over the next 2 or 3 days for sure, and I believe the last time I could get in was on 11/8/2003.

If there's anything else I can do, let me know, I'm glad to help! If you like I'll run a tracert at work and post or email that, so you can look for differences.

Regards,

Lee

Tracert follows...

Tracing route to www.naturalpoint.com [66.182.52.188]
over a maximum of 30 hops:

1 18 ms 12 ms 10 ms <snip>
2 10 ms 9 ms 9 ms <snip>
3 9 ms 9 ms 10 ms <snip>
4 13 ms 12 ms 13 ms <snip>
5 15 ms 18 ms 15 ms <snip>
6 16 ms 15 ms 15 ms 66.185.132.33
7 16 ms 15 ms 16 ms 66.185.138.66
8 29 ms 27 ms 37 ms 66.185.152.50
9 29 ms 27 ms 29 ms 66.185.148.211
10 28 ms 27 ms 28 ms 66.185.140.242
11 93 ms 94 ms 93 ms 129.250.2.192
12 95 ms 94 ms 94 ms 129.250.28.90
13 94 ms 94 ms 94 ms 140.174.28.18
14 98 ms 104 ms 100 ms 216.210.208.2
15 126 ms 126 ms 128 ms 216.210.221.213
16 124 ms 124 ms 126 ms 206.58.252.67
17 * * * Request timed out.
18 * * * Request timed out.
... and so on...


Tracing route to naturalpoint.com [66.182.52.164]
over a maximum of 30 hops:

1 17 ms 9 ms 9 ms <snip>
2 10 ms 9 ms 9 ms <snip>
3 13 ms 9 ms 9 ms <snip>
4 13 ms 15 ms 13 ms <snip>
5 12 ms 14 ms 14 ms 66.185.132.33
6 19 ms 14 ms 13 ms 66.185.138.66
7 32 ms 27 ms 27 ms 66.185.152.50
8 25 ms 25 ms 26 ms 66.185.148.211
9 25 ms 26 ms 26 ms 66.185.140.242
10 94 ms 92 ms 91 ms 129.250.2.192
11 91 ms 92 ms 94 ms 129.250.28.90
12 92 ms 100 ms 94 ms 140.174.28.18
13 94 ms 94 ms 102 ms 216.210.208.2
14 124 ms 124 ms 125 ms 216.210.221.213
15 125 ms 124 ms 131 ms 206.58.252.67
16 * * * Request timed out.
17 * * * Request timed out.
... and so on...

[ November 18, 2003, 10:19 PM: Message edited by: HarryLee ]

quote:Originally posted by Jaeger:
To complicated for me. I doubt my results would be any differant then MssrSchmidt's.
Jaeger - It's NOT too complicated! And I can just about guarantee your results WILL be different than MssrSchmidt's. I've posted a tracert, and if you can too it may help find out why some of us can't access the site.

The tracert command "traces the route" that your computer follows thru the internet to get to a particular website - this route will be different for different people, in different places. I'm sure that at some point on the route I'm taking, bad data is being passed that causes me not to be able to connect. The fact that others get in, and that I can get in at work back this up - as the routing is slightly different for the others, and for me at work. I'm willing to bet that you and I, and others that can't get in, are going thru the same server somewhere on the route, and that server is the problem! If I'm right, the more tracert's Birch gets from people that can't connect, the better chance he has of finding out where the bad "connection" is...

Why don't you post your OS type? I'm sure with that info Birch could tell you step-by-step how to do the tracert, then copy and paste it into the post. And I *know* it would help him fix this...

quote:What bothers be is I haven't changed a thing on my end, so I can't see where my pc would be the problem. It's NOT your PC I've tried 2 different PC's with 2 different OS's, and 2 different browsers (different versions on each) and still can't get in! If it was any kind of PC-specific problem, one of 'em would have gotten in...

quote:Like HarryLee, I have been able to get access since November 8th or so.

Coincidence? I'm guessing you mean you *haven't* been able to get access since 11/8? Doubt it's coincidence, I imagine you and I are both being routed thru a server that has gotten screwed up somehow, and that's why we can't get in.

Regards,

Lee

Well I was able to access all of Natural Points sites today, but only from Work. Still can't do it from home.

HarryLee, you post up an "Instructions for dummies" read me and I'll try again.

When I first saw the post I opened the dos window and tried putting in some of the stuff mentioned above, and Windows XP Pro (my system) basically said it had no idea what I was talking about.

So, put up that "step by step", and I'll give it a go.

Thanks.

Hi Jaeger

OK, here's how to do the tracert:

Open the dos window then type the following command at the prompt:

tracert -d www.naturalpoint.com

If you like, I believe you can copy the command from this post to your clipboard then paste it into the dos window by right-clicking and choosing 'paste' from the context menu. (I *think* there's a paste option in XP's dos window, don't recall though and I'm on my Windows 98 machine at work now so I can't check...)

Then press Enter to run the command - it should start producing output within a second. If it gives an error, make sure you entered it right. It may take it a while to finish.

When it's done, if the first lines have scrolled off the top of the window, click-drag the bottom edge of the dos window until it's tall enough to see all the output. Click the right mouse button in the dos window, and select "Mark" from the pop-up menu.

Then look for the line reading "Tracing route to www.naturalpoint.com [66.182.52.188]", and click and hold the left button at the beginning of the line. While holding left button, drag down to the end of the output, and drag right so that all of the output is hilighted in white.

Finally, press the "Enter" key to copy the hilighted portion onto the clipboard. Now you can paste it into your post.

As Birch said, if you're concerned about revealing your IP address, delete the first few lines following the line "over a maximum of 30 hops".

Hope this helps!

Lee

Ok, Here you go. Hope it helps.

Tracing route to www.naturalpoint.com [66.182.52.18
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms <snip>
2 10 ms 10 ms 10 ms <snip>
3 12 ms 14 ms 12 ms <snip>
4 11 ms 11 ms 12 ms <snip>
5 15 ms 15 ms 15 ms <snip>
6 17 ms 17 ms 18 ms 66.185.133.225
7 16 ms 16 ms 17 ms 66.185.148.98
8 25 ms 23 ms 23 ms 66.185.152.195
9 26 ms 25 ms 24 ms 66.185.152.196
10 22 ms 22 ms 21 ms 66.185.151.49
11 26 ms 28 ms 27 ms 66.185.139.150
12 26 ms 25 ms 26 ms 129.250.2.36
13 23 ms 24 ms 23 ms 129.250.2.216
14 98 ms 98 ms 99 ms 129.250.5.112
15 98 ms 99 ms 98 ms 129.250.3.187
16 114 ms 103 ms 98 ms 129.250.5.48
17 98 ms 98 ms 98 ms 129.250.26.34
18 99 ms * 98 ms 140.174.28.18
19 101 ms 103 ms 103 ms 216.174.225.50

20 132 ms 134 ms 136 ms 216.210.221.213

21 134 ms 135 ms 148 ms 206.58.252.67
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Thanks for the instructions.