Problem connecting to a website. (more complicated than that though)
 

For the past few days i've had trouble connecting to ONE website. The website is run by a mate, and i have admin on there. But, i've had major difficulties getting on there. I run Mproxy, which has a list of all the ntl proxies, and runs through them finding the fastest proxy for each site, and in my IE, i have 127.0.0.1, which then means that all sites are proxied through Mproxy.
So i know that it's not just my local server that's having the trouble, i tried turning proxies off, so that it just used my local server, and the error changed.

When i use proxies i get the error 'HTTP 500, internal error'. If i turn proxies off, i get a normal 'the page cannot be displayed' error.

I've tried different settings with cookies, cleared my cache, turned off my firewall, ran virus checks, ad-aware, tried everything i can think of. With no avail. :-|

I only realised the difference in error, with proxies and without, today, so i'm guessing that has to be the trouble. But i don't understand why. Everyone else i know that uses the website, has no problems. Some of which are with ntl, which confuses me more.
Any ideas would be very gratefully accepted! :-)

Re: Problem connecting to a website. (more complicated than that though)
 

Hi DieDieMyDarling and :welcome: to nthellworld.co.uk :)

Are you connecting to this site via http or https ?

Can you ping the site ?

Re: Problem connecting to a website. (more complicated than that though)
 

It's Http. I used ping from dos prompt, and strangely it works if i use www.sitename.com, but NOT if i use http://www.sitename.com. Even though, if i typed the site addresss in, leaving out the http://, it gets added on when the site loads. Not sure if that's normal. I don't really know much about ping, it's only something i've used recently.

Re: Problem connecting to a website. (more complicated than that though)
 

If the person running the site is using a dynamic ip service like no-ip or dyn-dns then that could explain it. Open up a command promp and then type nslookup *sitename* and it should give you a numeric address.

Type that address into internet explorer IE http://111.111.111.111

If you have to connect to a different port put the port number on the end IE http://111.111.111.111:port number

Re: Problem connecting to a website. (more complicated than that though)
 

Ok, i just tried that, and got the error 'cache2.ntli.net can't find' address 'server failed'. I tried the ping again, and that worked ok. So i'm guessing it's my local server that's the problem? I still find it strange that out of all the websites i've tried, this is the only one not working. I've tried a lot, as usually when my area gets put on a proxy, a few sites don't work.

Re: Problem connecting to a website. (more complicated than that though)
 

???? Thats a bit strange...

From the command prompt type ipconfig /all and check that the dns servers are 192.168.4.100 and 192.168.8.100

I use Mproxy myself and it can do strange things. Try putting a proxy or two in IE and make sure you use port 8080

EDIT - If you want to you can PM me the site name and I will see if I can ping/connect for you.

Re: Problem connecting to a website. (more complicated than that though)
 

Did you mean 194.168.4/8.100??
Or would the difference at the beginning just be due to my location?

Re: Problem connecting to a website. (more complicated than that though)
 

DOH !!! - :blush: Yep...

194.168.4.100 / 194.168.8.100

LOL