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: Error Message in TelnetPro  (Read 1145 times)

crotrei

  • Full Member
  • ***
  • Posts: 12
  • Place Personal Text Here
Error Message in TelnetPro
« on: December 19, 2005, 03:06:05 pm »

A customer of ours is getting an error message that says:

version not supported/socket already connected/socket not bound

I had them change cables, try different ports on hub, and still same message. They are able to get on internet. They said that they were away (on vacation) and didn't touch software and when they came back they started getting it. (so it's not a new install of software) This is only happening on one of the clients. Not sure what's causing this.  ???

Mark
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Error Message in TelnetPro
« Reply #1 on: December 19, 2005, 04:19:06 pm »

Those don't sound like PRO error messages. Could be some underlying OS message either in windows or unix. I would ask him if the error is showing up in a seperate windows window OR in the emulation screen.
Logged

crotrei

  • Full Member
  • ***
  • Posts: 12
  • Place Personal Text Here
Error Message in TelnetPro
« Reply #2 on: December 20, 2005, 07:44:20 am »

He faxed me the error message. It is a small window that has that message and at the top bar it says TelnetPro. I thought at first it might be something in windows too, but the TelnetPro at the top is what has me confused.  :-\
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Error Message in TelnetPro
« Reply #3 on: December 20, 2005, 09:00:20 am »

Maybe some type of software update? Try the following in that order:

1) reboot the machine
2) check the windows firewall settings, unblock telnetpro.exe.
3) check third party firewalls, like mcaffee, disable them temporarily for testing.
4) reinstall pro over the top of the existing installation, cancel out of configwizard when you get to that point (you don't need to run it again)
Logged
 

Page created in 0.015 seconds with 21 queries.