Hello,
I have AT 2.12 running behind a firewall. I have been using it successfully over the last month. Today I was unable to SSH2 out. I did check some basic things first but it seems to be a problem with either my workstation or AT...
In particular if I wait for a while and I get a socks5 error. But what happens after that is what bothers me. When I close AT it generates an error and throws and application error. It is doing this on two different machines.
The error that it throws only happens after a failed SSH2 connect.
Gary
[size=1][ May 07, 2003, 04:40 PM: Message edited by: Brian T. Pence ][/size]
Can you tell me what socks error you're getting?
Just to clarify how I can reproduce this:
1. Start up AbsoluteTelnet
2. Load a connection file that does SSH2 over Socks
3. Attempt to connect (connect fails, what error?)
4. Exit program (program throws exception)
Is this right?
Brian
The order is correct.
The specific error for item 3 is "SOCKS5 Error - Address type not supported" which I assume is a standard winsock error.
Other than that the application works great...
And it's been working for you fine up until now. And you still can't get a proper connection through Socks5?
Sorry, maybe I should have cleared it up. The problem isn't the connection it's what happens when a connection fails and you close the applications.
I did resolve the connection issue and it wasn't with AT. It was some dumb person who setup a static route on the firewall lastnight that didn't come back... Fortunately it wasn't me.
Anyways, if this broken connection happens then you get the application error while exiting the application. Why this seems important is because when this happens Visual C++ opens up and toasts anything that I'm working...
It's not your fault... It's how we have our damned computers configured here at work...
Hope that helps.
Gary
Thanks, Gary..
I was thinking for a minute that we might be dealing with two different issues, here. I'm glad to hear that Absolute is connecting via socks again. I'll have to look into the crash issue, though. This shouldn't happen.
Gary,
What version of Windows are you using?
Brian
2000Pro, SP3 with hot fixes as of 5/4/2003.
Same here. Problem is, I can't recreate the error with my proxy server. What proxy server do you use?
