I seem to be unable to acess my website link (http://www.scolebrook.co.uk) I'm getting 'invalid url' messages and a tracert to scolebrook.co.uk is timing out once it gets to hop 7.
Just wondering if others could try it before I start moaning at my hosting company.
Just got through from work
Working fine for me ???
No problems here, Ray:
tracert www.scolebrook.co.uk
Tracing route to scolebrook.co.uk [80.82.123.181]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.1.254
2 14 ms 11 ms 11 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 14 ms 15 ms 14 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 14 ms 13 ms 11 ms mfnx-gw-a.lonap.net [193.203.5.16]
5 14 ms 29 ms 15 ms ge-2-1-0.mpr1.lhr2.uk.above.net [64.125.28.141]
6 15 ms 13 ms 13 ms 79.141.38.196.available.above.net [79.141.38.196]
7 16 ms 13 ms 15 ms prohost3.34sp.com [80.82.123.181]
Trace complete.
That's strange, Steve, I've just tried again and get the message 'url is invalid and cannot be loaded' wonder if it's an idnet routing problem again?
It would be odd, Ray, as I routed through IDNet.
I presume you've tried other DNS servers
That's different to what I've just got, Rik,
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ray Coles>tracert scolebrook.co.uk
Tracing route to scolebrook.co.uk [80.82.123.181]
over a maximum of 30 hops:
1 73 ms 99 ms 99 ms speedtouch.lan [192.168.1.254]
2 14 ms 17 ms 16 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 14 ms 14 ms 15 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 16 ms 16 ms 16 ms mfnx-gw-a.lonap.net [193.203.5.16]
5 26 ms 16 ms 15 ms ge-2-1-0.mpr1.lhr2.uk.above.net [64.125.28.141]
6 16 ms 15 ms 16 ms 79.141.38.196.available.above.net [79.141.38.196
]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10
Form Idnet
C:\Users\Rich>tracert www.scolebrook.co.uk
Tracing route to scolebrook.co.uk [80.82.123.181]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms www.routerlogin.com [192.168.0.1]
2 14 ms 13 ms 14 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 13 ms 13 ms 13 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 13 ms 13 ms 14 ms mfnx-gw-a.lonap.net [193.203.5.16]
5 13 ms 17 ms 14 ms ge-2-1-0.mpr1.lhr2.uk.above.net [64.125.28.141]
6 14 ms 14 ms 17 ms 79.141.38.196.available.above.net [79.141.38.196]
7 16 ms 15 ms 14 ms prohost3.34sp.com [80.82.123.181]
Trace complete.
Quote from: Steve on Apr 25, 2010, 10:49:39
I presume you've tried other DNS servers
Not yet, Steve, I'm currently using opendns.
Do a malware scan maybe?
Or switch to IDNet if it's working that way.
Quote from: Ray on Apr 25, 2010, 10:52:39
Not yet, Steve, I'm currently using opendns.
Open DNS all to frequently does this. I have ended up changing back to ISP Dns many times. I only use OpenDNS during school holidays now.
I'm also having problems reaching a number of websites since the early hours, www.vbadvanced.com being one of them.
[EDIT] I can access your site though Ray.
Quote from: zappaDPJ on Apr 25, 2010, 12:02:19
I'm also having problems reaching a number of websites since the early hours, www.vbadvanced.com being one of them.
Vbadvanced is off line Zap, it was down early last Sunday too,Brian or Zachery may be updating things.
Ah, cheers, tell them to get their finger's out, I need to check a few things :D
http://downforeveryoneorjustme.com/http://www.vbadvanced.com
Its down its not just you !!
;D
Quote from: Rik on Apr 25, 2010, 11:04:50
Or switch to IDNet if it's working that way.
I've just done that, Rik, and I still can't access it, also done a scan with Malwarebytes and that's come up clean. :wall:
Quote from: rgt247 on Apr 25, 2010, 12:06:37
http://downforeveryoneorjustme.com/http://www.vbadvanced.com
Its down its not just you !!
Ever feel they're picking on you, Zap? ;D
Have you tried through a proxy, Ray?
Have you cleared your DNS cache Ray?
Quote from: Rik on Apr 25, 2010, 12:18:36
Have you tried through a proxy, Ray?
Yes, Rik, and I can get onto the site through a proxy.
Weird. Could something be blocking your IP address?
Quote from: Rik on Apr 25, 2010, 12:36:40
Weird. Could something be blocking your IP address?
It is, Rik, I'm stumped at the moment, I'm wondering if it's something to do with my router as the problem is the same on all my machines, which seem to indicate it's got to be either the router or as you say something blocking the IP address. ???
Do you have a spare you could try, Ray?
Quote from: Rik on Apr 25, 2010, 13:18:25
Do you have a spare you could try, Ray?
Yes, Rik, I'm just about to try my Dg834G so If I dissappear for a while you'll know why! ;)
You're still here I see. :)
Well that didn't make any difference, now back on my old faithful Speedtouch, think I'll have a word with my web hosting company, 34sp, tomorrow to see if the problem is their end. :comp:
It seems the most likely explanation atm. :( Anything we could do to help out in the short term?
I don't understand this.
Everyone else can access the site via IDNet or Opendns and via proxy ,I used hidemyass it was a bit slow but it did load.
Ray cannot access the site on any of his machines even with a change of router. If Ray's IP address was blocked surely the use of a proxy would negate that. So the problem must be local, Is this a software security suite issue or is the browser looking for a local address for the website which does exist anymore.Have you cleared the browsers cache?
Can you ping 80.82.123.181 Ray?
I don't either, Steve, I've tried accessing on both desktops and my Home server and get the same on all machines, I've tried FF, IE8 and Opera, I've flushed the dns cache rebooted the pc and my router, I'm baffled. :-\
Pinging fails as you can see below and a tracert times out after hop 6.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ray Coles>ping 80.82.123.181
Pinging 80.82.123.181 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 80.82.123.181:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Ray Coles>
Very odd, Ray. :shake:
ping 80.82.123.181
Pinging 80.82.123.181 with 32 bytes of data:
Reply from 80.82.123.181: bytes=32 time=15ms TTL=58
Reply from 80.82.123.181: bytes=32 time=14ms TTL=58
Reply from 80.82.123.181: bytes=32 time=20ms TTL=58
Reply from 80.82.123.181: bytes=32 time=15ms TTL=58
Ping statistics for 80.82.123.181:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 20ms, Average = 16ms
Have you tried from Safe Mode with Networking Ray?
Quote from: Rik on Apr 25, 2010, 17:50:16
Very odd, Ray. :shake:
It is, Rik, i've just dug out an old PC with XP Pro on it, that's not been used for a couple of years and the only security softwaer on it is windows firewall, and tried that with nothing else connected to the network and still unable to get to the site. I'm becoming convinced that some security software on the hosting site is blocking my IP as I can't access my site admin panel or ftp to my webspace either.
It does sound like you've upset them, doesn't it. :(
Problem solved, my IP was being blocked by the hosting server for some reason. :)
Quote from: Ray on Apr 27, 2010, 11:59:55
Problem solved, my IP was being blocked by the hosting server for some reason. :)
:thumb: Glad its sorted Ray
At least our diagnosis was correct, Ray. :)
Quote from: Rik on Apr 27, 2010, 12:29:12
At least our diagnosis was correct, Ray. :)
They don't like Ray? ;)
;D
Quote from: Rik on Apr 27, 2010, 12:29:12
At least our diagnosis was correct, Ray. :)
Indeed, Rik, it seemed the most likely as I wasn't having problems with any other sites.
We can change that. :evil:
;D
;D
That didn't last long I can't access my website again. :bawl:
You have upset them, Ray. ;) It's working fine from here (link in OP).
Seems so, Rik, I've reopened my ticket, any way they know what's causing it but obviously haven't found out why yet. :shake:
It seems so basic a fault that they'd have the answer immediately. :(
I've had a reply from them, Rik, and they have asked for times when I first noticed the problem, I think he's going through their server logs to see what he can find.
Quote from: Ray on Apr 29, 2010, 08:59:25
I've had a reply from them, Rik, and they have asked for times when I first noticed the problem, I think he's going through their server logs to see what he can find.
It does make you wonder what happens in situations like this, unless Ray is a undercover hacker ;)
Quote from: Gary on Apr 29, 2010, 09:14:41
It does make you wonder what happens in situations like this, unless Ray is a undercover hacker ;)
;D
I wouldn't know where to start, Gary. :)
Don't look at me, I was just experimenting, honest. ;D
They thought they had found the cause as one of their server security rules blocking me, but I've just tried it and they were wrong.
Move it to IDNet. ;)
Quote from: Ray on Apr 29, 2010, 09:18:17
;D
I wouldn't know where to start, Gary. :)
Denial is the best form of defence hey, Ray ;)
It is is strange, Gary, I've been using them to host my web site for just over 3 years now and I've never had any problems before.
Quote from: Ray on Apr 29, 2010, 12:01:25
It is is strange, Gary, I've been using them to host my web site for just over 3 years now and I've never had any problems before.
That is odd Ray, it does make you wonder why on earth its happening, if it were a black on IDNet we would all have the issue :dunno:
I think I've got them baffled, they can't find anything in their logs to indicate why I'm being blocked, this is turning into a similar saga to your PC repair, Rik. ;D
;D
Finally sorted at last, it due to me having several ftp login failures so it decided to block my IP address, presumeably because they beefed up their security last year after they had several web sites hacked.
They now have a facility in your account where you can block ftp access and I must admit this has caught me out a few times because I've forgotten I've used it, this is obviously what has caused the excessive ftp login failures, must remember to re enable ftp access before I try and update my site in future :red:
At least you got there, Ray. :)
Indeed, Rik, bit embarrassing though. ;)
At least they couldn't see you. ;)
True! ;)