UDP/TCP app stops working when ethernet cable is connected

[Glauber]

Hello,

I'm developing a UDP/TCP app, app #1, to communicate with app #2. Everything is working fine while they use the loopback pseudo-interface (127.0.0.1) to communicate. But as soon as I connect a random ethernet cable to my ethernet card, app #2 can no longer see the packets sent by #1, even though they are still using 127.0.0.1 and not the card. Eventually they will be on different computers, so working through ethernet is a must. My firewall is off.

Are there LV ethernet/network/etc settings I should be paying attention to?

Thanks,

Glauber

[Zekasa]

Hi,

fisr of all you have to make sure that both computers on the network are seeing each other, you can do this using "ping" command from DOS.

if they do not seeing each other, and your connecting them through netwrok make sure that your using a straight Ethernet cable, if you are connecting them directly make sure that you have Cross over Ethernet cable

Hope this helps

[Glauber]

yep, they can see each other, but that's not even the point. if the apps are communicating through the pseudo-interface, whatever LAN settings should not matter right? connecting an ethernet cable should not prevent them from communicating given they were working correctly before the cable was connected.

[syang]

May I ask what version of Labview you using?