[EMAIL PROTECTED] wrote: > so what changed on your box and why > did you change it > since > you were able to ssh?
Unfortunately I cant say when it started. I also tried many setups that is why I dont think its the configuration of my box. I tried booting a live Linux, that should rule out wrong configs. This is my current knowledge: - Connecting (to the server) with putty.exe does work. - Connecting to a friends server (using openssh) at the _same_ network doesnt work. That is it waits until connection times out at debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP - Connecting from the server (using openssh) to the outside world does work. - Changing MTU changes the point were connection aborts. with MTU set to 1446 it aborts at debug1: SSH2_MSG_KEXINIT sent Wheras with MTU set to 1500 (on both sides), the client gets debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Thanks, Micha -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
