There are lots of ways to achieve this in Labview and each one has different benefits:-
A clearer objective of the requirement will assist in choosing the optimum route.
In principle the answer is as follows: -
1) Under Windows 2K for example, you could could write the results on the remote P.C via a local Labview application to a flat text file formated as an XML prepared HTML file then use the WEB server in Windows 2K to distribute the results.
i) This promotes seperation between data provision and retrieval.
ii) Is simple to implement using text files.
iii) Is Low cost because you don't need anything but time.
iv) As it uses the web port 80 it does not give security issues on a network.
Pick-up the results from the remote machine using a second application to read the HTTP port (80). In fact you can test this using the TELNET program in Windows 2K and often in UNIX and there are loads of code / examples on mini-TELENT around for implementation and testing.
2) Write a fully fledged Client Server TCP/IP application under Labview.
See 'Data Client' example in Labview.
i) You have a work-up to understand this.
ii) It's pretty specific and tricky to test.
iii) It is a Labview only solution.
iv) You could have security issues on a well managed larger network if you use non-standard TCP/IP ports. You can forget it through a firewall if you don't get it right.
This is the help text on the appropriate example
Data Client.vi displays data sent via TCP from Data Server. Once a TCP connection is open, the VI reads 4 bytes to determine the amount of data being sent. It then reads and charts that many bytes.
If all this network talk is 'Greek' then you need to start learning about networks and protocols... and this is not the right place for that discussion.