ProComm errors on Win 2000 when open a telnet session

[Thornious]

All,

I know this a forum for aspect, but I was hoping someone else has had this error and resolved it. Since we have upgraded to W2K ProComm crashes randomly when opening a telnet session. I am using v4.8 of ProComm Plus and have tried installing this on many different machines with the same result. It does create a windows error file but that is not much help to me. If anyone else has had this problem and could shed some light on a fix, that would greatly be appreciated.

thanks
rich

 

[knob]

Can't say I have any real ideas for this, as I run NT instead of Win2K. Are you using the Connection Directory to make the connection? If so, you can try making a manual connection (Data | Manual Connect menu item) and see if that works better. If so, your Connection Directory may have possibly been corrupted (small chance though). You might want to try closing any other applications that are running at the same time in case there is a weird conflict going on (again, small chance).

Are you running version 4.8? Previous versions of Procomm were released before Win2K came out.

 

[Thornious]

Knob,

Thanks, but yeah I am definitely on Version 4.8.

I am using an imported old connection directory on my correct machine, but I have tried with a clean new directory on freshly installed machines and the same problems still occour.

I was not able to reproduce the problem when I manually connected to a session. It does seems likely that it is tied to connection directory. But why would it show up on a new install?

 

[knob]

Oops, you did mention you had 4.8 in your first message, I must have read right over that.

Are you manually creating the entries in the new Connection Directory, or are you importing them from a text file?

 

[Thornious]

Thanks for the advice.
I am manually creating entries in ProComm so far.

I did take your advice and stared to look harder at the connection dir possibility. So I deleted my pw5.dir again and rebooted. But this time when I built the connection, I put the port in the box designated TELNET PORT in the telnet options tab. So far I have used ProComm multiple times and it has not failed since. I will keep my fingers crossed. I figure it was a combination of W2K and ProComm, because in previous editions of ProComm & W95 you could place and space after the ipaddress and put the port number right there with no harm. Thanks again for pointing out the obvious some times its the little things. I will let everyone know later if this was really the fix or not.

 

[imshaikh]

Hi-
We are also experiencing the similar errors on Procomm running on Win2k Server. I was wondering if you could explain the steps involved in building new connection and the TELNET PORT setting as mentioned in your last response. I would really appreciate it.

 

[imshaikh]

Your solution to procomm issue could be quiet useful to me. I would really appreciate it if you could respond to my message at your earliest convenience. Thanks in advance for your help.- IS

 

[knob]

What it sounds like he did was delete his Connection Directory (pw5.dir) and then restart Procomm, which will cause a new Connection Directory to be created. He then re-entered his telnet entries, but placed the port number in the field labeled Telnet Port (click on the Telnet Options button to see this field) instead of placing the port number after the machine name in the Host/IP Address field.

 

[Thornious]

The solution I mentioned did not work. It seemed to work fine when I kept the connection directory at a very low number of entries i.e. 3 or 4, but when I placed more than that in it started failing again. Let me know if you find any solutions it would greatly be appreciated.

 

[knob]

Someone over on the Symantec support forum is having a similar problem with telnet connections crashing on Windows 2000. Is that you by chance?

 

[Thornious]

yes thats my manager and they were not much help as you can tell.

 

[knob]

I've been working with the Symantec tech on their forum as well and have posted a few questions about the problem you are seeing. If you could tell your manager to respond to the questions I posted this afternoon, I'll see if I can offer any suggestions. However, I was not able to reproduce the problem on the Windows 2000 SP2 machine I was testing on.

 

[Thornious]

Knob,

Thanks for the info and the help. Hope I did not insult you with my last post if I did I apologize. I will definitely let him know to reply. Thanks again

Rich

 

[imshaikh]

This is for both Rich and Knob-
Knob may not be able to produce the error right away. We notice the telenet failure every 2-3 days. It freezes the entire machine. We almost have to restart the procomm and scheduler every other day. Knob- I really appreciate your ongoing help.

 

[Thornious]

I have found the more you change telnet sessions within the same window the faster the problem replicates itself. Sometimes it will happen on the first connection / session but most of the time it is when you close one connection / session and open another within the same window. Also I have found that when an address fails it will fail more often than others when trying to reconnect or connect again at a later time.

One common factor between Imshaikh's problem and mine is the W2K server. Now mine is not running on a server, but the program is a copy downloaded from the server to my machine where it resides and runs. Is It possible that the server is somehow corrupting the original? Also everyone else here, about 8 people use this same copy and they all experience the same issues.

 

[Thornious]

Knob

I just looked on Symantec website and did not see any posts about the problem. The issue out there that I was speaking of was from Dan Glotzbach and it was posted on March 27. Maybe you could check it out it has a Dr. Watson error log as well. How can I find out what questions you posted in the forum to try to answer them?

thanks
rich

 

[hankm3]

Hello,
Have written Many Scripts using Win98-SE using Procomm Plus 4.8, works Fine. Folks using Win2000-> have Problems with Windows Unable to Find Files Etc.

This may have to do with File Path Names.. (DOS).. Not Sure..

Just a Thought !!

Hank

 

[knob]

One thing to keep in mind is that Procomm is not supported on Win2K or NT Server. I don't know if there are any issues when running Procomm on Server, but I do know that Symantec (and Quarterdeck and Datastorm before them) said that the program was only supported on the workstation versions.

Thornius, you didn't insult me so don't worry about that. I've got a pretty thick skin from working in tech support a few years back anyways. The message thread I was replying to was started by Andy Schroder. If you want to take a look at the questions I've posted in that thread and answer them here, we'll see if we can narrow down what is causing the problem.

One question in addition to the ones I've asked on the Symantec site - when you switch from one connection to another, are you disconnecting from the first connection in some manner?


As for copying the install from the server, I would think this would cause problems, unless you mean the contents of the Procomm CD were copied to the server and you installed from there. IF you actually did copy the installed files from the server, then it's possible this could cause a problem.