LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   can't reach www.berbens.nl (https://www.linuxquestions.org/questions/linux-networking-3/cant-reach-www-berbens-nl-224244/)

boda 08-30-2004 06:06 AM

test

XavierP 08-30-2004 06:45 AM

Can you not reach all websites or just some websites? Can you ping them? Have you tried traceroute? What happens when you try to reach the websites? Is your firewall blocking them? Are you ate home or at work? If at work, maybe there is a site blocker.

boda 08-30-2004 06:52 AM

test

XavierP 08-30-2004 07:56 AM

well, it appears from your traceroute that the failure is either at ams-ix1.sara.computel.nl [195.69.145.35] or at the next step. I was able to get to the website.

Could you do a traceroute to a site you can get to so we can see what should happen. Also, check other failed sites in the same way to see if it happens at the same point.

It would appear that it's not a Linux problem but someone else's problem.

boda 08-30-2004 08:07 AM

test

XavierP 08-30-2004 08:18 AM

I can't see how the problem can be at your end. You are quite clearly getting part of the way - maybe there's a DNS server in your way that is blocking you.

traceroute to berbens.nl (83.137.20.90), 30 hops max, 38 byte packets
1 192.168.2.1 (192.168.2.1) 1.216 ms 1.164 ms 1.141 ms
2 10.48.128.1 (10.48.128.1) 9.024 ms 9.812 ms 9.162 ms
3 brom-t2cam1-a-ge-wan34-110.inet.ntl.com (80.1.226.33) 8.502 ms 24.335 ms 36.168 ms
4 brom-t2core-a-ge-wan61.inet.ntl.com (80.1.225.5) 37.645 ms 24.230 ms 9.368 ms
5 pop-bb-a-so-210-0.inet.ntl.com (62.253.184.105) 12.865 ms 10.899 ms 13.882 ms
6 amst-ic-1-so-000-0.inet.ntl.com (62.253.188.94) 23.893 ms 34.888 ms 31.787 ms
7 sara.ams-ix.network.bit.nl (195.69.144.35) 28.244 ms 30.768 ms 48.542 ms
8 computel.customer.bit.nl (213.136.31.82) 24.024 ms 24.960 ms 21.733 ms
9 loolaan.loolaan-sara.computel.nl (83.137.16.9) 26.653 ms 26.065 ms 27.947 ms
10 surfbird.computel.nl (83.137.20.90) 27.509 ms 24.426 ms 24.115 ms

This is mine, we can see that the ams-ix1.sara.computel.nl [195.69.145.35] part of your route comes up on mine. It's just the next 3 steps that don't connect. Try pinging the final 3 steps of my traceroute and see what happens.

boda 08-30-2004 08:23 AM

test

XavierP 08-30-2004 08:36 AM

I would say that the fact that you can't reach 2 servers nearer them than you would suggest that the problem either lies with them (maybe they can't get traffic from your ip set) or the problem lies with your ISP.

I would email the webmaster of your ISP and supply traceroute details and ping details. Also show successful pings and traceroutes to show that it's not that you can't get any website, just this one (maybe a selection of other failed traceroutes?) Maybe they can track down the problem.

NetAX 08-30-2004 10:32 AM

I agree with XavierP, it looks like a problem with your ISP. I suggest trying a different ISP, Netzeo dial up for example, or going to a friend who has a different ISP and see if you can connect to the site just to make sure the problem is within your ISP service.

boda 08-30-2004 10:53 AM

test

NetAX 08-30-2004 12:34 PM

It cant be your site. Even if the site your trying to get to is blocked, i dont think you would be able to do a tracert if its already blocked. eg. hop 1-5.

It could be that the site has blocked you for some reason or blocked a range of IP addresses.


All times are GMT -5. The time now is 09:52 AM.