Help with FTP not logging in. Bluehost tells me it's my problem

[fainerbainer]

So basically I've been trying to log in with Cyberduck. Our old web server was cheap and we could upload anything. They are now shoddy so I transferred our domain thinking I can just upload my website from my computer files right away after transfer. Yet, now I can't even connect and the only I help I got was this after sending in my trace report:


wait until that router is fixed or track down who owns it

So what I don't understand is that I can still connect to my old server and look at my directory that is still stored on their hardware. I can connect with cyberduck to the old server but not to bluehost.

I ask what the problem is and he says to do the above. That my "hops" aren't making it and then timing out. I don't time out on the old server though.

I then ask if there's any easy ways to figure out why the router isn't connecting and his answer is:


]: and that router currently isnt working. I suggest you go read about the nature of internet traffic, router hops and related information if you are unsure what I mean.

So that was his response. I then ask if I need to get a new router, hardwire my connection or just some kind of idea of what to do to connect to bluehost. He says:


I'm sorry but I am not here to troubleshoot your internet connection. I already told you what I suggest
[1:02:09 AM]: since you are choosing to ignore me and the responses I give
[1:02:12 AM]: have a good day

And then he cuts me off. All I want to do is connect and our stinking server and get our website back online. The hop on the router is not in their network. I understand that but just a little help in the right direction would mean a lot. Not just "you're ignorant so read up on what you need to do."

I didn't fork over $166 just to get a asinine response like that. Any of you have problems with this in the past and what you did to resolve a time out from your FTP?


Running cyberduck on a macbook (2.16Ghz core 2 duo, 1g ram, using iWeb to make files/directories).

:::EDIT:::

Traceroute has started ...

traceroute to dufurchristianchurch.org (74.55.100.8), 64 hops max, 40 byte packets
1 8.64.374a.static.theplanet.com (74.55.100.8) 2.746 ms 2.234 ms 2.277 ms
2 12.153.181.3 (12.153.181.3) 23.366 ms 23.566 ms 22.825 ms
3 12.154.212.1 (12.154.212.1) 5.770 ms 5.577 ms 6.571 ms
4 12.116.162.109 (12.116.162.109) 14.013 ms 13.127 ms 12.950 ms
5 tbr1.st6wa.ip.att.net (12.127.6.50) 16.353 ms 16.912 ms 16.786 ms
6 12.127.6.57 (12.127.6.57) 14.109 ms 15.950 ms 13.805 ms
7 192.205.35.30 (192.205.35.30) 13.195 ms 19.608 ms 17.719 ms
8 ae-2.r20.sttlwa01.us.bb.gin.ntt.net (129.250.4.157) 16.375 ms 17.888 ms 17.114 ms
9 p64-7-0-0.r20.snjsca04.us.bb.gin.ntt.net (129.250.4.23) 38.456 ms 40.197 ms 38.340 ms
10 ae-0.r21.snjsca04.us.bb.gin.ntt.net (129.250.2.97) 42.336 ms 38.286 ms 39.015 ms
11 as-0.r20.lsanca03.us.bb.gin.ntt.net (129.250.4.97) 47.650 ms 47.679 ms 57.226 ms
12 ae-0.r21.lsanca03.us.bb.gin.ntt.net (129.250.3.34) 51.838 ms 47.361 ms 46.969 ms
13 as-0.r21.hstntx01.us.bb.gin.ntt.net (129.250.3.122) 94.713 ms 86.487 ms 87.099 ms
14 xe-4-3.r03.hstntx01.us.bb.gin.ntt.net (129.250.4.238) 86.743 ms 86.242 ms 87.103 ms
15 xe-4-4.r03.hstntx01.us.ce.gin.ntt.net (128.241.1.6) 84.684 ms 114.423 ms 84.532 ms
16 po2.car11 (74.55.252.206) 91.082 ms 88.145 ms 88.252 ms
17 * * *
18 * * *


So now, is the router on the last IP timing out? I went ahead and talked to that IP address tech support and they said their router was fine. Everything is fine with my ISP and Wireless router. I even ran trace on my ethernet cable and experienced the same thing.

I opened a ticket with bluehost to see if they will resolve this.

