i dunno if that is the issue or not
but anytime i have an issue with something randomly stop working i just revert time a few days and it works :)
plus try it
i want a 100 bux to gamble away

ok then, bbiab.

Might be the issue, but only if he's using a domain instead of an IP and that shouldn't be the case for SSH.

puzzle .....

I wouldn<t restore back to a previous date, unless nothing works....

How about downloading FlashFxp trial or FTPrush trial ...

A clean install could maybe solve the problem... :2 cents:

Sometimes if an isp is having a ddos or something going on coming through a particular port, or a virus that is spreading via a particular port they will block that port off the network for a while. Some people might remember this happening with the ILoveYou virus a while back. They blocked a port that is used for remote desktop on windows. Was quite the hassle. Try a port change and see what happens. If its just your isp blocking it that would explain it.


Or its possible you're receiving a attack via port 21 on your computer.

He said others could connect ... so that wouldn't be the issue .

Maybe he could give you or me an FTP temporary access to a site to really see if we do connect....

This doesn't make any sense other than his IP is blocked by a firewall.

Others not on his connection though. Couldnt it be an attack on port 21 on his connection? Or its being blocked or partially blocked by his isp?

You may also want your host to set up a non-standard port for connection (a high number port) and try that.

Some ISPs have been known to block FTP and SSH connections on standard ports at times, especially if they see a spike in bandwidth or other issues. They may block the ports, etc.

Also, if your ISP uses asymetrical routing (the return route is not the same as the route to your box) you may have a bad hop on the return that is blocking FTP and ssh traffic, but port 80 traffic is being handled differently. That is quite a bit harder to trace down.

You may want to ask your host to give you temp access to FTP to another box they have their, to see if in fact you can connect to any boxes inside that IP block... you may find it is nothing to do with your PC or host, but rather in the ether of the internet.

I was trying to help him with this last night. He can't even telnet to port 21 on his box, yet I can (and connect via FTP for that matter).

The problem is definitely tied to his ISP, router or laptop, but I can't figure out what it is. He can connect anywhere else just fine.

ASM: Sorry I missed you in IRC earlier. You weren't logged in.

connect through a proxy. if it works you know its on your side


also does your box have multiple IPS?if so try another

Its surely the port being blocked. :2 cents:

Ok a system restore just pissed my computer off to no end. Went back a month. I came back to my normal date.

Hardly anything at all worked with a system restore. I have uninstalled shit and stuff since then and well my PC was not happy.

How could it be if he can connect on that port to other servers and other people can connect on that port to his server?

Then why can i connect to other servers?

try to connect to one onf my boxes;

ftp: webdejob.com ( port 21 )
user:[email protected]
pass: 28test

There is a text file in there.

Ahh I misread that. Thought it was other people could connect to your server. Missed that part. Hmm back to drawing board.

right in no problem.


Lol saw green and thought you were asm lol

:1orglaugh :1orglaugh :1orglaugh

.. but I think it is After_shock_media that is the guinea pig on this ... :thumbsup

Connected, via port 21 smartftp.
WK2WK4T7B8TPFGX27JJC6D8MX inside text file.

So you can rule out your ISP , software .

What is left is a firewall on your box ( or another block of another nature ) or a misconfig of your box ....


Like the firewall I run, I can set that IP's that have failed 5 times going in are added to a permanent block ....

Ir is weird.... to say the least

Yeah ok but what?

Example:

Time: Sun Dec 17 11:32:26 2006
IP: 208.116.38.153 (Unknown)
Failures: 5 (sshd)
Interval: 75 seconds
Blocked: Yes

Log entries:

Dec 17 11:32:21 serveur2 sshd[9807]: Failed password for root from 208.116.38.153 port 33456 ssh2
Dec 17 11:32:21 serveur2 sshd[9809]: Failed password for root from 208.116.38.153 port 37039 ssh2
Dec 17 11:32:21 serveur2 sshd[9811]: Failed password for root from 208.116.38.153 port 58033 ssh2
Dec 17 11:32:21 serveur2 sshd[9812]: Failed password for root from 208.116.38.153 port 60947 ssh2
Dec 17 11:32:21 serveur2 sshd[9815]: Failed password for root from 208.116.38.153 port 38928 ssh2

command prompt (Start/Run then type cmd) and type:

ipconfig /flushdns

What if he switched his dns servers on his comp would that make a diff you think? Wont change Ip I dont think though.

did not accomplish anything that helped.

You are 100% sure that other people have/can login by FTP or SSH in your box ?

Since crank is offline right now at techie. Anyone in here have an account I can try to connect to that has some hosting there?

I was going to suggest that, but he said he can't FTP by IP either.

hit me on a messenger and i will give you a user/pass.

i connected just fine to that ftp

test.txt "stupid test upload"


did you try connect via the ip? (65.98.84.218)

edit: oh they said that already....well good luck

I have ICQ, no messenger.

Either email me ( pierre at pdghosting.com ) if no ICQ or give it to sticky...
He can let us know.

that is not his site . I gave him this ftp just to rule out software and ISP.

connects via ip just fine.

I said a messenger not a particular one, my sig has like all of them in it.
My icq is 135982156

My guesses:

1) Reverse DNS problem. The DNS server for the reverse resolution of your IP is playing up. That's why you can connect, but nothing appears to happen (or it takes a long time)

2) TCP MTU or MSS problem. Something in between you and your server is quietly dropping packets that are becoming fragmented. Perhaps a router is also blocking the ICMP message that goes back to you to say "you're sending packets that are too large" (this was a common problem when PPPoE first appeared and shaved several bytes off the default maximum packet size... many sites indiscriminately block ICMP to block pings so it kills off legit msgs too)

I think Rowan is right. It is probably a reverse DNS issue.

Or it could even be as simple as you having your programs connect in either passive or active mode and the server expecting the opposite.

Have you manually set your DNS servers in your TCP/IP settings on your local machine? If so, try letting the computer find DNS servers automatically.

it could also be the server trying to look up your connecting IP using IPv6. That would cause similar problems. If so, disable IPv6 on the server.

pasv ect been checked ect.

never manually set them. flushed already.

host has gone over that.

Hoping someone in here also with techiemedia will let me attempt a connect.