[quote=em99010pepe;138216]For windows I suggest you to install [URL="https://secure.logmein.com/products/free/"]LogMeIn Free[/URL] to remotely control the cores.[/quote]
Yeah, that's a good idea. I've already sent Gary some instructions for setting up VNC/SSH on his Linux machines, though due to a little mix-up on my end about what brand router he had, I'll have to rewrite some of it.

Oh, one quick thing: does LogMeIn Free require any port forwarding to be set up?

[quote=Anonymous;138228]Oh, one quick thing: does LogMeIn Free require any port forwarding to be set up?[/quote]
[URL="https://na1.salesforce.com/_ui/selfservice/pkb/PublicKnowledgeSolution/d?orgId=00D300000006VGf&lang=&id=50130000000GPzI&retURL=%2Fsol%2Fpublic%2Fsolutionbrowser.jsp%3Fcid%3D02n30000000DBsi%26orgId%3D00D300000006VGf%26lang%3D&ps=1"]https://na1.salesforce.com/_ui/selfservice/pkb/PublicKnowledgeSolution/d?orgId=00D300000006VGf&lang=&id=50130000000GPzI&retURL=%2Fsol%2Fpublic%2Fsolutionbrowser.jsp%3Fcid%3D02n30000000DBsi%26orgId%3D00D300000006VGf%26lang%3D&ps=1[/URL]
Looks like it requires ports 443 and 80 TCP on the hardware firewall and localhost port 2002 in any software firewalls (plus the firewall needs to allow the specific .exe's to access the Internet, and there's special instructions for Norton).

[quote=Mini-Geek;138232][URL]https://na1.salesforce.com/_ui/selfservice/pkb/PublicKnowledgeSolution/d?orgId=00D300000006VGf&lang=&id=50130000000GPzI&retURL=%2Fsol%2Fpublic%2Fsolutionbrowser.jsp%3Fcid%3D02n30000000DBsi%26orgId%3D00D300000006VGf%26lang%3D&ps=1[/URL]
Looks like it requires ports 443 and 80 TCP on the hardware firewall and localhost port 2002 in any software firewalls (plus the firewall needs to allow the specific .exe's to access the Internet, and there's special instructions for Norton).[/quote]
Okay, it looks like that's just a case of making sure traffic isn't [i]blocked[/i] on those ports, not port forwarding. Since Gary's just using a Belkin consumer router, that shouldn't be a problem. :smile:

I can run perl on Windows or Linux, makes no difference to me.
If you want me to process the logs automatically while I'm already processing them, and that would help out, then let's get-er-done :smile:
email me that bad boy. :)

I think you will find RealVNC a better product and been in use for zillions of years. ;)
[URL]http://www.realvnc.com/cgi-bin/download.cgi[/URL]
with source code to if you want to roll your own :smile:
Choose your poison [url]http://www.realvnc.com/products/download.html[/url]
I've always used the Free edition with no problems ever.
Only need to open port 5900 on your router and port forward it to the PC on the inside.
Using it on your LAN, you can manage all Windows/Vista boxes from one PC.
From that one PC, you can open a SSH to your Linux boxen to manage your clients.

[quote=IronBits;138255]I think you will find RealVNC a better product and been in use for zillions of years. ;)
[URL]http://www.realvnc.com/cgi-bin/download.cgi[/URL]
with source code to if you want to roll your own :smile:
Choose your poison [URL]http://www.realvnc.com/products/download.html[/URL]
I've always used the Free edition with no problems ever.
Only need to open port 5900 on your router and port forward it to the PC on the inside.
Using it on your LAN, you can manage all Windows/Vista boxes from one PC.
From that one PC, you can open a SSH to your Linux boxen to manage your clients.[/quote]
Actually, I've used TightVNC myself quite a bunch and found it to be just as good as RealVNC (in fact I think it might even be based on it), except with a few more handy features. :smile:

Specifically, here's what I was thinking of having Gary set up as an easy way to manage all of his machines without having to mess with things like configuring different ports to forward to different machines and all that shabang: simply configure all the Linux machines with SSH, but only one of them port-forwarded, and set up a user account for me on the systems, then I would SSH in and configure the VNC. Once it's all set up, Gary would then connect to the Internet-facing machine through SSH, and use an SSH tunnel to VNC into each of the machines, thus using the one Linux machine as a secure jumping-off point to access all the others.

For the Windows machines, VNC would also work (and since all of Gary's machines are on the same local subnet, the Linux jumping-off machine would still work great for this), though I was also considering the possibility of using LogMeIn Free on the Windows machines since that doesn't require any port forwarding whatsoever. Of course, since the jumping-off-machine setup would only require one forwarded port (SSH on the jumping-off machine), anyway, that might be somewhat of a moot point.

I'm thinking that maybe with a nice little Perl script that would take care of all the long strings of commands required to open tunnels within SSH connections, such a method could be quite secure and user-friendly. :smile:

Anon :smile:

You're making it way to complicated.
On his router, forward port 5900 to his main windows box (IPaddy)
Then install VNC Server (with strong password) on that computer.
From that familiar windows box, he can ssh to any linux box or VNC to any other windows box.
Done. His linux boxen should already have ssh installed and working, just need to edit /etc/sudoers ;)
Make sure you give install PuTTY for him on his windows box, it's really a nice dos interface terminal with pretty vga colors. ;)

