Forum Home
Press F1
 
Thread ID: 24277 2002-09-07 09:46:00 Proxy Software returns WSANO_DATA TGhost (1798) Press F1

Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 1436997888 bytes) in C:\xampp\htdocs\PF1\thread.php on line 92
Post ID Timestamp Content User
77389 2002-09-07 09:46:00 First off, this is my first post here (like a quick glance at the post count wouldn't tell you that), although I've had a subscription to PC World for around 4 years now, and have got one of the old "Evolve" T-Shirts that I won from a letter of the month, I think it was October 1999...anyway, I've recently been customising my Windows box with more and more Linux-esque tools (read as open source, configuration in text files that are not really end user friendly) tools and recently acquired Prixovy (http://www.privoxy.org) (it's a continuation of Junkbusters that's still supported), a proxy with some very powerful features that I'll be taking advantage off to help make websites i commonly visit more usuable to me by inserting CSS stylesheets or Javascript or even just some plain formatting changes right into the pages before they reach my browser (and with the nice side-effect of blocking ads .. -block pressf1.co.nz and -block pcworld.co.nz, of course)..but, anyway, enough of the preamble. Well, maybe a little more.

Now, I've noticed a real degridation in the speed of my dial-up connection (XTRA) after installing Privoxy, and it's not to be completely written off to the problem I have, as it is mentioned in their FAQ that filtering a web page requires loading it into a buffer and then working with it, but, I've noticed that pages will only load after the error message pops up in the Privoxy console. That error would of course be the WSANO_DATA mentioned in the title of this post...the full line is;

Error: Unable to get my own hostname: WSANO_DATA - Valid name, no data record of requested type.

After a little searching in Google I found a few cryptic pieces, like the following;

This error occurs when a database function, such as resolving an host name into an internet address, fails. This is typically a configuration or data entry problem, such as an invalid host name or non-existent service.

The requested name is valid, but does not have an Internet IP address at the name server. This is not a temporary error. This means another type of request to the name server will result in an answer. For protocol and services resolution, the name or number was not found in the respective database.

The name you have used is not an official hostname or alias. This is not a software error, another type of name server request may be successful. Any of the Winsock name resolution functions can fail with this error. The Winsock API does not provide any way to select specific name resolution protocols, server address, or record type.

TCP/IP scenario: Most Winsock implementations use domain name system (DNS) protocol for hostname to address resolution, although a few use Network Information System (NIS). Assuming you have a name server configured instead of or as well as a host table, a hostname resolution request causes a Winsock DLL to send a DNS "A" record query (address query) to the configured DNS query. If you have more than one server configured, the hostname query fails only after the Winsock DLL has queried all servers.

Check that you have a name server(s) and/or host table configured. If you are using a name server(s), check whether the server host(s) are up. For example, you can try to ping the server(s).

You could also try to resolve another hostname you know should work, to check that the name resolution server application is running.

If you are using a host table exclusively, you'll need to update it to add the destination hostname and address.

All of which, of course, means absolutely nothing to me.

Now I'm going to do the clueless newbie thing and list absolutely everything I think could be remotely related;

- I've got a dialup connection to XTRA.
- The network settings on my computer have been replaced several times as an inbuilt Ethernet card can conflict with my internet connection.

That's about it, really. Pinging and tracert'ing 127.0.0.1 (localhost) don't come up with any errors, so...

...Any ideas, or any other information that I should give to help people help me solve this problem?
TGhost (1798)
77390 2002-09-07 10:35:00 I have read some of the Prixovy sites information. Have you made many configuration changes so far and did junkbuster use to work properly?
Are you running Windows 2000?
The message seems to indicate that prixovy cannot resolve the dns name of your PC. Depending on what version of windows you have, the DNS name can be set up in various places.
Can you ping xtra.co.nz OK? Or 202.27.184.3?
Then you can tracert 202.27.184.3 to see the path prixovy takes
If you run ipconfig /all in windows 2000, it will tell you what your dns name is to see if that is a problem
You can also run nslookup for DNS problems (if you have windows NT/XP/2000
Marty2001 (421)