Hey Eddie, The group voted last night to have an outside agency help with processing old claims. As a result, they are going to need to have access to our SequelMed system.
I you understand Window's remote desktop and want to come up with a solution with that technology, that's fine. But in the meantime, I want to set up a remote desktop system with tightVNCserver. What I would like you to do is this: 1. Ask Bob what computer(s) will be dedicated to these remote users. Unfortunately Windows will support only one desktop at a time, so it can't be a behind-the-scenes user (like Linux supports). So there will need to be one dedicated Windows computer for each remote user. Get the IP address of this/these computers(s). 2. On that computer, log in as administrator, and install tightVNC server. You can get it from here: http://www.tightvnc.com/ Make sure that the tightVNC server is setup so that it automatically runs upon startup from the non-administrator account. This should mean putting a shortcut for it in the startup menu folder for the standard user. 3. To allow secure connection to this tightVNC server from the internet, I plan on using ssh tunneling. Here is how it works. Remote user uses PuTTY to create a SSH connection to my linux server. PuTTY session creates an IP tunnel. The specifications for this tunnel are set up in PuTTY. You say something like, "All IP traffice being sent to the localhost with ___ port number will be captured and transported to the remote server. From the server, take all such packets and send them to _______ IP address with _____ port number. After a secure log-in, the SSH server on my linux box honors these requests and sends the packet whereever requested in our internal network. In the PuTTY configuration window, look for SSH->Tunnels. In the Source Port field, you would put 5900. That is the default port # that VNCServer runs on. In the Destination field, you would put something like this: 192.168.0.150:5900, which would specify the IP address of the dedicated Windows computer, and specify to keep the port number at 5900, I am telling you this as background information. I don't need you to do this right now. I am going to test connecting to the dedicated Windows machines, and I will do this PuTTY configuration on my end. 4. I would like you to make a new user on the Linux server, for the remote user to establish a SSH connection. Lets call the user: r3m0t3vncus3r, and have the password to be: B1ll1ng Give me a call if I haven't explained this well enough, or when you get this set up. Thanks so much. Kevin ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
