hosting problem with Just Host

[gutterleech]

I created a website for some one. But, while uploading it, just Host always gives me an error. Login Failed.
She talked to Just Host and they told her that there is a congestion problem with my ISP. I checked with my ISP and they told tht everything is fine.
This is the log of Tracert test.

Any suggestions? what should I do???

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Manu>tracert search-4.me

Tracing route to search-4.me [79.170.44.130]
over a maximum of 30 hops:

1 1349 ms 115 ms 107 ms 172.29.243.129
2 102 ms 125 ms 105 ms 172.29.243.131
3 121 ms 115 ms 126 ms 115.113.56.129.static-delhi.vsnl.net.in [115.113
.56.129]
4 120 ms 107 ms 110 ms 121.242.227.245.static-delhi.vsnl.net.in [121.24
2.227.245]
5 141 ms 130 ms 147 ms 59.163.55.149.static.vsnl.net.in [59.163.55.149]

6 1597 ms 153 ms 129 ms 59.163.55.149.static.vsnl.net.in [59.163.55.149]

7 126 ms 147 ms 128 ms if-14-0-0-101.core2.MLV-Mumbai.as6453.net [216.6
.13.37]
8 143 ms 148 ms 152 ms if-12-0-0.core1.MLV-Mumbai.as6453.net [209.58.10
5.81]
9 2216 ms 249 ms 269 ms if-1-0-0-1980.core1.PYE-Paris.as6453.net [80.231
.196.37]
10 * * 268 ms Vlan1804.icore1.PYE-Paris.as6453.net [80.231.196
.30]
11 * * * Request timed out.
12 258 ms 269 ms 259 ms te1-1.ccr02.par04.atlas.cogentco.com [130.117.15
.157]
13 259 ms 277 ms 268 ms te0-2-0-4.mpd21.par01.atlas.cogentco.com [130.11
7.50.145]
14 278 ms 268 ms 267 ms te1-7.mpd02.lon01.atlas.cogentco.com [130.117.0.
181]
15 306 ms 312 ms 323 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
16 305 ms 272 ms 279 ms 149.6.185.90
17 285 ms 272 ms 276 ms mx02-xe1.2.0-dry.dc2.nodefour.net [83.166.164.38
]
18 271 ms 289 ms 289 ms 83.166.164.54
19 2023 ms 289 ms 299 ms web130.extendcp.co.uk [79.170.44.130]

Trace complete.

C:\Users\Manu>

C:\Users\Manu>

[AntonyF]

That sounds like very bad advice they've given... congestion sounds like hokey!

What was the error?

P.S. in the time try switching to/from PASV mode if you can find the option, that's normally an issue.

[gwpriester]

Are you publishing through Web Designer or are you using an FTP application?

And is the problem still occurring?

Sometimes password servers have problems and reject log ins automatically even though the log in is correct.

[ckh]

Looking at the tracert, I'm inclined to think it may be your ISP

1 1349 ms 115 ms 107 ms 172.29.243.129

The first hop in your trace should be more like 10 to 15 ms and not over 1300, that may indicate a problem with your network itself where your computer is at. I'm assuming that is your IP.

19 2023 ms 289 ms 299 ms web130.extendcp.co.uk [79.170.44.130]

over 2 seconds for the ping to your hosting account. With all of the other high ping rates, I'd say it was a combination of your home network or your ISP's network causing the problem.

Try tracing other other sites and see what you get. google.com might be a good one just for comparison. Yahoo.com another.
6 1597 ms 153 ms 129 ms 59.163.55.149.static.vsnl.net.in [59.163.55.149]

Looks to still to be within your ISP's network. You shouldn't see anything that high within your ISP's network.

[gutterleech]

Hello.

I am getting error "Login Failed" while trying to login to the control panel used by JustHost. I am not uploading the site. Just trying to login to site control panel as told by the person for whom I created website.

- I have tried to login using a different PC which uses different broadband service provider and ISP, and I got the same error. Login Failed.

My Ip is 121.245.30.206


If its my ISP issue, then how come I can login into my plesk control panel, and its Ftp, and every other site. Only this just host control panel is not working.
Any clue?


I am using 3 MB PS plan, and even if the signals are low, I get the speed of more than 1 mb ps

[gutterleech]

19 2023 ms 289 ms 299 ms web130.extendcp.co.uk [79.170.44.130] - It has nothing to do with my IP because, I am in India. So, i suppose it related to JustHost, as the website I created is on the extension. ORG.UK

6 1597 ms 153 ms 129 ms 59.163.55.149.static.vsnl.net.in [59.163.55.149] - this is related to me, because, my broadband service provider is Tata photon, which also works under the name VSNL ( they took over this company from our screwed up government).


This is my tracert for Google.com. Any help would be appreciated, as I dont know how to read Tracert.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Manu>tracert google.com

Tracing route to google.com [66.249.89.104]
over a maximum of 30 hops:

1 122 ms 110 ms 129 ms 172.29.243.129
2 106 ms 108 ms 209 ms 172.29.243.131
3 122 ms 108 ms 110 ms delhi-202.54.240.193.vsnl.net.in [202.54.240.193
]
4 142 ms 148 ms 129 ms 59.163.16.13.static.vsnl.net.in [59.163.16.13]
5 282 ms 145 ms 131 ms 59.163.16.13.static.vsnl.net.in [59.163.16.13]
6 129 ms 127 ms 142 ms 59.163.25.242.static.vsnl.net.in [59.163.25.242]

7 145 ms 129 ms 131 ms 121.240.0.10.static-Mumbai.vsnl.net.in [121.240.
0.10]
8 126 ms 129 ms 145 ms 216.239.43.214
9 162 ms 161 ms 155 ms 72.14.232.100
10 199 ms 218 ms 220 ms 66.249.94.74
11 292 ms 275 ms * 72.14.232.115
12 335 ms 258 ms 258 ms 209.85.255.35
13 259 ms 270 ms 272 ms 72.14.236.126
14 247 ms 268 ms 249 ms nrt04s01-in-f104.1e100.net [66.249.89.104]

Trace complete.

[AntonyF]

Hello.

I am getting error "Login Failed" while trying to login to the control panel used by JustHost. I am not uploading the site. Just trying to login to site control panel as told by the person for whom I created website.

That's nothing to do with your internet connection then. It's probably a username/password error. You need to ensure that's correct - and if you are sure, get their tech support to try and login with those credentials.

[gutterleech]

Yeah, thanks. it was a password issue. I asked her many times about the password. She always gave me the incorrect one. Today, I insisted her to check the password. Then she checked and gave me teh correct password.

[oltonalex]

Would have thought so, a congestion issue doesn't cause a login error based on wrong login credentials :P