Member Avatar for Alessandrorenzi

Hi guys,
I have a VB6 exe file on pc A and I want run this exe from pc B.
Pc A and pc B are connected in internet.
Then, the running exe file in pc B has to send in real time data to pc A
Is it possible and how can I do?
Thak you in advance for your help

  • 3 Contributors
  • 2 Replies
  • 290 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by Reverend Jim

Dani AI

Generated

Short summary and practical path forward.

wants to launch a VB6 EXE on PC B and have that running instance stream data back to PC A in real time. The answers already in thread (file shares / email / remote invoke) point to workable quick fixes, but they leave out the robust, repeatable architecture and the traps (NAT/firewall, UAC, missing dependencies) you’ll hit when you want reliable, real-time streaming.

Recommended approach (robust)

  • Run the EXE on PC B and install a small “agent” or service on B that establishes an outbound, authenticated, encrypted connection to PC A (or a cloud relay). Because the agent makes an outbound connection, you avoid NAT/firewall inbound rules. The agent receives a start/stop command, spawns the EXE locally, captures its output (stdout or a dedicated IPC channel), and forwards the stream over the persistent connection. Use a socket or WebSocket for low-latency streaming and JSON/binary frames for messages.

Simpler alternatives (trade-offs)

  • Remote command tools or scheduler-based remote starts can work for occasional runs, but are brittle across NATs, UAC, and intermittent connectivity and are not good for continuous streaming. File-drop or periodic HTTP polls are simple but add latency and are not true real time.

Security, reliability, and troubleshooting

  • Use TLS and token-based auth, run the agent with least privilege, and log both sides. Ensure the EXE’s dependencies are installed on B. To debug: verify the EXE runs locally first, check firewall rules and Event Viewer, confirm the agent can make outbound connections (use netstat), and capture traffic if needed. For streaming glitches, buffer sizes and explicit flushes in the producer are common culprits.

Quick checklist

  1. Confirm you have permission to run software on PC B.
  2. Verify EXE runs locally on B and all dependencies exist.
  3. Build/deploy a small agent on B that opens an outbound TLS socket to A or a relay.
  4. Agent spawns EXE and streams its output back.
  5. Add auth, logging, and retry/heartbeat logic.

This pattern scales and handles NAT/firewall issues; it’s the usual production approach for “run remotely and stream back” scenarios.

Recommended Answers

All 2 Replies

Member Avatar for DenisOxon

Hi,

You say PC's are connected via internet, but how ? Are they connected as if in same building so you can map a drive on the other ? If so then have a mapped drive and the data can be saved to drive on relevant PC.

If not, then install program on remote PC and get it to email results to first PC, which are then extracted, as and when.

Denis

Member Avatar for Reverend Jim

If you have the appropriate rights to access the remote PC, and if that program is available through a share on that PC and if it is a stand-alone program (does not require components that are not installed on your PC then you should be able to execute the program by

\\computername\sharename\progname.exe

If the program is in a subfolder under the sharename then just add qualifiers to the path.

That's assuming you want to run the program on your computer. If you want to run it on the remote computer then you can use something like psexec to invoke it (a free sysinternals utility available from Microsoft).

Edited by Reverend Jim
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.