Some cannot access my host

Hi all,

I am running my own server attached to the internet with a fixed ip address.
It turns out that some people (est. 50%) cannot connect to it. There is no
DNS problem as for all these people the domain name resolves nicely. My ISP
is stomped. They claim it works but I consider them lucky to be part of the
50% that can connect (and they are in the same
subnet anyway). I am getting very little help from them. Also the ADSL
provider KPN is uncooperative. I have collected some traceroutes from
several affected people. They all show timeout before it reaches my host
but only after the trace leaves my provider. They now think the problem lies
withing the KPN routers but the router is different for most cases so they
see no pattern.

Since I have a smartphone that cannot reach the site over UMTS I am myself
now also affected. I cannot get to my e-mail.

I am now quite stuck as nobody seems to even understand the problem, let
alone take it seriously. What can I do to further diagnose the issue to
provide hard evidence to my ISP and/or KPN so they can fix the problem.

Please have a go at www.klaverstijn.nl (212.129.142.65).

Looking forward to your contributions.

Kind regards,
- Jan.

Here is where my trace stops.

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Bruce.BRUCE-NGA48Y9YD>tracert www.klaverstijn.nl

Tracing route to www.klaverstijn.nl [212.129.142.65]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 1 ms <1 ms <1 ms 192.168.1.1

3 24 ms 23 ms 23 ms L100.DSL-19.LSANCA.verizon-gni.net [71.109.144.1

]

4 25 ms 25 ms 25 ms P3-0.LCR-04.LSANCA.verizon-gni.net [130.81.35.30

]

5 27 ms 27 ms 27 ms so-6-2-0-0.BB-RTR2.LAX01.verizon-gni.net [130.81

..28.229]

6 29 ms 28 ms 29 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]

7 91 ms 91 ms 91 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.64.14]

8 91 ms 90 ms 91 ms 0.so-7-0-0.BR2.CHI13.ALTER.NET [152.63.73.29]

9 91 ms 90 ms 90 ms sl-st21-chi-3-0-0.sprintlink.net [144.232.18.141

]

10 89 ms 90 ms 89 ms sl-st20-chi-1-0.sprintlink.net [144.232.8.102]

11 89 ms 89 ms 89 ms sl-franc2-8-0.sprintlink.net [144.223.241.82]

12 110 ms 110 ms 110 ms po15-0.nykcr2.NewYork.opentransit.net [193.251.2

43.205]

13 111 ms 111 ms 111 ms po11-0.nykcr3.NewYork.opentransit.net [193.251.2

42.210]

14 179 ms 179 ms 179 ms so-4-3-0-0.loncr5.London.opentransit.net [193.25

1.243.106]

15 181 ms 181 ms 181 ms ge-3-3-0-0.loncr4.London.opentransit.net [193.25

1.242.22]

16 192 ms 190 ms 192 ms po1-0-0.amscr2.Amsterdam.opentransit.net [193.25

1.242.193]

17 191 ms 192 ms 191 ms 193.251.247.210

18 191 ms 190 ms 190 ms PC14.cr2-asd4.nl.euro.net [194.134.162.10]

19 190 ms 189 ms 189 ms 10GE1-4.dr1-asd5.nl.euro.net [194.134.162.6]

20 192 ms 192 ms 192 ms 194.134.180.146

21 * * * Request timed out.

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.



Thanks,

Bruce

"Jan Klaverstijn" <(E-Mail Removed)> wrote in message
news:46856d9a$0$2842$(E-Mail Removed)...
> Hi all,
>
> I am running my own server attached to the internet with a fixed ip
> address. It turns out that some people (est. 50%) cannot connect to it.
> There is no DNS problem as for all these people the domain name resolves
> nicely. My ISP is stomped. They claim it works but I consider them lucky
> to be part of the 50% that can connect (and they are in the same
> subnet anyway). I am getting very little help from them. Also the ADSL
> provider KPN is uncooperative. I have collected some traceroutes from
> several affected people. They all show timeout before it reaches my host
> but only after the trace leaves my provider. They now think the problem
> lies withing the KPN routers but the router is different for most cases so
> they see no pattern.
>
> Since I have a smartphone that cannot reach the site over UMTS I am myself
> now also affected. I cannot get to my e-mail.
>
> I am now quite stuck as nobody seems to even understand the problem, let
> alone take it seriously. What can I do to further diagnose the issue to
> provide hard evidence to my ISP and/or KPN so they can fix the problem.
>
> Please have a go at www.klaverstijn.nl (212.129.142.65).
>
> Looking forward to your contributions.
>
> Kind regards,
> - Jan.
>

