For those of you who like the Idokorro version of the telnet/ssh products (some would argue this one is the best, but I'll let you be the judge...) MobileSSH Version 2.1 is now out! This can be downloaded wirelessly over-the-air via entering "www.idokorro.com" inside your BlackBerry Browser. Or by going to MobileSSH download page if you prefer to install via BlackBerry Desktop.

If you already have MobileSSH installed, this becomes an upgrade instead of a trial. Also, you may need to uninstall your 2.0 from BlackBerry->Options->Applications before installing 2.1 wirelessly. (Your settings will not be lost if you were previously using Version 2.0)

New and improved features for 2.1 include...
- IBM 3270 Terminal Emulation
- SSH 2 public key authentication
- Improved SSH connection speed
- Session import/export functionality
- User definable shortcut keys
- Improved VT100/TN5250 support

Previously improved features for 2.0 include:
- IBM 5250 Terminal Emulation
- SSH 1 support (in addition to SSH 2 support)
- ANSI color code support for VT100 sessions
- Huge performance improvements
- Improved performance in local input mode / Telnet local echo support
- Improved VT100 rendering
- Improved font selection, allowing you to choose your favorite BlackBerry font
- Option to disable splash screen
- Option to auto-hide local input buffer (except for 7100 series devices)
- SureType support for 7100 series devices
- Improved symbols and special keys screens
- ALT + and CTRL+ALT + support (in addition to CTRL + support)
- Shortcut keys for common screens / CTRL+ / ALT+
- User Interface improvements
- Option to choose connection method (TCP/IP stack or BES/MDS) from within the application

I recently upgraded to thie new 2.1 version. For some reason I am having some problems with the the wheel moving the cursor. In the version 2, I was able to use vi to edit file and what not. Now while in vi (with local scrolling disable) I am unable to move the cursor up, down, left or right. What is funny is that while at the bash prompt, I can scroll up to get the bash history. It seem like the up, down, left, right arrow keys do not work while in a program. Any suggestions?

Did you toggle the "VT100 Cursor Codes" checkbox? This may have gotten set/cleared. They use different cursor codes. Let me know if this works for you.

Wow that was quick! I did try that, but it also does not seem to work. There is something in the config that is diffrent between the 2.0 and 2.1. I had this same problem in version prior to 2.

Strange. I will debug this tomorrow with the MobileSSH programmer.

Also, did you change your connection method? telnet versus ssh? Try the original connection method too.

If you are an experienced UNIX user, type "cat", hit Enter, and try using the wheel. Please type out the output in your next message. It should look something like "^[[A^[[B^[[B^[[A^[[C^[[D" .... (Once your done, you can send a Ctrl-C or simply disconnect)

I am going to bed soon, but I'll be watching this thread and sending a link to the MobileSSH programmer. We take these things seriously.

Wow. I am impressed with your responsivness! Thanks Mark! I cant telnet cause it is disabled. I am ssh'ing into a linux box (fedora core 3). As for the cat'ed output:

EDITED; I accidentally reversed the '[' for the down and shift down.

scrolling down gives: ^[[B
scrolling up give: ^[[A
scrolling shift down gives: ^[[C
scrolling shift up gives: ^[[D

but .. if i do vi .bash_profile and *try* to move the cursor around (it does not move on the screen) in there then exit and cat the cursor output:

scrolling down gives: ^[OB
scrolling up give: ^[OA
scrolling shift down gives: ^[OC
scrolling shift up gives: ^[OD

weird.

Oh, and if it helps I have a 7520 on the nextel network

Just wondered if you got Dan's email message. We have a new version for you to try out. He says this issue has now been fixed.

[Edit: I think they have now put this new version up on the main www.idokorro.com via BlackBerry Browser for OTA wireless download -- Version 2.1.19]

Cool. I will try the OTA out. I did not get any email from Dan.

AWESOME! It work again! Thanks for you help guys!

BTW - OTA is now at Version 2.1.20

Ok this program not cought my attention now that it supports 3270. I tried this program for the first time and telnet works very well, impressive.

BUT 3270 has problems

- No PA1 and PA2 keys OR Reset (one of the most important keys)
- Problem with some emulation, I was able to get to splash 3270 screen but could not get to the mail TSO menu.
- I getting error "Unsupported Function" at time.

Can not report any more since I can not get to the main menu.

Another problem is that I have I am almost through all of my connections trying to test 3270 connections. I would like to try different mods to see how it supports it.

Vinnie

These problem have been received by Idokorro Technical Support and we are diagnosing and fixing them as we speak. This thread will be notified when a patch is available.

For faster support responses please email Idokorro Technical Support directly at (which is what vinniet did)

A new build of Mobile SSH (version 2.1.21) which added the PA1, PA2, PA3 and System Request keys on the “Special Keys” screen is now available.

It can be downloaded from the same locations mentioned in the first message in this thread.

He says the email bounced -- I think we may have the wrong email address. Either way, glad this issue has been fixed and it is working for you!

Can you download the software again and tell me if 3270 is working better for you? Thanks!

I am new to the forum and a new 7250 user over VZW. We have BES running (4.0), a new installation in the last couple months. We also run three iSeries servers in house, which I want to have access to via the Blackberry. I downloaded (OTA) the Idokorro client and was able to easily connect via TCP/IP. However, I cannot get it to connect via the MDS connection. We are planning on blocking all external access to these boxes soon and switch to VPN for all access. I can find little documentation about making the necessary adjustments on either the handheld or the BES to allow the connection. Lastly, the connection is failing with the error on the emulation screen being: *** Disconnected: Socket closed

Any help would be appreciated. We haven't made a purchase decision on this software yet, pending me working this issue out.

Hello Joe1004,

The latest version of Mobile SSH (2.2) will automatically detect whether or not the MDS is enabled on your handheld and will default to a TCP/IP connection if it is not currently working.

Normally when the MDS is enabled for your BlackBerry an icon named "BlackBerry Browser" will appear (though it can be renamed by the BES Administrator). The icon should look like a globe with a building behind it on a 7250 no matter wht it's name is. The BlackBerry Browser is a web browser that works through your MDS and is a good test to see if your MDS is working properly or not. Are you able to use the BlackBerry Browser to connect to internal and external web sites?

If you do not see a "BlackBerry Browser" icon or if you receive errors when trying to use it then you should double check the following on your BES:
- The MDS is enabled and started
- The MDS is enabled for your user
- The 'Allow other Browser Services' IT Policy is enabled (this is not needed for enabling the MDS but is needed by Mobile SSH)

If all of those have been done then you should also:
- Go into your user properties and resend the IT Policy to your BlackBerry
- Connect your BlackBerry to you desktop and run Desktop Manager to let it resync (This is not really needed with BES 4.0, but I believe it does ensure any MDS or IT Policy changes are applied to your BlackBerry right away)
- Reboot your BlackBerry (removing and replacing the battery is usually easiest)

After you have done those steps please try the BlackBerry Browser again. If it is now working then Mobile SSH should now be able to connect using your MDS.

I assume you encountered this error by switching the Mobile SSH connection method from Default to BES/MDS? Normally this error occurs when the MDS has not yet been properly enabled on a handheld so the above steps should resolve this.

If you are still having problems I encourage you to contact me directly at