Putty and Winscp setup

E

eddied

New Member
Joined
Mar 6, 2006
Messages
7
Reaction score
0
Hi Guys

I'm a new IBurst user and so far, the experience has been extremely positive.

This morning however, I was horrified when I discovered I could not connect to a remote box through either Putty or WinSCP. I'm told IBurst utilizes a transparent proxy, might this be the cause of my problems? If not, what am I doing wrong?

Thanks in Advance
 
Same here. I don't use Putty though - use linux.

EDIT: Same here, as in like Luke, SSH is working fine for me.
 
Same here... Everything work like a charm.... Putty and WinSCP3
 
Iburst indeed does use a Incomming Transparent Proxy (196.2.124.251).Putty and WinSCP works fine.
 
I'm a still having no luck. Connecting with the same box through a dailup connection works perfectly. When I switch over to IBurst however, no dice. WTF?? Do I have to specify the transparent proxy to putty or winscp? The remote box I'm connecting to uses port 222, might this port amazingly be blocked by IBurst somehow?
 
Maybe 1 of the above posters can test the IP for you, if you want. Only IP is needed, no login info. Maybe PM one of them. Unfortunately I can only check after hours. BTW, i'm connecting thru port 443
 
Weird, a partner in crime managed to connect to the same box through his IBurst connection. Is it possible that my low-budget I-GO account is port-shaped(my friend has a G6 account)?
 
eddied said:
Is it possible that my low-budget I-GO account is port-shaped(my friend has a G6 account)?
Click to expand...
Not likely - I have an I-Go Lite that i use regularly when i'm out the office and I have no problem with SSH
 
eddied said:
I'm a still having no luck. Connecting with the same box through a dailup connection works perfectly. When I switch over to IBurst however, no dice. WTF?? Do I have to specify the transparent proxy to putty or winscp? The remote box I'm connecting to uses port 222, might this port amazingly be blocked by IBurst somehow?
Click to expand...

You specified port 222 - this port is in use by Smoothwall in a default installation.

Most other installations default to port 22.

Are you sure you're using the correct port?

Have you tried changing your MTU settings for iBurst manually?
 
try:

telnet <server_IP> 222

What happens?

I ssh to all sorts of non-standard ports on iBurst (with an ipcop box inbetween that listens on 222 on the inside), and have no problems.

Maybe you have some sort of personal firewall software on your PC that blocks outgoing connections on 222 for that specific interface - which might explain why it works on dial-up.
 
OK, so I disabled my firewall and I am still not able to connect.

So I decided to have a cup of coffee, stare at the wall and clean up my desk seeing as I was unable to earn my paycheck. In the process of cleaning up my desk, I moved my Desktop Modem closer to the window.

Signal strength picked up from 70% to around 100%.
Just for the hell of it I tried to reconnect with Putty and hey-presto, works perfectly.

So are you telling me I'm able to download, browse, play games and do all the things expected from an Internet connection at 70% IBurst signal strength except connect through ssh?

Anyway, thanks for all your help. With IBurst I'm learning something new everyday ;)
 
eddied said:
So are you telling me I'm able to download, browse, play games and do all the things expected from an Internet connection at 70% IBurst signal strength except connect through ssh?
Click to expand...
:confused: :confused:

Weird... but glad it's sorted out. Still going :confused: on this one... :D
 
There is absolutely no way that an increase in signal strength could result in SSH suddenly working (or is there??? :) ).

What probably happened was I reset the modem, although I can't remember doing that. What I am 100% sure of is that my problem was NOT DUE TO CONFIGURATION OR SOFTWARE ERROR ON MY MACHINE.

In any case, I'm glad it's working. Thanks for all your help, this community is alive and well.
 
It can. ssh is an interactive conversation between the host and the server. A combination of slow response times and packet loss can easily cause your login attempt to time out.

Imagine working on iBurst, and having to ssh into a box on a Sentech VSAT connection....
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X