Cannot connect to my Webhost.. Oscarent.net

[-Jayenkai-]

My website is hosted by Oscarent.net

For the past week or so, I haven't been able to access it.. at all.
At first, I assumed it'd been the server, but then I realised that my Blogger blog was still managing to post entries to the server. So then I assumed it was probably a DNS thing, occasionally NTL takes a couple of days to catch up..
But no, it wasn't that either.
Using transparent "Free-Anonymous-Web" proxies, I've been able to access my site's web pages without issue. But of course, using those, I can't FTP/otherwise, meaning I can't actually update any parts of my site.
I've tried 10-20 different NTL proxies, and none of them are letting me into my site.

So, basically...

1) Can You access Oscarent.net?
2) Why can't I access Oscarent.net?
and, 3) What can NTL do to help me regain access to Oscarent.net?!

[Jon M]

Download Failed (1)

What is your website URL... ?

(before I move this out of the NTL BB discussion area, lets find out if any other NTL users can access it)

[-Jayenkai-]

Specifically, http://oscarent.net/~jayenkai/ (http://oscarent.net/%7Ejayenkai/) but I can't seem to connect to any of oscarent.net |Edit| *tests to make sure* Not even by pinging it! |edit|

[Jon M]

It looks fine from here (non NTL)

---------- Post added at 14:58 ---------- Previous post was at 14:39 ----------

We have a few NTL users here who have experienced similar issues with other domains. I'll see if I can find one of those threads.

[Aragorn]

Just tried on my NTL connection and it just times out. Works fine when I'm vpn'ed into work and using their internet gateway.

[Jon M]

You've tried alternative proxies, but have you tried alternative DNS servers ?

[Bifta]

Works fine here, though going by their site it's definately not someone I'd entrust hosting anything important to.

[-Jayenkai-]

You've tried alternative proxies, but have you tried alternative DNS servers ?

Does that just give out the IP for the server?
I assumed that'd be right, but no, I haven't given that a go.
Any suggestions for testing?
|Edit| never mind, found a topic. giving it a go.... ... Tried a couple, but no luck so far.. I'll keep trying |edit|

|Edit2| Right, checking here.. http://www.dnsstuff.com/tools/ping.ch?ip=oscarent.net That site pings oscarent.net, giving the ip 69.50.161.74 If I then ping 69.50.161.74, it timeout's.. So, that couldn't be a DNS issue.. Could it? |edit2|

[Jon M]

I used to use the demon DNS servers to test problems like this... I can't remember them offhand though.

It also depends on how you connect, via the cable modem directly or whether you have a router. If it's the former via ethernet you'll have to manually switch from getting DNS servers automatically with DHCP to a manually assigned one. I'm not sure if a USB connection to the modem offers the same level of configuration.

[Paul]

I cannot access it from here (and before anyone blames the proxy servers, they are currently turned off in Nottingham).

[Jon M]

Looks like Demon don't allow DNS queries outside their IP range anymore, oh well.

[Cyrill666]

Hello,

I've had a similar problem since about 4am this morning when I could no longer get http traffic to/from my server (all other services, email, ftp etc seem fine). I can work around the problem by changing my proxy.

for info - the site is www.yarm.net

:rolleyes:

[Jon M]

Next thing to do is test whether you can view via IP.. go to:
http://69.50.161.74/~jayenkai/
and see what happens.

[-Jayenkai-]

Well, if I can't ping it!!!.. (ie, no I can't get there, either)

[Jon M]

You can "ping" a name as well as an IP address, I didn't know whether you'd done the latter.

[Cyrill666]

A tracert might shed some light on where the problem is?

I've had a similar problem in the past which turned out to be my hosting company blocking the NTL proxy server I was using. Might be worth contacting your host?

[AbyssUnderground]

Does not work for me either. Times out using the domain and IP.

2Mbps NTL, Middlesbrough

[Paul]

Well, if I can't ping it!!!.. (ie, no I can't get there, either)Not being able to ping a site doesn't necessarily mean much, you can't ping cableforum.co.uk :)

