Thanks for all the help fellas.
I've followed suggestions, and reached another snag.
In case this is relevant to my problem, I'm trying to access a Windows
server running freesshd, from a remote Mac running latest Leopard.
After I run JellyfiSSH, I launch MS RDC for Mac, and after spinning
its wheels for a while RDC returns the message "The Mac cannot connect
to the Windows-based computer" followed by a few suggestions about the
Windows server possibly not being set up to accept remote connections,
the Windows server is not on, or the Mac or Windows machine is
experiencing network problems.
The first two suggestions aren't valid because a Windows user has
confirmed his remote access is working fine when I couldn't. So I
suspect it is something I have wrong in JellyfiSSH.
The Windows IT guy I've been speaking with, who can access the Windows
server remotely but isn't familiar with the MacOS, gave me the detail
of what to enter into JellyfiSSH after I sent him some screenshots. He
suspects my access problem may have something to with JellyfiSSH being
a UNIX focussed tool, but just guessing. He wasn't sure of what option
to choose for the field "Shell'. The options are bin/bash, /bin/csh, /
bin/sh, /bin/tcsh, or /bin/zsh. We went for the first one. So there's
my first question - anyone know which Shell option I should choose?
The "Type" option appears to have two settings. The first selection he
was sure about, and that was SSH 2. The second setting he wasn't sure
about. The options are des, 3des, blowfish, 3des-cbc, blowfish-cbc,
cast128-cbc, arcfour, aes256-cbc. We ran with aes256-cbc. Second
question - anyone know for sure which option?
Hopefully I can avoid having to try 40 different combinations of Shell
setting and the Type setting.
Something else that may provide a clue.
When I click Connect on JellyfiSSH, a Terminal window appears asking
for my password. I enter the passord, and the cursor drops to the next
line, and presumably the password has been accepted, though there is
no confirmation of that. I then click Connect on RDC, but what happens
then is that in the Terminal window the following appears ...
client_input_channel_req: unexpected channel -1
Any hints most welcome.
Cheers, Steven
On 19/04/2009, at 8:13 AM, Stuart Evans wrote:
Hi Steven,
Microsoft Remote Desktop Client for Mac will remotely connect to any
windows
computer with remote control services enabled. Windows servers run
Terminal
Server services that enable you to connect remotely. All you need to
know is
the remote clients IP Address (eg 202.43.45.72), or if it has a DNS
host
name then via it's hostname (myserver.mydomain.com.au). You don't
need SSH
unless the remote site has set this up for security reasons. The
other issue
you might have is if the site redirects RDP traffic. RDP traffic
uses TCP
Port 3389 and because it is an easy way to get onto a server, we
always use
a different port and redirect it to 3389. These are details you
should be
able to get from your host company. (ie IP address, port number, and
user
details to login)
Also go to the RDP preferences before you connect. There are a
number of
useful items such as the login (username/password/domain), screen
resolution
(set to lower if your link is slow), sound (turn off!), printers and
even if
your drives are accessible when you connect (useful for copying
files). Some
of these may be blocked by security on the server. Once you have your
settings you can save this for future use. Do Save As...
If you do need SSH client - try this one
http://www.grepsoft.net/jellyfissh.html
Regards,
Stuart
On 18/04/09 5:00 AM, "WAMUG Mailing List" <wamug@wamug.org.au> wrote:
Subject: Re: Apple Remote Desktop alternative ?
Date: Fri, 17 Apr 2009 10:46:59 +0400
References: <list-468...@wamug.org.au> <list-468...@wamug.org.au>
X-Mailer: Apple Mail (2.930.3)
Thanks Rob.
I installed RDC, and the first thing that comes up when I launch the
application is a request for the name of a computer (giving examples
MyPC, name.microsoft.com, IP number).
Upon asking the question of a windows user what I might put in here,
the answer was "You can't connect until you succesfully make an SSH
tunnel connection".
What bit of software or what procedure do I need follow on a Mac to
"make an SSH tunnel connection" ?
Cheers, Steven
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>