My tracert stoped at the 194.134.180.186, the same IP range as Bruce.

A whois shows . . .

OrgName: RIPE Network Coordination Centre
OrgID: RIPE
Address: P.O. Box 10096
City: Amsterdam
StateProv:
PostalCode: 1001EB
Country: NL

ReferralServer: whois://whois.ripe.net:43

NetRange: 194.0.0.0 - 194.255.255.255
CIDR: 194.0.0.0/8
NetName: RIPE-CBLK2
NetHandle: NET-194-0-0-0-1
Parent:
NetType: Allocated to RIPE NCC
NameServer: NS-PRI.RIPE.NET
NameServer: NS3.NIC.FR
NameServer: SUNIC.SUNET.SE
NameServer: NS-EXT.ISC.ORG
NameServer: SEC1.APNIC.NET
NameServer: SEC3.APNIC.NET
NameServer: TINNIE.ARIN.NET
Comment: These addresses have been further assigned to users in
Comment: the RIPE NCC region. Contact information can be found in
Comment: the RIPE database at http://www.ripe.net/whois
RegDate: 1993-07-21
Updated: 2005-08-03


The www.ripe.net web site has a contact menu. I would start there and see
what they have to say.

Best of luck and keep us posted as to what you find.

Chris

Jan Klaverstijn wrote:
> Hi all,
>
> I am running my own server attached to the internet with a fixed ip address.
> It turns out that some people (est. 50%) cannot connect to it. There is no
> DNS problem as for all these people the domain name resolves nicely. My ISP
> is stomped. They claim it works but I consider them lucky to be part of the
> 50% that can connect (and they are in the same
> subnet anyway). I am getting very little help from them. Also the ADSL
> provider KPN is uncooperative. I have collected some traceroutes from
> several affected people. They all show timeout before it reaches my host
> but only after the trace leaves my provider. They now think the problem lies
> withing the KPN routers but the router is different for most cases so they
> see no pattern.
>
> Since I have a smartphone that cannot reach the site over UMTS I am myself
> now also affected. I cannot get to my e-mail.
>
> I am now quite stuck as nobody seems to even understand the problem, let
> alone take it seriously. What can I do to further diagnose the issue to
> provide hard evidence to my ISP and/or KPN so they can fix the problem.
>
> Please have a go at www.klaverstijn.nl (212.129.142.65).
>
> Looking forward to your contributions.
>
> Kind regards,
> - Jan.
>
>

Jan:

Here are the results from my Windows 98se system.

HTH & GL

John

Tracing route to niwg-n-0e41.mxs.adsl.euronet.nl [212.129.142.65]

over a maximum of 30 hops:



1 <10 ms <10 ms <10 ms [192.168.2.1]
2 33 ms 32 ms 31 ms 10.6.27.1
3 31 ms 31 ms 29 ms p11-0.lcr-01.pitbpa.verizon-gni.net
[130.81.44.20]
4 36 ms 35 ms 38 ms 130.81.28.12
5 39 ms 40 ms 39 ms 0.so-3-2-0.xt2.dca6.alter.net
[152.63.39.177]
6 62 ms 61 ms 61 ms 0.so-5-0-0.xl2.chi13.alter.net
[152.63.64.14]
7 62 ms 62 ms 62 ms 0.so-7-0-0.br2.chi13.alter.net
[152.63.73.29]
8 62 ms 62 ms 62 ms sl-st21-chi-3-0-0.sprintlink.net
[144.232.18.141]
9 62 ms 62 ms 62 ms sl-st20-chi-1-0.sprintlink.net
[144.232.8.102]
10 62 ms 62 ms 62 ms sl-franc2-8-0.sprintlink.net
[144.223.241.82]
11 82 ms 81 ms 80 ms po15-0.nykcr2.newyork.opentransit.net
[193.251.243.205]
12 81 ms 81 ms 80 ms
gi0-0-0.nykcr3.newyork.opentransit.net [193.251.240.230]
13 152 ms 151 ms 150 ms
so-4-3-0-0.loncr5.london.opentransit.net [193.251.243.106]
14 150 ms 151 ms 162 ms
ge-4-0-0-0.loncr4.London.opentransit.net [193.251.242.182]
15 161 ms 160 ms 161 ms
po1-0-0.amscr2.amsterdam.opentransit.net [193.251.242.193]
16 161 ms 162 ms 160 ms 193.251.247.210
17 161 ms 162 ms 162 ms pc14.cr2-asd4.nl.euro.net
[194.134.162.10]
18 160 ms 159 ms 161 ms 10ge1-2.dr2-asd4.nl.euro.net
[194.134.162.2]
19 159 ms 162 ms 162 ms 194.134.180.18
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 *

