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.

Have you tried it from another computer using the same internet connection?

yes, see first post.

Ok. Didn't see that one. Then it is without a doubt a DNS issue. And if you haven't played with your DNS settings it is with 99% certainty on the host site. Your ISP is that last 1% and since you can connect fine to other servers, that 1% is almost eliminated.
Have your host go over the reverse DNS again as Rowan suggested.

Try having them run sshd in debug mode (-d) while you try logging in

He's unable to connect via IP, so I don't see where DNS settings come in to play.

He said earlier that he was able to connect via internet explorer. Just VERY slow.

I internet explorer, yes I can connect very slow. But I also used the IP and not the domain.

If it was a host issue, why all three boxes? I would imagine they would know if they did something to all of them.

Bump for more ideas/answers.

I will pick this back up when i awake from passing out.
I have been up over 48 hours not including 2 one hour naps.

bump for you and good luck

Did you remember to feed the gerbils?

check your firewall.. see if it is blocking port 22 :-)

1. Have your host disable name resolving in your sshd and ftp server configurations. (Temporarily for sshd anyway, ftp reverse lookups are a waste of resources)

2. See if a reverse entry for your IP exists and is resolvable. If not, see above.

3. Change either your FTP or SSH port (or both, whatever) on the server and see if you can connect through the alternate port(s).

I have same problem before two weeks.I was solved it by adding domain name and ip adress from my server into hosts file.

another bump for you

Did you finally get this resolved?

was it fixed and if yes, what was the problem??

Not completly fixed. I can however connect and get some of the work done thanks to crank over at techiemedia who directed me to try using an SSH ftp program over port 22.

I also discovered if I set the timeout function in my ftp to over 2 minutes, it allowed me in. Though it was also a long wait between each task. The SSH way just takes a bit to connect but once connected all is fine and fast.

The direct problem has not been resolved yet and I am leaning toward a hardware issue on my end. So still have a tech scheaduled to see what the fuck is and went wrong.

BTW for those that suggested it, adding ips and domains to hosts file, no help. Firewall was also not blocking any ports. DNS is fine. Lastly I was unable to connect via standard ftp through port 22. Crank had to have me change and set a lot of different check boxes in the secure ftp program he suggested I try.

So then, how come you could FTP in one of my boxes with no delay ?

Makes no fucking sense :2 cents: