C
Chad Amberg
We have several applications that bind to ports using the
127.0.0.2 address. This is so that they are not
available outside the system it is ran on, and also there
is no chance of interfering with any apps running on the
normal system. Under SP1, 2000, even back to Windows 95,
this works just fine.
However, under XPSP2, the application can bind the ports,
but we can not connect to them at all. Everything just
times out. For example, we will have a POP3 listener on
127.0.0.2 port 110, but anything trying to connect to
that will just time out.
This did not happen with the release candidates or the
betas. Suddenly this doesn't work on the RTM version and
we're just about out of luck when SP2 gets installed on
workstations.
Can anyone tell us why this change was made, and more
importantly, was it a screw up that this happens and it
will be fixed, or will it stay this way?
127.0.0.2 address. This is so that they are not
available outside the system it is ran on, and also there
is no chance of interfering with any apps running on the
normal system. Under SP1, 2000, even back to Windows 95,
this works just fine.
However, under XPSP2, the application can bind the ports,
but we can not connect to them at all. Everything just
times out. For example, we will have a POP3 listener on
127.0.0.2 port 110, but anything trying to connect to
that will just time out.
This did not happen with the release candidates or the
betas. Suddenly this doesn't work on the RTM version and
we're just about out of luck when SP2 gets installed on
workstations.
Can anyone tell us why this change was made, and more
importantly, was it a screw up that this happens and it
will be fixed, or will it stay this way?