Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jwf]

I have a customer that has ICE.TCP Pro on an office workers desktop.  They are getting this person a new machine and have decided that the work done using ICE.TCP Pro would be more appropriate at the console of one of their servers.  So I installed ICE.TCP Pro onto the server (Windows Server 2003).  When I try an execute telnet I get an error message:

Terminal Services are being run from this computer.  A thin client license is required for Pro to run.  Contact J.River, Inc.

They do not wish to run this application via terminal services (used only for admin) but from the console.  Perhaps I have messed something up?

John

[jimn]

You can't run TelnetPro  on a terminal server console without purchasing a terminal server license.

Once the program is installed on a terminal server there is no way for the program to know if it is being run on the console or on 100's of thin clients. So for licensing purposes the program needs a TS license to run on terminal servers.

Jim

[jwf]

This machine isn't a terminal server per se, but runs terminal services for remote administration.  Their is what I do, help admin Windows, and what they do, other stuff.

I will not use tcppro remotely and they will use it locally on the console.

Hmm.

What does this other license cost?  I will need to let them know.

[Bob]

http://www.icetcp.com/products/price-list.html

If you have a VPN connection to their machine running terminal services you are already into their network and so you could just use up a user on YOUR machine and run PRO on it to their Unix server instead of third partying through their machine with terminal services. It's simpler and faster.

[jwf]

Hi Bob,

Thanks for the reply.

I do not want to get to their Unix machine.  That isn't purpose.  I just help them admin the windows server through terminal services.

They have an application that they run once or twice a week.  This application uses TCPPro to screen scrape.  The person/job/machine that they had doing this is going away.  I figured that they could just do it on their server rather than buy a whole new machine just for this.

My connection through terminal services has very little to do with this problem.

They do not use terminal services to publish your emulator.  The option you give me is too costly for something they won't use.  This has taken something that should have been easy and made it into a problem.

Do you have any other suggestions?  Perhaps your screen scraping will work somehow?

John

[Bob]

You can't run PRO remotely on their machine (because it knows it's being used remotely) but THEY can run it locally on that same machine and do the scraping that you described.

[jwf]

Now I'm confused.  And I suppose it's my own fault!  

I got the above error when I was trying to execute the emulator at the console.

I was physically at the computer when I installed it.

Terminal services is running.  Yes.  Terminal services is not being used for anything at this time.

What you are saying is good.  It means we can do as we thought.  So, how do I get it to not give me that error at the console?

John

[jwf]

Okay, more info:

I grabbed a machine out of my pile of development test machines.
I did a clean install of Windows 2003 Server Web Edition.
Included SP1.
Used Security Wizard to config the machine as a web server only.
Included remote admin.
Created one local user only.
(Note: this machine is not in a domain)
Installed TCP Pro.
Created a license/sequence number for that one user.
opened the emulator. <logged in as that one user>
Entered a known host IP address.
And got the above error.

So I have a server right in my office now for working this out.  Yes, I went to their office and grabbed their CD and license document.

John

[Bob]

You must have a VERY old version (help->version information). If it's older than 5.0.81 you will have to update the license server.

http://yabb.jriver.com/ice/index.php?board=2;action=display;threadid=306

Tells you how to update the license server. If the version is newer than 5.0.81 you can just get the update onto the PC in question and run a user install to update that PC (canceling out of configwizard when you reach that step).

[jwf]

Oh yeah, on the box [neat picture!] it has a sticker that says Ver 5.1

[jwf]

Hehe, I popped right in and put the version info right after I posted the previous.  You are apparently on-the-ball!

Anyway, I went to the thread you handed me and the first thing it does is have me get the version info.

Mine all read 5.1.07

Do I need to upgrade?
If so, can I just uninstall and reinstall?

Thanks!

John

[Bob]

Update to the current version and install the user portion on that one PC, then have them try connecting to their unix machine from that one PC again. Though you will get the thin client message, they should not...

[jwf]

Bammo!  That did it!

Thank you very much!

John