Print

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

[arcs]

TCP-PRO VErsion 5.1.26 - 5 Users
Windows XP Version 5.1(Service PAck 2)
SCO Openserver 5.0.7 Enterprise 5 Users

Having loaded TCP-PRO and configured each PC by "Network Available" method, we are experiencing problems with users "locking out". This seems to occur when a second user logs in and this then locks both users. Also we get the messages:

DEJAVU: Initializing copy protection failed (4,0)
TELNETPRO: Connection Error, Can't create CAquiarius class window
TELNETPRO: Can not create new session.Please run ConfigWizard.

We have re-run ConfigWizard, but keep getting the same messages.

Anyone any ideas how to correct or point us in the right direction if we have done something silly?

[Bob]

TCP-PRO Version 5.1.26 - 5 Users
Windows XP Version 5.1(Service PAck 2)
SCO Openserver 5.0.7 Enterprise 5 Users

Having loaded TCP-PRO and configured each PC by "Network Available" method, we are experiencing problems with users "locking out". This seems to occur when a second user logs in and this then locks both users. Also we get the messages:

What is the "Network Available" method??

Did you install the admin portion onto a machine, share the TC5_USER directory as Full control for all then browse to it from a new client PC and run setup from there??

DEJAVU: Initializing copy protection failed (4,0)
TELNETPRO: Connection Error, Can't create CAquiarius class window
TELNETPRO: Can not create new session.Please run ConfigWizard.

We have re-run ConfigWizard, but keep getting the same messages.

Anyone any ideas how to correct or point us in the right direction if we have done something silly?

Some questions...

Did you ever run an older version??
Did you install PRO on the client PC as a NOT limited user??

[arcs]

This is a brand new installation of unix and TCP-PRO, so no, we haven't run an older version. We have run ICE.TEN on another unix server but have upgraded to a new server and ICE.TCP-PRO.

We have followed the instructions regarding loading the software on to a client PC and sharing the TCP5_User folder.

[arcs]

Hold everything........we may have solved this by lookin at a different problem.

On the unix server we executed the route command:-

route add xxx.xxx.xxx.0 xxx.xxx.xxx.254

0 being the IP "family" and 254 the router.

This appears to have solved the problem. I guess without this the unix server didn't really know where to go!!!!!! yet we could login of sorts. Anyway, all is weel that ends well.  Thank you for your help.