ICE

Please login or register.

Login with username, password and session length
Advanced search  

News:

ICETCP.PRO and ICETCP.PLUS are compatible with Windows 11!

Author Topic: Odd problem with Icetcp Pro  (Read 2395 times)

Rich

  • Jr. Member
  • **
  • Posts: 5
  • Place Personal Text Here
Odd problem with Icetcp Pro
« on: September 27, 2006, 07:31:31 pm »
Hello,

We have an odd problem with Icetcp Pro (Telnet).  When my users return to the office with their laptop (prior using a VPN connection at home) and using Icetcp Pro, a window appears with strange number like that: 24503192, 12668791, etc ...  Meanwhile, the DOS Telnet works without any problems.  I also tested Hyper Terminal and it works.

After 1 hour or 2, there are able to connect to my Unix system using Icetcp Pro.  If the users do not use a VPN connection at home, they have not the connection problem with Icetcp Pro.  Very strange !!!

Do you have an idea or a solution ?

Thanks

PS: My users are using Telnet Pro version 5.1.25 on Windows XP SP2 without firewall.  I have upgraded it to 5.1.26 two months ago
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Odd problem with Icetcp Pro
« Reply #1 on: September 28, 2006, 11:08:18 am »
Quote from: Rich on September 27, 2006, 07:31:31 pm
Hello,

We have an odd problem with Icetcp Pro (Telnet).  When my users return to the office with their laptop (prior using a VPN connection at home) and using Icetcp Pro, a window appears with strange number like that: 24503192, 12668791, etc ...  Meanwhile, the DOS Telnet works without any problems.  I also tested Hyper Terminal and it works.
Is the window a windows message box?
If so does it say TelnetPro on the title line or something else??

Quote
After 1 hour or 2, they are able to connect to my Unix system using Icetcp Pro.  If the users do not use a VPN connection at home, they have not the connection problem with Icetcp Pro.  Very strange !!!

Do you have an idea or a solution ?

Thanks

PS: My users are using Telnet Pro version 5.1.25 on Windows XP SP2 without firewall.  I have upgraded it to 5.1.26 two months ago

It sounds a little like PRO is trying to bring up the VPN when you run it in office. Is the IP address of the unix server the same both at home and at work? You may have to disable the VPN in network settings at work so windows doesn't try to bring it up when you run TelnetPro.
Logged

Rich

  • Jr. Member
  • **
  • Posts: 5
  • Place Personal Text Here
Odd problem with Icetcp Pro
« Reply #2 on: September 28, 2006, 08:06:22 pm »
Hello,

The window is a Windows message box.  It says:

Title line:        TelnetPro
Content:        ! Unknown: 24503192

The IP address of the Unix server is the same at home and at work.  Note that Dos Telnet and Hyperterminal works everytime (at home and at work) !!!

Why after 1 hour or 2, the TelnetPro works ?

Richard

Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Odd problem with Icetcp Pro
« Reply #3 on: September 29, 2006, 10:17:24 am »
Hyperterminal and MS telnet are very simple programs that make very little use of the more advanced features of winsock that TelnetPro uses.

I haven't seen anything like what you've described before. I would try a couple of things.

1) download version 5.1.19 from our public ftp site
it's tcp-pro-demo119.exe and is in pub/downloads on ftp.jriver.com

Download it, skip the server install and just do a user install on the one machine that is giving you trouble. Cancel out of configwizard when it comes up. Don't reboot. Try it and let us know the results. There is a difference in how MFC42.DLL is used in versions 5.1.19 and older and versions newer than that.

2) check for hung sessions on the unix machine (netstat).
Logged

Rich

  • Jr. Member
  • **
  • Posts: 5
  • Place Personal Text Here
Odd problem with Icetcp Pro
« Reply #4 on: October 02, 2006, 12:25:24 pm »
Hello,

This morning, the version 5.1.26 doesn't works.  Therefore, I have downloaded and installed version 5.1.19 on the machine who give me trouble.  This old version (5.1.19) works.  I try the version 5.1.26 just after and it works.  For your information, the VPN connection is disabled automatically when the connection is closed (at home).  If I want to activate it, I must start the Cisco Client Connection.

The netstat doesn't show problems.

Another idea ?

Thanks
Richard
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Odd problem with Icetcp Pro
« Reply #5 on: October 02, 2006, 01:01:46 pm »
It sounds like the problem IS related to winsock startup and mfc42.dll because 5.1.19 always works, right??
Logged

Rich

  • Jr. Member
  • **
  • Posts: 5
  • Place Personal Text Here
Odd problem with Icetcp Pro
« Reply #6 on: October 02, 2006, 01:13:08 pm »
Hello,

I don't  know if the version 5.1.19 will always work.  The user must establish a VPN connection at home and return to the office to see if everything is ok.  Currently, both versions works.  This morning, version 5.1.26 doesn't works.  We haven't any problems with the version 5.1.26 if the user doesn't make a VPN connection (the majority of my users are always at the office).

How to correct the Windows Winsock / Icetcp Pro 5.1.26 ?

Thanks
Richard
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Odd problem with Icetcp Pro
« Reply #7 on: October 02, 2006, 01:27:37 pm »
I can't tell you any more until you find out if 5.1.19 reproduces the problem next time you come back from home. If it's related to the mfc42.dll there is nothing you can do at the current time to make 5.1.26 behave like 5.1.19.
Logged

Rich

  • Jr. Member
  • **
  • Posts: 5
  • Place Personal Text Here
Odd problem with Icetcp Pro
« Reply #8 on: October 06, 2006, 03:24:01 pm »
Hello,

After a second test, it's seems that everything works after I have installed the Icetcp Pro 5.1.19.  Even the version 5.1.26 works !!!  

Is it possible that version 5.1.19 have overwrited a "not working file" in version 5.1.26 ?

The solution is to downgrade to 5.1.19 ???

Another solution ?

Thanks
Richard
Logged
 

Page created in 0.017 seconds with 20 queries.