-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That about sums up what I experienced. And no, I'm quite sure Gnapster
normally does something unconventional since some of my other clients still
work!
Michel
On Monday 15 January 2001 04:59, you wrote:
> ** Reply to message from "John J. LeMay Jr." <[EMAIL PROTECTED]> on Sun, 14
> Jan 2001 23:32:48 -0500
>
> Well, this is interesting. On my first try I was not able to negotiate with
> the server and my connection was closed. After receiving the PSH from
> c2.napster.com with an address to try, 64.124.41.158 on port 8888, Gnapster
> correctly attempted to connect. Upon attempting this connection, I received
> a RST immediately following the handshake.
>
> My second attempt was a bit more sucessful. I rec'd a different address
> from c2, 208.184.216.21. I sucessfully connected to this host, logged in,
> received the MOTD info, and then immediately rec'd a RST from the host.
> Gnapster never displayed the MOTD and I was not able to determine from
> Gnapster's interface if I had been logged on.
>
> Definitely looks like something changed somewhere with Napster, however I'm
> not sure Gnapster is all that innocent here. I would post the trace, but
> I'm not sure if anyone else is interested. Besides, I don't feel like
> filtering out my id and password! ;)
>
> John LeMay Jr.
> Senior Enterprise Consultant
> NJMC, LLC.
>
>
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New! Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
- --
Cleanliness is next to impossible.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjplVHUACgkQJGJajIpyEn6P+QCfcweu6hGLKyf56RcE7c5eNdCY
rKwAniBGAAJEeNq4hp81CsCW8pebVXjq
=q3yV
-----END PGP SIGNATURE-----
