|
|
Posted by db on 10/11/05 01:08
"George Hester" <hesterloli@hotmail.com> wrote in message
news:_NA2f.37948$7b6.19207@twister.nyroc.rr.com...
> Getting connected correctly is the problem. These latest host files and
> dll
> fixes are sending us to fraudulent peer cache servers. When we get
> connected and have no chat channels and cannot whois ourselves that says
> the
> host whereever that is we connected to is a fraud. And it is harming the
> Network.
>
> --
>
> George Hester
> _________________________________
That sounds ridiculous to me, George. For a start there are only a handful
of cache servers operating and all of those are closely monitored by people
who have a relatively high, or high, level of understanding of the WPNP.
Anything obviously untoward should reveal itself quite quickly particularly
given the amount of focus at this moment in time.
Once your WinMX client has gone "green" (connected) the operations of your
client have absolutely nothing to do with the cache servers at all; your
client simply connects to other peers running primary connections. If you
have problems, like an inability to list chat channels fully, or inability
to whois yourself, then that is purely down to an issue, or issues, between
your client and the remote primary client, or clients, that you're trying to
communicate with. It is highly likely to have nothing whatsoever to do with
cache servers.
Are you using the DLL fix to get online, or a hosts file modification, or
both? The hosts file modification should have zero issue in respect to your
argument so long as you haven't messed it up in some way (like removing the
"127.0.0.1 localhost" line or something), though there's always the
possibility that the DLL could have outstanding issues that may cause
problems similar to what you're seeing. You have the power to run the tests
there to try and determine whether this might be the case, so do it, and
stop being so irresponsible by spreading bollocks around as if it's the
truth.
Navigation:
[Reply to this message]
|