All that other stuff is overkill mainly because there is only one way inside his network, on port 5900 to his Windows PC using VNC server.
I've been doing it for many many years and managed many many pharms, some large, some small this way.
He can also read all his mail on his PC while he's there, he'll feel right at home.
As to automating his clients on the Linux boxen, that's really easy.
I posted a section on how to set it up in Linux, then just run ./clients-nplb and off it goes, then we could put that into the init.d startup folder and it will always restart if the computers are rebooted for any reason, and he can monitor them.
You could also easily setup Samba for inside WAN only connections so he can map Windows Drive letters to each Server where the clients are located and keep an eye on the results files etc.
Keep it simple and he'll catch on quick. :smile:

Oops, yes, he can forward port 5900 to a linux box so you can get them setup first, then he can point it back to his Windows box. ;)
I have managed 32 crunchers on my personal lan all using VNC Server on each one, and VNC Viewer to get to any one of the headless boxes.
I have managed 40 crunchers on my brother's personal lan by VNCing to one Windows box, then getting at all the others.
And, while he is at home, he can disable the port 5900 forwarding in his router offering even more security, and only enabling it for when he's going to be gone for days at a time. ;)

I must admit I feel rather blessed having everyone talk about how to configure MY systems. lol

Just got back, unpacked, and running laundry now. First day back is always busy so I'll be busy most of Thursday also.

Anon, perhaps we can link up on Google chat or something sometime this weekend and get this remote access thing set up.


Gary

Gary,

I am on port 400 with 4 cores, can't add the work machine because port 400 is blocked. When we reach 505k I'll switch to port 300 to help us go up to 510k.

Carlos

[quote=em99010pepe;138277]Gary,

I am on port 400 with 4 cores, can't add the work machine because port 400 is blocked. When we reach 505k I'll switch to port 300 to help us go up to 510k.

Carlos[/quote]


Thanks for helping Carlos.

[quote=IronBits;138264]You're making it way to complicated.
On his router, forward port 5900 to his main windows box (IPaddy)
Then install VNC Server (with strong password) on that computer.
From that familiar windows box, he can ssh to any linux box or VNC to any other windows box.
Done. His linux boxen should already have ssh installed and working, just need to edit /etc/sudoers ;)
Make sure you give install PuTTY for him on his windows box, it's really a nice dos interface terminal with pretty vga colors. ;)

All that other stuff is overkill mainly because there is only one way inside his network, on port 5900 to his Windows PC using VNC server.
I've been doing it for many many years and managed many many pharms, some large, some small this way.
He can also read all his mail on his PC while he's there, he'll feel right at home.
As to automating his clients on the Linux boxen, that's really easy.
I posted a section on how to set it up in Linux, then just run ./clients-nplb and off it goes, then we could put that into the init.d startup folder and it will always restart if the computers are rebooted for any reason, and he can monitor them.
You could also easily setup Samba for inside WAN only connections so he can map Windows Drive letters to each Server where the clients are located and keep an eye on the results files etc.
Keep it simple and he'll catch on quick. :smile:

Oops, yes, he can forward port 5900 to a linux box so you can get them setup first, then he can point it back to his Windows box. ;)
I have managed 32 crunchers on my personal lan all using VNC Server on each one, and VNC Viewer to get to any one of the headless boxes.
I have managed 40 crunchers on my brother's personal lan by VNCing to one Windows box, then getting at all the others.
And, while he is at home, he can disable the port 5900 forwarding in his router offering even more security, and only enabling it for when he's going to be gone for days at a time. ;)[/quote]
The reason why I was thinking of bouncing it through SSH at the entry point instead of VNC, is primarily because it makes everything secure, even the VNC connections which are originally unencrypted. Long story short, I was hoping that my method would allow Gary to connect to any and all of his machines, Linux or Windows, and get full graphical remote control (you're right, VNC probably would be better for the Windows machines than LogMeIn Free, since that way he can access all the machines the same way). That way he can interact with any of his machines as if he was sitting in front of them, except of course for the slight lag that always happens when you VNC over the internet. :smile:

Gary, sorry if this feels like we're all talking [i]about[/i] you in front of your nose--trust me, it should be a lot simpler than this on your end. :smile: As you suggested, we should probably get together on Google Talk sometime soon and discuss setting it up.

(P.S.: IronBits, actually I don't think Gary's machines will have the SSH [i]server[/i] already up and running, since they're Ubuntu machines and on non-server Ubuntu installations, only the SSH client is installed by default. However, it's only a simple matter of "sudo apt-get install openssh-server" to get it going. :smile:)