That sounds more like the ftp-server is configured with the wrong ip.. as you kindly pasted: 161.38.xx.xxx
If the server is on a LAN then this will cause an error as the local maskin has a unic lan ip like 192.168.x.x and then when you connect using that 161.38.x.x ip, passiv mode isn't able to open a port for that ip. Kinda hard to explain this good, but say the server has 192.168.1.1 and you try to open a passiv mode port using 161.38.xx.xxx:<port>, what your really doing is trying to open a connection with his router and not ftp-server, as the router is the one with the 161.x ip .. and the one trying to figure out what to do with it. If it doesn't know... you'll get a connection failed / timeout error.
But then again.. can this be case here?
Yes, if using Passiv Mode
If using some router/wingate/proxy/firewall application/server then problems like this can allso happen as bigstar stated.
What i do:
Disable everything and try, if it works, aktivate 1 element
Still working, one more.. and so on until something stops working, and you've found you source.
If disabling everything isn't work, then the problem isn't you!
Remeber, even try bypassing your router, and try.
Threaded Mode