[JohnHorb]

Well the name is resolving OK, so not a DNS issue, but a tracert seems to indicate its an NTL issue somewhere:-

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\John>nslookup oscarent.net
Server: cache1.ntli.net
Address: 194.168.4.100
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: oscarent.net
Address: 69.50.161.74

C:\Documents and Settings\John>tracert oscarent.net
Tracing route to oscarent.net [69.50.161.74]
over a maximum of 30 hops:
1 * 9 ms 11 ms 10.10.224.1
2 9 ms 23 ms 19 ms bagu-t2cam1-a-ge95.inet.ntl.com [80.5.162.13]
3 11 ms 9 ms 15 ms bagu-t2core-a-ge-wan61.inet.ntl.com [80.5.161.5]
4 33 ms 9 ms 10 ms man-bb-a-so-100-0.inet.ntl.com [62.253.188.25]
5 14 ms 11 ms 35 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
6 20 ms 14 ms 16 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 16 ms 18 ms 22 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 19 ms 17 ms 18 ms gfd-bb-a-so-500-0.inet.ntl.com [213.105.172.137]
9 16 ms 25 ms 16 ms gfd-dc-a-ge400.inet.ntl.com [62.253.188.154]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15

[jellybaby]

Times out for me too

[Jon T]

I can't get to it here:

1 1 ms 1 ms 1 ms cpc2-mfld8-3-0-cust***.nott.cable.ntl.com [86.9.
59.206]
2 9 ms 7 ms 7 ms 10.25.71.254
3 11 ms 11 ms 8 ms nott-t2cam1-b-v107.inet.ntl.com [81.109.167.149]

4 12 ms 10 ms 15 ms nott-t2core-b-ge-wan84.inet.ntl.com [80.1.79.225
]
5 10 ms 12 ms 11 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 13 ms 12 ms 25 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]

7 22 ms 19 ms 18 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

8 19 ms 20 ms 19 ms gfd-bb-a-so-500-0.inet.ntl.com [213.105.172.137]

9 19 ms 19 ms 20 ms gfd-dc-a-ge400.inet.ntl.com [62.253.188.154]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

[JohnHorb]

Could be a routing problem somewhere, or someone is blocking NTL IPs?

[marky]

I get Nothing, ive tried a few different ntl proxys and nothing :shrug:

[-Jayenkai-]

'tis a bit mental, really..
So, what's the theory? An NTL issue, or something at their end, 'cos I'm just completely out of ideas, to be honest..

Either way, looks like I'm after a new host, too, whilst I'm at it..

[marky]

I would ticket the host with your ip as reference, then take it from there, i'm still having problems with mine, they can be very ignorent :shrug:

[Chris W]

hmm... can be traced to from outside the ntl network

1 L300.VFTTP-04.DLLSTX.verizon-gni.net (72.64.77.1) 9.838 ms 9.508 ms 9.979 ms
2 P1-3.LCR-03.DLLSTX.verizon-gni.net (130.81.37.32) 9.838 ms 9.197 ms 9.946 ms
3 so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net (130.81.17.173) 9.920 ms 9.818 ms 9.976 ms
4 69.31.63.73 (69.31.63.73) 9.911 ms 9.465 ms 9.904 ms
5 0.so-2-1-0.cr1.sfo1.us.nlayer.net (69.22.142.85) 52.218 ms 49.334 ms 49.983 ms
6 ge1-1.hr1.sfo1.us.nlayer.net (69.22.143.2) 52.352 ms 49.318 ms 52.424 ms
7 atrivo.ge1-4.hr1.sfo1.us.nlayer.net (69.22.128.250) 52.430 ms 51.984 ms 52.292 ms
8 69.50.161.74-custblock.intercage.com (69.50.161.74) [open] 52.426 ms 51.823 ms 54.897 ms

but not from inside where i am...

