From: wayne <wa...@ny...> - 2002-11-06 17:57:35
|
> From: xxxx > To: "wayne" <wa...@ny...> > Subject: Nesma I've copied this (suitably anonymized) to the proxytools-users list so others can also benefit. Subscribe at the proxytools web site in my sig below. > Hi Wayne > > Just to let you know the Nesma config does not work. It keps saying you are > offline. Maybe that's because it knows no proxies to connect to. It needs at least one live one to prove it's on-line. Normally, I can guarantee one because every ISP that censors must provide users with one (or more), or a transparent proxy connection. It would seem that they have changed proxies since my last information from there. Ideally someone there (you?) will run statProxy on all of the proxies they have given you and send the results to me for inclusion in the localProxy database. It would also be good to send tests on the ones LP is trying to use (they are probably dead though). I can't know what proxies they give you unless someone tells me, and even then I probably can't test them for you because they are not accessible from outside. I found this in their proxy configuration info on their web site: proxy.nesma.net.sa, port 80. A way for you to get started immediately, is to select your configuration, put proxy.nesma.net.sa:80 in the proxy hints box on LP's 'advanced' window and click the 'Test and merge user proxies'. Wait for all the tests to finish, then restart LP so it can build a new configuration for you. Note that you can always do this with any proxy you find. That resolves to 8 different proxy addresses, using: nslookup proxy.nesma.net.sa Non-authoritative answer: Name: proxy.nesma.net.sa Addresses: 212.71.32.96, 212.71.32.97, 212.71.32.98, 212.71.32.87 212.71.32.86, 212.71.32.93, 212.71.32.94, 212.71.32.95 Most are new, and are not in the localProxy database. 97 and 98 were already in the database, and I can't see why they didn't work. You'd need to run statProxy as below on them so we can sort that out. Note though, that these guys sometimes lie to the outside world about such addresses. But I think my info was good when those were added. Please run this to help others: perl statProxy.pl -t all:-18 proxy.nesma.net.sa Wait until it finishes and post the results to me. Then I can include them in the database for everyone (along with all the latest test results on proxies). > I tried the Awalnet config and that sort of works OK. Many of those proxies have probably changed too. You may not have complete access to those either. If you can find their recommended proxy configuration at http://www.awalnet.net.sa/, run the same test as above on it. I can't even access that page from outside! > As an aside, is there a quick way of changing the proxy settings > automaticaly. > > So when you are online you don't have to go Tools...Options etc Oh, in the web browser? I didn't include the code to *write* the registry because of the differences between Windows versions and the (almost guaranteed) possibility that somewhere it would screw up the user's registry. There's code to read it, so LP can use any proxies found there (the ones you've put in the browser config) to make it's build with. Come to think of it, LP should have found your existing web browser proxies when it started up. Do you have the web browser set up with the proxy address above? What operating system are you using? > Regards > > xxxx -- wa...@ny... http://proxytools.sourceforge.net/ |