Programming from home to the lab?

Click For Summary

Discussion Overview

The discussion revolves around the challenges and potential solutions for programming from home to a lab environment, specifically focusing on accessing and running applications remotely on a lab computer. The context includes considerations of hardware limitations, software tools, and network configurations.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant inquires about the feasibility of logging into a lab machine from home to run a Windows application, given hardware limitations at home.
  • Suggestions include using Remote Desktop or VNC, with a note that firewall settings may require port adjustments.
  • Another participant mentions the possibility of using Bloodshed's Dev-C++ for C/C++ programming, emphasizing its open-source nature.
  • Concerns are raised about the practicality of VNC due to potential restrictions on running servers on the lab computer.
  • A low-tech alternative is proposed, involving connecting a modem to the lab computer and using a phone line for access, though its effectiveness is uncertain.
  • One participant humorously suggests using a long ethernet cable to connect the two computers directly.
  • Another participant expresses intent to try Remote Desktop, noting the need to test hardware-related code in the lab.
  • Discussion includes the possibility of running an SSH server for application forwarding, with some uncertainty about its capability to handle Windows applications without VNC.
  • There is a mention of using Cygwin's SSHD for SSH access and file transfer, along with VNC, through a single open port.
  • Questions arise about the ability of Cygwin's SSHD to forward Windows applications without VNC, with a participant stating that they use VNC through SSH for remote desktop access.
  • One participant suggests rewriting the application to use X11 as an alternative approach.
  • A link to a remote access service is shared as a potential solution.

Areas of Agreement / Disagreement

Participants express a variety of approaches and tools for remote programming, with no consensus on the best method. Several competing views and suggestions remain unresolved.

Contextual Notes

Limitations include potential firewall restrictions, the need for specific software configurations, and the uncertainty of the effectiveness of low-tech solutions like modem access.

nbo10
Messages
416
Reaction score
5
programming from home to the lab?

Hi all,
I'm using microsoft studio to develop a few programs that I use in lab to run various experiments. I want to write the programs at home, but I don't have the hardware on my home pc. I'm using XP, and wonder if there is a way I can log into a machine in my lab, copy the app to that computer and then run the app. It's a window app with a gui so I can't just telnet. I ahve broadband on both computers so bandwidth isn't a problem. Any Ideas?? Thanks

JMD
 
Technology news on Phys.org
  • Remote Desktop (assuming the lab pc runs Win XP)
  • VNC (possibly using SSH tunneling)
If the lab pc is behind a firewall, you might have to open some ports.
 
What programming language are you specifically using. If it is C/C++ you should just get a copy of Bloodshed's Dev-C++. It's opensource software, therefore it is free it use.

The likelyhood of doing VNC is almost silm to none. You'll need to run a server all day on the lab computer and most likely they've locked down the services that can run.
 
If the lab pc's ports are blocked by a firewall, you might try this low-tech approach.
Connect a lab phone-line to a modem on the lab-computer and call it from home. I'm not clear on how networking will work via modem... but I would think it should work. Remote Desktop or VNC will probably be sluggish, but it might be okay if you are patient and do not require a crisp desktop image. It may help to reduce the resolution and color-depth of the lab pc.

Maybe aspects of the development (which do not require the lab pc's hardware) can be done at home. Then, transfer the program to the lab pc. Then, use Remote Desktop or VNC to execute the program.
 
That's real practical. Why doesn't he just get a really long ethernet cable and hook the two computers up directly
 
I'm going to give the remote desktop a try. I can do most of the programming at home but at some point I need to make sure the code for the hardware works, I just don't want to have to spend more countless hours in lab than I have too.

JMD
 
Any chance he could run an SSH server and do some sort of forwarding? I know OpenSSH only supports X11 applications, but a more propiertary SSH might support forwarding graphical Win32 applications.
 
Last edited:
graphic7 said:
Any chance he could run an SSH server and do some sort of forwarding? I know OpenSSH only supports X11 applications, but a more propiertary SSH might support forwarding graphical Win32 applications.

I use cygwin's sshd. Using the PuTTY client, I get ssh access, scp file transfer, and forwarding of VNC and X... all through one open port.


Concerning modem-access to an office computer, my advisor used that technique since he didn't have broadband at home and the university dial-up lines were time-limited.
 
Can a Cygwin SSHD forward Windows applications (without the use of VNC), though?
 
  • #10
graphic7 said:
Can a Cygwin SSHD forward Windows applications (without the use of VNC), though?

Not that I know of.
I use VNC through SSH to access my remote Windows desktop.
 
  • #11
Ah, that's what I was thinking.

He could always rewrite his application to use X11 instead. :frown:
 

Similar threads

  • · Replies 7 ·
Replies
7
Views
5K
  • · Replies 16 ·
Replies
16
Views
3K
  • · Replies 6 ·
Replies
6
Views
4K
Replies
1
Views
2K
  • Sticky
  • · Replies 13 ·
Replies
13
Views
9K
  • · Replies 13 ·
Replies
13
Views
7K
Replies
81
Views
12K
  • · Replies 9 ·
Replies
9
Views
2K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 18 ·
Replies
18
Views
5K