PC to PC Communication using LabView

[RavensFan]

Check to make sure the port is not being blocked by a PC's firewall or by a firewall within  your network.

[GuenterMueller]

---

MikeMSD wrote:[...]  OR, is it possible that these VI can't work across a network?

---

They definitely do.  Should be a firewall issue. Provided, you made no typo in the ip addresses or ports.

[MikeMSD]

I used IPCONFIG to verify the IP of the computers.

Well, I've turned the firewall completely off on the PC, for testing and I have no anti-virus software right now, because this is a test computer,which typically has no internet access.

Should these VI work, simply by replacing the localhost with the server computer IP?

[GuenterMueller]

Specify the ipaddress of the PC that runs the "Simple Data Server" in the "Simple Data Client".  Then, the client should connect to the server.

[MikeMSD]

  That's what I said I did, on page 1.   It's just not connecting, for some reason.   I even tested a known good cable, just to make sure it wasn't a cable issue.  I've also tried other ports to see if I can find one that might work. 😉  But there are a lot of ports. 

There must be something simple I'm missing here.  But I'll figure it out, if there are no more suggestions.

I wonder.  After I installed the runtime engine, I just assumed it would be accessed when I ran the VI executable.   I didn't specifically run the engine.  I'm assuming that since there are no errors on trying to run the VI that nothing special was needed to get the runtime engine into this equation.  Right?

[GuenterMueller]

---

@MikeMSD wrote:

  That's what I said I did, on page 1.   [...]

There must be something simple I'm missing here.  But I'll figure it out, if there are no more suggestions.

---

Right, I now recognised it in your post.   You are right in expecting a simple issue that might be missing because TCP isn't that complicated:  Specifying an ipaddress and a port should do ...    Can you confirm that you can "ping" your PCs?  If not, that would be "the simple thing".

[MikeMSD]

Interesting, my client computer cannot ping the server computer. 

However, my server can ping my client computer.

I guess that's why I can't connect.  I ran the command IPCONFIG, and used the ethernet IP reported.  Shouldn't CONFIG report the IP of the server computer, when I run that on the server computer? 

I'm obviously not an IT guy so this IP stuff is kind of Duh!  All my other ethernet connections are from PC to device.  This is a PC to PC.  I don't need any kind of cross-over or something to go from PC to PC do I?  I thinking not, since I can ping one direction but not the other. 

[GuenterMueller]

---

@MikeMSD wrote:

Interesting, my client computer cannot ping the server computer. 

However, my server can ping my client computer.

I guess that's why I can't connect.  I ran the command IPCONFIG, and used the ethernet IP reported.  Shouldn't CONFIG report the IP of the server computer, when I run that on the server computer?  pinpin

---

Yes, it should: ipconfig should give you the details of each networking interface card of that PC.

To verify that your client can reach the server run (ipaddress taken from your previous post) at a command prompt

ping 10.178.76.138

[MikeMSD]

I did that.  

When I PING 10.178.76.138, from the client to the server, I get timeouts.

When I PING 10.178.76.100, from the server side to the client, I get reports back.

This does make it look like there is something blocking those on my server computer.  However, I have turned the firewall completely off and there is nothing else I can see that would cause the issue.  I'll look around some more.

 TADA.  It's working.  I went back to the firewall settings and there was two settings.  One for public and one for private.   I turned everything off and now it works.

Thanks very much for walking me through this... everyone who helped.

Mike

[GuenterMueller]

Congrats.