--
\\\||///
------------------o000----(o)(o)----000o----------------
----------------------------()--------------------------
'' Madness takes its toll - Please have exact change. ''

John Dulak - Gnomeway Services - http://tinyurl.com/2qs6o6

"Jan Klaverstijn" <(E-Mail Removed)> wrote in message
news:46856d9a$0$2842$(E-Mail Removed)...
> Hi all,
>
> I am running my own server attached to the internet with a fixed ip
> address. It turns out that some people (est. 50%) cannot connect to it.
> There is no DNS problem as for all these people the domain name resolves
> nicely. My ISP is stomped. They claim it works but I consider them lucky
> to be part of the 50% that can connect (and they are in the same
> subnet anyway). I am getting very little help from them. Also the ADSL
> provider KPN is uncooperative. I have collected some traceroutes from
> several affected people. They all show timeout before it reaches my host
> but only after the trace leaves my provider. They now think the problem
> lies withing the KPN routers but the router is different for most cases so
> they see no pattern.
>
> Since I have a smartphone that cannot reach the site over UMTS I am myself
> now also affected. I cannot get to my e-mail.
>
> I am now quite stuck as nobody seems to even understand the problem, let
> alone take it seriously. What can I do to further diagnose the issue to
> provide hard evidence to my ISP and/or KPN so they can fix the problem.
>
> Please have a go at www.klaverstijn.nl (212.129.142.65).
>
> Looking forward to your contributions.
>
> Kind regards,
> - Jan.
>

Double click on www.klaverstijn.nl goes well.
ping www.klaverstijn.nl goes well
tracert www.klaverstijn.nl cannot go outside my linksys adsl-modem-router
as follow:
Tracing route to www.klaverstijn.nl [212.129.142.65]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
etc....etc...
any idea ?

"ray" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Jan Klaverstijn" <(E-Mail Removed)> wrote in message
> news:46856d9a$0$2842$(E-Mail Removed)...
>> Hi all,
>>
>> I am running my own server attached to the internet with a fixed ip
>> address. It turns out that some people (est. 50%) cannot connect to it.
>> There is no DNS problem as for all these people the domain name resolves
>> nicely. My ISP is stomped. They claim it works but I consider them lucky
>> to be part of the 50% that can connect (and they are in the same
>> subnet anyway). I am getting very little help from them. Also the ADSL
>> provider KPN is uncooperative. I have collected some traceroutes from
>> several affected people. They all show timeout before it reaches my host
>> but only after the trace leaves my provider. They now think the problem
>> lies withing the KPN routers but the router is different for most cases
>> so they see no pattern.
>>
>> Since I have a smartphone that cannot reach the site over UMTS I am
>> myself now also affected. I cannot get to my e-mail.
>>
>> I am now quite stuck as nobody seems to even understand the problem, let
>> alone take it seriously. What can I do to further diagnose the issue to
>> provide hard evidence to my ISP and/or KPN so they can fix the problem.
>>
>> Please have a go at www.klaverstijn.nl (212.129.142.65).
>>
>> Looking forward to your contributions.
>>
>> Kind regards,
>> - Jan.
>>
>
> Double click on www.klaverstijn.nl goes well.
> ping www.klaverstijn.nl goes well
> tracert www.klaverstijn.nl cannot go outside my linksys adsl-modem-router
> as follow:
> Tracing route to www.klaverstijn.nl [212.129.142.65]
> over a maximum of 30 hops:
>
> 1 1 ms 1 ms 1 ms 192.168.1.1
> 2 * * * Request timed out.
> etc....etc...
> any idea ?
>
hum hum...it's not "etc...etc...etc" - it's ...
Tracing route to www.klaverstijn.nl [212.129.142.65]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 131 ms 26 ms 26 ms niwg-n-0e41.mxs.adsl.euronet.nl
[212.129.142.65]


Trace complete.

All goes well, but there is no trace(my router/modem has ipadress
62.235.208.123)