Hi All, I'm having trouble with the Tunnelier client connecting to a new WinSSHD server.
I had the server setup in trial mode on a box in my DMZ, got my client to purchase the Tunnelier client and it all worked great. I was able to do a windows share via the internet.
I now setup the real server and installed a shiny new copy of WinSSHD, exported the config from the test server, imported to real server + I moved the IP address from the test server to the real server (I am NATting on my firewall).
Problem is now when my client (person) uses the Tunnelier client, they get "Connection failed. Connect() failed: WIndows error 10061 : No connection could be made because the target machine actively refused it."
I have also tried connecting from my home machine and get the same error. I can telnet to the servers address on port 22 and can clearly see that its a WinSSHD server and the list of encryption/authentication protocols. I also tried the Putty client and get a network error connection refused message.
But here's the thing. I can connect using Tunnelier from other networks. I've tried two different ones that definately traverse the internet to get to the server.
Can anyone provide any troubleshooting tips here. I'm at a loss to explain what I see happenning.
Friday, March 17, 2006
you mention that you tried:
A. connecting with Tunnelier and got error 10061;
B. connecting with PuTTY and got the equivalent error;
C. connecting with "telnet server.ip.address 22" and got the SSH server version string?
Have you actually tried these all on the very same machine, or were any of these attempts made on different machines?
If it were just Tunnelier not working and telnet working, I would guess you may have configured incorrect proxy settings for outgoing connections. However, with PuTTY not working either, and assuming you don't have the same proxy misconfiguration there, I have no explanation at this time...
Saturday, March 18, 2006
Yes, All are happenning on the same machine. It was a fresh installation of Tunnelier and Putty as well.
To make matters even worse, I installed Tunnelier onto my notebook and using the same internet connection, I can connect to the WinSSHD server. Config consists of just enetering the IP address of the WinSSHD server at the moment so theres not much chance of doing that wrong.
I'm looking for troubleshooting ideas as my clinet seems to have the same issue from their office.
You know the moment when you realise whats wrong but you've opened your mouth and made an idiot of yourself aleady. Yep, just had one of those.
My personal firewall wasn't configured to allow port 22 out and also to not popup any message. Do I feel like a clown! (let me check, red nose, big shoes, yep thats a clown).
Thanks for you help Dennis, sorry to have wasted your time.
Saturday, March 18, 2006
Ah, and telnet.exe must have been permitted (unblocked), so it did work with Telnet but not with other programs. Interesting! Thanks for sharing how you fixed it.
Sunday, March 19, 2006
I spoke to my client this morning and explained the problem I found and asked them to double check their firewall as they claim to not have any outgoing restrictions and guess what? They had exactly the same problem. So, with the rules updates its all working fine now.
Monday, March 20, 2006
This topic is archived. No further replies will be accepted.Other recent topics