Last login: Sat Jan 14 21:35:26 on console
Welcome to Darwin!
Chris-Computer:~ Chris$ traceroute 69.50.161.74
traceroute to 69.50.161.74 (69.50.161.74), 64 hops max, 40 byte packets
1 speedtouch.lan (10.0.0.138) 2.394 ms 1.139 ms 1.018 ms
2 brnt-bam-1.inet.ntl.com (62.253.189.142) 11.230 ms 11.030 ms 10.630 ms
3 brnt-t2core-a-ge-wan63.inet.ntl.com (213.105.199.5) 14.646 ms 13.188 ms 15.719 ms
4 bre-bb-a-so-400-0.inet.ntl.com (62.253.188.126) 15.566 ms 14.844 ms 17.052 ms
5 gfd-bb-b-so-700-0.inet.ntl.com (213.105.172.150) 16.338 ms 12.003 ms 19.272 ms
6 nth-bb-a-so-000-0.inet.ntl.com (62.253.185.97) 16.315 ms 19.340 ms 16.514 ms
7 nth-bb-b-ae0-0.inet.ntl.com (62.253.185.118) 17.616 ms 16.786 ms 15.999 ms
8 lee-bb-a-so-600-0.inet.ntl.com (62.253.185.102) 19.074 ms 20.047 ms 20.206 ms
9 pop-bb-b-so-100-0.inet.ntl.com (62.253.185.238) 24.536 ms 27.042 ms 24.078 ms
10 gfd-bb-a-so-500-0.inet.ntl.com (213.105.172.137) 25.220 ms 27.569 ms 27.029 ms
11 gfd-dc-a-ge400.inet.ntl.com (62.253.188.154) 27.615 ms 26.214 ms 25.688 ms
12 * * *
13 * * *

[neoapple]

yer im having same issues wwith other sites
im in bromley area
i can access http://board.iexbeta.com/
but i cant go direct to http://iexbeta.com/
now i badly need access to this main part as im a news crew person there!

[JohnHorb]

OK from here (NTL connection).

---------- Post added at 18:58 ---------- Previous post was at 18:55 ----------

Route to oscarent now seems to be sorted:-

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\John>tracert oscarent.net
Tracing route to oscarent.net [69.50.161.74]
over a maximum of 30 hops:
1 22 ms 8 ms 8 ms 10.10.224.1
2 8 ms 7 ms 9 ms bagu-t2cam1-a-ge95.inet.ntl.com [80.5.162.13]
3 15 ms 9 ms 9 ms bagu-t2core-a-ge-wan61.inet.ntl.com [80.5.161.5]
4 15 ms 8 ms 31 ms man-bb-a-so-100-0.inet.ntl.com [62.253.188.25]
5 26 ms 14 ms 10 ms 212.187.137.1
6 9 ms 9 ms 9 ms so-6-0-0.mp2.manchesteruk1.level3.net [4.68.113.
114]
7 16 ms 16 ms 24 ms ae-1-0.bbr2.london1.level3.net [212.187.128.57]
8 16 ms 16 ms 16 ms unknown.level3.net [212.187.131.187]
9 16 ms 17 ms 16 ms ge5-3-0-1000m.ar2.lon3.gblx.net [208.50.13.193]
10 83 ms 83 ms 90 ms so5-0-0-2488m.ar2.nyc1.gblx.net [67.17.64.150]
11 87 ms 85 ms 111 ms gblx.ge-2-0-0.cr1.nyc3.us.nlayer.net [69.31.95.1
93]
12 157 ms 197 ms 160 ms 0.so-0-3-0.cr1.sfo1.us.nlayer.net [69.22.142.78]
13 156 ms 157 ms 157 ms ge4-8.hr1.sfo1.us.nlayer.net [69.22.143.14]
14 161 ms 163 ms 158 ms atrivo.ge1-4.hr1.sfo1.us.nlayer.net [69.22.128.2
50]
15 156 ms 157 ms 158 ms 69.50.161.74-custblock.intercage.com [69.50.161.
74]
Trace complete.
C:\Documents and Settings\John>

[-Jayenkai-]

Hurrah!
Yes, it's back again, for whatever reason. So, um, case closed I guess, and we'll probably never know the true reason why.

Thanks everyone for your help...