Localhost IP Addresses Other Than 127.0.0.1

[Jeff S.]

We are developing an application in C# that runs on a PC and communicates
with a piece of equipment via the ethernet. For testing we have developed a
simulation of the equipment that we want to run on the same PC as the
application. We assigned the address 127.168.8.225 to the application and
127.168.8.129 to the simulation (both represent localhost). Under Windows
2000 this worked fine but when we upgraded to Windows XP it stopped working.
A possible clue is that on 2000 if I ping 127.168.8.225 the reply is from
127.168.8.225 but on XP the reply is from 127.0.0.1. Is this a change in XP
and does anyone know of a workaround.?
--
Jeff S.

[Wessel Troost]

> application. We assigned the address 127.168.8.225 to the application

and
127.168.8.129 to the simulation (both represent localhost). Under

Assuming only one of them is listening on a socket, both the client and
server can use the same IP address. Try 127.0.0.1 for both?

Greetings,
Wessel

[Chad Z. Hower aka Kudzu]

"=?Utf-8?B?SmVmZiBTLg==?=" <se*******@noemail.nospam> wrote in
news:54**********************************@microsof t.com:

to Windows XP it stopped working. A possible clue is that on 2000 if
I ping 127.168.8.225 the reply is from 127.168.8.225 but on XP the
reply is from 127.0.0.1. Is this a change in XP and does anyone know
of a workaround.?

Ping is not a reliable way to check what you seek.

Are you explicitly binding your server to an address? Also you should not use the 127.x block for
IP's, use 192.168.0.x or one of the other reserved LAN blocks.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Get your ASP.NET in gear with IntraWeb!
http://www.atozed.com/IntraWeb/

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

IT should not be any problem really

I assume that you are binding each app to only one of the IPs ( You can usi
a IPEndPoint instance for this)

Do you know if you the service is listening? doing a telnet to that port?

what if you set different ports ? can you connect then?
cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation


"Jeff S." <se*******@noemail.nospam> wrote in message
news:54**********************************@microsof t.com...

We are developing an application in C# that runs on a PC and communicates
with a piece of equipment via the ethernet. For testing we have developed
a
simulation of the equipment that we want to run on the same PC as the
application. We assigned the address 127.168.8.225 to the application and
127.168.8.129 to the simulation (both represent localhost). Under Windows
2000 this worked fine but when we upgraded to Windows XP it stopped
working.
A possible clue is that on 2000 if I ping 127.168.8.225 the reply is from
127.168.8.225 but on XP the reply is from 127.0.0.1. Is this a change in
XP
and does anyone know of a workaround.?
--
Jeff S.

[Chad Z. Hower aka Kudzu]

"=?Utf-8?B?SmVmZiBTLg==?=" <se*******@noemail.nospam> wrote in
news:54**********************************@microsof t.com:

to Windows XP it stopped working. A possible clue is that on 2000 if
I ping 127.168.8.225 the reply is from 127.168.8.225 but on XP the
reply is from 127.0.0.1. Is this a change in XP and does anyone know
of a workaround.?

Ping is not a reliable way to check what you seek.

Are you explicitly binding your server to an address? Also you should not use the 127.x block for
IP's, use 192.168.0.x or one of the other reserved LAN blocks.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Get your ASP.NET in gear with IntraWeb!
http://www.atozed.com/IntraWeb/

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

IT should not be any problem really

I assume that you are binding each app to only one of the IPs ( You can usi
a IPEndPoint instance for this)

Do you know if you the service is listening? doing a telnet to that port?

what if you set different ports ? can you connect then?
cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation


"Jeff S." <se*******@noemail.nospam> wrote in message
news:54**********************************@microsof t.com...

We are developing an application in C# that runs on a PC and communicates
with a piece of equipment via the ethernet. For testing we have developed
a
simulation of the equipment that we want to run on the same PC as the
application. We assigned the address 127.168.8.225 to the application and
127.168.8.129 to the simulation (both represent localhost). Under Windows
2000 this worked fine but when we upgraded to Windows XP it stopped
working.
A possible clue is that on 2000 if I ping 127.168.8.225 the reply is from
127.168.8.225 but on XP the reply is from 127.0.0.1. Is this a change in
XP
and does anyone know of a workaround.?
--
Jeff S.

[Jürgen Friedrich]

Hi Jeff,

Windows XP SP2 pervents connections to local loopback adresses other than
127.0.0.1. There is a download at
http://support.microsoft.com/default...b;en-us;884020 that resolves
this problem.

Jürgen
"Jeff S." wrote:

We are developing an application in C# that runs on a PC and communicates
with a piece of equipment via the ethernet. For testing we have developed a
simulation of the equipment that we want to run on the same PC as the
application. We assigned the address 127.168.8.225 to the application and
127.168.8.129 to the simulation (both represent localhost). Under Windows
2000 this worked fine but when we upgraded to Windows XP it stopped working.
A possible clue is that on 2000 if I ping 127.168.8.225 the reply is from
127.168.8.225 but on XP the reply is from 127.0.0.1. Is this a change in XP
and does anyone know of a workaround.?
--
Jeff S.