What if bluehost says it is that IP's problem (ThePlanet.com) and ThePlanet (who told me to talk to bluehost) says it is bluehost's problem? Am I stuck with a domain that I can do nothing with???!

[Early Out]

Apparently no one involved in all of this has noticed one important fact. That domain, dufurchristianchurch.org, expired on Aug. 13, 2008. That's why you can't connect to it.

Until that's sorted out, you should be able to connect to your BH account using the numeric address. Your "welcome to BH" email should have included that - it will look something like ftp://username@12.34.56.78/public_html, where "username" is your 8-character BH username, and 12.34.56.78 is the shared IP address of the server you're on. Depending on your FTP client, you might also try entering 12.34.56.78/~username as the hostname (again, where 12.34.56.78 is the shared IP address, and username is your BH username).

[Reverend]

Part of the problem was that last night, Integra was having router issues that were causing problems for a lot of people, myself included.

It appears that there was some miscommunication/misunderstanding going on (not excusing anything, just stating).

I know that plenty of other people were having problems getting through Integra to Bluehost, but the connection issue was resolved quickly.

The support agent could have communicated that better, but having done tech support myself when something major like that happens and it's completely outside your control, dealing with tons of people all at once, all bitching you out for something that isn't your company's fault. . . it can make a person terse.

As for your particular issue, as Early Out said, your expiration date might be the problem. Although, doing a whois search shows your DNS do not even point to bluehost, so that might also play a big part.

[Early Out]

Although, doing a whois search shows your DNS do not even point to bluehost, so that might also play a big part.Yes, we seem to have a whole series of problems on this one. Step one, renew the domain name. Step two, point it to the BH nameservers (ns1.bluehost.com and ns2.bluehost.com). Step three, wait for DNS propagation.

The "bad router" problem is always a messy one. Somewhere between you and the site you're trying to reach, there's a router that's lost its mind. Bluehost can't fix it, obviously. Your ISP says, "It's not our router, so we can't fix it." Of course, the ISP isn't telling you the whole truth. They have peering agreements with the folks who do own the router, so they're the ones who have the clout to get it repaired.

Happily, these kinds of problems usually get taken care of pretty quickly - in a NOC somewhere, there's a red flashing light on the board, and it's just a matter of getting the responsible party to swap out the flaky box.

[fainerbainer]

Apparently no one involved in all of this has noticed one important fact. That domain, dufurchristianchurch.org, expired on Aug. 13, 2008. That's why you can't connect to it.

Until that's sorted out, you should be able to connect to your BH account using the numeric address. Your "welcome to BH" email should have included that - it will look something like ftp://username@12.34.56.78/public_html, where "username" is your 8-character BH username, and 12.34.56.78 is the shared IP address of the server you're on. Depending on your FTP client, you might also try entering 12.34.56.78/~username as the hostname (again, where 12.34.56.78 is the shared IP address, and username is your BH username).

Used that as my FTP and it connected in less than 2 seconds. hrmmmm...thanks.

Now it seems I need to get it renewed and pointed to bluehost. . .However, the support at server south is really bad! I'll see what I can do

[redsox9]

Sounds right because your BH account is still active. Now you just need to renew the domain name and point it to the proper name servers.

[fainerbainer]

Sounds right because your BH account is still active. Now you just need to renew the domain name and point it to the proper name servers.

I just sent a ticket/support request to DirectI (who was registrar before). I asked them to renew it. Will I have to pay them again or will they just do it and direct it to bluehost with no problem. I should have checked into this when it said "expired domains won't transfer".

But I tried contacting serversouth (old server setup people) but I didn't expect all the third party stuff. I guess I'm learning a lot in this process but it would have been helpful for the support at bluehost to help me out a bit more.

The last person I talked to on bluehost was very helpful! Thanks guys. The forums are the ones who have cleared this up and got me asking the right questions. I've depended on forums for troubleshooting for so long and it's nice to see this community on bluehost!

Thanks again.


PS:

I'm to this spot now:

"Congratulations, the domain dufurchristianchurch.org has been successfully UNLocked with the Losing Registrar, which means it can safely be transfered." I'm trying to use bluehost as registrat and point to their server. I can't get the registry authorization code. It won't email it to me either. hmmm