At 6:56 PM -0700 8/30/07, Bennie Warren wrote:
We just had a power outage. I connected to the internet with my wireless Verizon card. Then I opened up Intermapper Remote to see how everything was doing, mostly watching the UPS's to see when to move the generator into place. Well the power came back on in a few minutes so I disconnected the Verizon card and hooked my DSL back up. I didn't think about quitting the application as I usually don't quit anything. Now Intermapper won't let me log in with IM Remote as it says that serial number is in use by another IP. How can I force a disconnect on that connection? I would think I could do that from a menu any time I wanted to kill a connection?

I'm a little surprised that you're having a problem; any connection which is truly inactive, as you'd think one associated with a disconnected wireless card would be, should be disconnected after several minutes of inactivity.

However, apparently this isn't true for you. If you have the telnet server running (or you can get in another way to turn it on), you can use telnet to kill a connection:

1) Log in to the telnet server.
2) Issue a plain KALI command. You will get a list of remote server connections. 3) Find the one with the IP address in question and type the command "KALI id kill" where id is the id from the first column of the KALI command output.

Given that you and Kevin, at least, are having this problem, I think we need to revisit the timing out of inactive sessions, and we should also at least consider whether we should give some way to disconnect a session. Perhaps if you're trying to connect with same license, you could be given the option of forcing the other session to end so that you can get on.

-- Christopher

--
================================================
Christopher L. Sweeney
Dartware, LLC
http://www.dartware.com/
____________________________________________________________________
List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

Reply via email to