From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_06AB_01C482C4.2D032C00
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I tested with 127.0.0.2, 127.0.0.3, and 127.0.0.4.  All worked fine.=20

Rich

  "John Beckett" 
wrote in message =
news:411f5aa0.43649144{at}216.144.1.254...
  "Rich"  wrote in message news::
  >    I have seen claims of loopback being blocked.  I'm skeptical.  =
What I
  > would understand is a spoofed loopback address (e.g. 127.x.y.z !=3D
  > 127.0.0.1).  However,  I just tried this on a Windows XP SP2 system =
and=20
  > I could both listen on and spoof from 127.0.0.x addresses.  Whatever =
the
  > behavior should be identical between the Home and Professional =
editions
  > plus other editions.

  The reports on 127.0.0.x problems in XP SP2 are very vague. I think =
the
  claim is that a program can't use 127.0.0.x (where x > 1) to open a
  connection.

  I'm not sure how an app would bind to (say) 127.0.0.2 - I suppose it =
might
  just be the normal stuff when an app specifies the IP it wants to use,
  rather than "any ip". Anyway, then the app (apparently) tries to open =
a
  connection to some other app that is listening on some other IP. =
Pretty
  strange.

  John

------=_NextPart_000_06AB_01C482C4.2D032C00
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I tested
with 127.0.0.2, =
127.0.0.3,=20
and 127.0.0.4.  All worked fine. 
 
Rich
 

  "John Beckett" <FirstnameSurname{at}com=">mailto:FirstnameSurname{at}compuserve.com.omit">FirstnameSurname{at}com=
puserve.com.omit>=20
  wrote in message news:411f5aa0.43649144{at}216.=
144.1.254..."Rich"=20
  <{at}> wrote in message  * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)

SEEN-BY: 633/267 270

@PATH: 379/45 1 396/45 106/2000 633/267