XP SP2 Problem

[chad]

An issue with the general release (Not the release candidate!)
If you ping 127.0.0.2 on SP1 and older, you get a response from
127.0.0.2. Which is the way it should work. Especially when you have
applications that bind to the 127.0.0.2 address.
SP2 breaks this, by having 127.0.0.1 respond. Which means that
applications written to bind to the 127.0.0.2 address don't work
anymore. Because they will never get any connections from the system.

U:\>ping 127.0.0.2

Pinging 127.0.0.2 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Can't think of ANY reason for this to happen and doesn't bode well for
application compatability.

 

[Randy Harris]

An issue with the general release (Not the release candidate!)
If you ping 127.0.0.2 on SP1 and older, you get a response from
127.0.0.2. Which is the way it should work. Especially when you have
applications that bind to the 127.0.0.2 address.
SP2 breaks this, by having 127.0.0.1 respond. Which means that
applications written to bind to the 127.0.0.2 address don't work
anymore. Because they will never get any connections from the system.

U:\>ping 127.0.0.2

Pinging 127.0.0.2 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Can't think of ANY reason for this to happen and doesn't bode well for
application compatability.

Not on my system, running SP1:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\>ping 127.0.0.2

Pinging 127.0.0.2 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

D:\>

 

[R. McCarty]

Ping 172.0.0.2 receives Reply from 127.0.0.1, running 2180

^Snip^

 

[Ron AG]

Have SP1, 127.0.0.2 receives replies from 127.0.0.1 however

 

[Ron AG]

Have SP1, 127.0.0.2 replies from 127.0.0.1 however

 

[chad]

Have SP1, 127.0.0.2 replies from 127.0.0.1 however

Actually, you all are right, I was using Win2k to test against while
trying to figure out what was wrong.
However, the problem remains. With the firewall completely off,
nothing I have bind to a 127.0.0.2 address is reachable at all.
Everything times out. I should be able to telnet in to the ports and
just can't reach them.

 

[OP]

Chad,

Any update on this issue? This causing me also lot of
problems and wonder if there is any solution/workaround
for that...

 

[chad]

Chad,

Any update on this issue? This causing me also lot of
problems and wonder if there is any solution/workaround
for that...

Not yet. I've posted in the official microsoft boards, etc. Short of
wasting my money on a support call, I'm not sure we will get an answer
quickly.
This wouldn't be so bad if they weren't releasing SP2 on windowsupdate
as an automatic install. That they are doing it that way, is going to
screw up untold numbers of systems. Lots of small software vendors
are getting royally bent over on this one!

 

[chad]

Chad,

Any update on this issue? This causing me also lot of
problems and wonder if there is any solution/workaround
for that...

Found another post:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&[email protected]
It seems Canon print drivers are failing because of this same issue.
Lets hope they can get an answer out soon!

 

[Randy Harris]

You guys have probably already seen this, but in case not, here is a
Microsoft hotfix for this problem:

http://support.microsoft.com/default.aspx?scid=kb;[LN];884020

HTH,
Randy

 

[Microe]

I linked to Microsoft for the Hotfix only to learn that you have to call
in and may have to pay for the fix. Does anyone know what the fix
actually does?