Results 1 to 23 of 23
  1. #1

    My First 48 Hours: **********.com Review

    Server Ordered: CELERON 2.4 LS VR
    Date: Fri, 14 January 2005
    Time: 05:55

    Order went through instantly, all money is in their hands.

    Jan 14, 08:57: Contacted via IM and told server will be ready in 12-48 hours.

    Jan 14, 11:10: Contacted via IM and told server is now in the "instant setup" queue and will be ready "today."

    Jan 14, 15:38: Contacted via IM and told server will be ready in 6-10 hours.

    Jan 14, 20:34: Contacted via IM and told server installation not going well, new estimated time Jan 15, 9AM.

    Jan 15, 09:36: Contacted via IM and told server will be ready in 2-3 hours.

    Jan 15, 10:19: Contacted via IM and told server is almost done, but they must wait for the DirectAdmin licensing.

    Jan 15, 15:00: IP addresses and root passwords delivered to me. Still can't do anything to the server cause it's not "live" on the net yet, because control panel not installed yet.

    Jan 15, 20:04: I contacted them via IM for an update. No response.

    Jan 15, 23:44: Finally contacted and was told they'll "check into it."

    Jan 16, 02:27: Receive DirectAdmin license info and they install the control panel and send me login information.

    Jan 16, 09:00: I find out.

    Jan 16, 17:40: Server crashes in the middle up uploading via FTP. Does not come back.

    Jan 16, 18:19: Contact tech support through ticket system.

    Jan 16, 19:21: Am told they are running a checkdisk on it.

    Jan 16, 20:15: Am told checkdisk still running.

    Jan 16, 20:45: Am told to keep checking every few hours to see if the server pings.

    PRESENT: Server still down. No responses to tickets and all the IM techs are offline.

    Draw your own conclusions.

    edit: I may have converted some of these times wrong, because I'm trying to piece together ticket conversations and IM messages I'm receiving from two different timezones other than my own. None of them are off by more than an hour which doesn't throw off the entire timeline, especially how long its taking to get a stable server.
    Last edited by EverSpeed; 01-16-2005 at 10:45 PM.

  2. #2
    Join Date
    Jan 2005
    Location
    Singapore
    Posts
    93
    Have you search WHT for review on them before purchasing?
    http://www.kwanun.com
    Kwanun Internet Services
    Shared|Reseller Webhosting

  3. #3
    YES, that's why I went with them. I found no negative comments on them. Not one. There were people who had their server in two hours! Incredible support where their server went down and it was up in less than an hour. How they reboot servers often before you report it to them because of their monitoring system.

    Phht.

  4. #4
    My server is still down.

  5. #5
    Join Date
    May 2004
    Location
    Blue Springs, Missouri
    Posts
    366
    remember when I said that comment was spam? I wasn't lying ...

    best of luck though!!

  6. #6
    They told me it was back up, I got all excited, but it was down.

    Still down.

  7. #7
    Join Date
    Dec 2002
    Location
    Ferenginar
    Posts
    4,157
    Just curious what are the specs and price?
    What's your budget?

    Seriously, what's your budget?

  8. #8
    Join Date
    May 2004
    Location
    Blue Springs, Missouri
    Posts
    366
    if I remember correctly, all ********** does is resell servers for tomsyer.net.

    I could be wrong though ....

  9. #9
    Join Date
    Apr 2003
    Location
    Sweden
    Posts
    1,061
    Sounds like a "reseller reselling through a reseller"

    Although I hope you will have you server online soon. The dedi business is like every other business; sometimes things go wrong - and as you said only positive responses from other WHT users regarding them, so give it a few days.
    -Mr Bister

  10. #10
    Seven MORE hours later, still not up. And they keep closing my support ticket.
    Last edited by EverSpeed; 01-17-2005 at 11:05 AM.

  11. #11
    Join Date
    Jul 2003
    Posts
    191
    Do they have a number to call them? It looks like they are giving you the shaft. Threaten them with a chargeback and see if they respond.

  12. #12
    Join Date
    Jan 2005
    Posts
    60
    Originally posted by mrbister
    ...and as you said only positive responses from other WHT users regarding them, so give it a few days.
    see this thread

    Not all are happy with **********...

  13. #13
    They do have a representative here, maybe he can clear things up.

  14. #14
    Join Date
    Jul 2004
    Posts
    351
    Originally posted by RossMAN
    Just curious what are the specs and price?
    I think this one:
    Intel Celeron 2.4 LS
    Memory: 512MB DDR System Memory
    Storage: 80GB 7200RPM IDE Hard Disk
    Transfer: 1200 GB per month Premium Bandwidth
    Fully Managed
    Free Panel: DirectAdmin (Value $29)
    Control Panel: cPanel +$33
    Live Support/HelpDesk
    IP Addresses: 5
    $89.00 Monthly - Free Setup

  15. #15
    Originally posted by input
    see this thread

    Not all are happy with **********...
    LOL!! Look at the starter of the thread... ME. LOL!

    Anyway, UPDATE:

    I am going on 4 hours and 11 minutes of UPTIME. I was informed the server had a bad network card. I will update this thread as needed, but I truly do hope it was the network card.

    I will post a one month review as well. Thanks, **********.com for getting it working. Need a little work on communication, but was told that's being worked on. We'll see and I'll let you all know!

  16. #16
    Join Date
    Dec 2002
    Location
    California
    Posts
    2,005
    Originally posted by Morgant6911
    Do they have a number to call them? It looks like they are giving you the shaft. Threaten them with a chargeback and see if they respond.
    This is a stupid idea. Fraud works two ways, if you claim fraud when there is none, you are the one commiting fraud.
    I wish all my traffic went through AS174.

  17. #17
    Well, here's an update... after they fixed my server, I was getting pings of 50-60ms. Now, a whole half day later...

    Pinging slstream.com [207.226.20.30] with 32 bytes of data:

    Reply from 207.226.20.30: bytes=32 time=659ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=657ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=655ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=662ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=653ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=657ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=654ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=662ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=663ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=668ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=682ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=678ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=674ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=659ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=653ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=659ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=671ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=670ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=659ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=671ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=668ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=643ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=638ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=646ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=635ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=647ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=654ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=661ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=657ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=666ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=659ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=666ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=668ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=669ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=665ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=657ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=655ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=675ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=673ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=676ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=671ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=669ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=672ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=673ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=677ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=680ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=682ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=676ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=679ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=677ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=665ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=678ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=665ms TTL=47
    Reply from 207.226.20.30: bytes=32 time=688ms TTL=47

    Ping statistics for 207.226.20.30:
    Packets: Sent = 54, Received = 54, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 635ms, Maximum = 688ms, Average = 664ms

  18. #18
    Join Date
    Jul 2001
    Location
    Melbourne, AU
    Posts
    1,392
    Which data center is this server located in?
    SERVSTRA | THE ENTERPRISE CLOUD SERVER & DEDICATED SERVER SPECIALISTS
    中国优先网络 - 最快到中国大陆
    14 world wide locations to choose from!

  19. #19
    Join Date
    Jan 2005
    Posts
    60
    Nothing wrong with the pings from here:

    From Dallas, Texas:
    PING 207.226.20.30 (207.226.20.30): 56 data bytes
    64 bytes from 207.226.20.30: icmp_seq=0 ttl=56 time=54.591 ms
    64 bytes from 207.226.20.30: icmp_seq=1 ttl=56 time=54.594 ms
    64 bytes from 207.226.20.30: icmp_seq=2 ttl=56 time=54.528 ms


    From Paris, France
    PING 207.226.20.30 (207.226.20.30) 56(84) bytes of data.
    64 bytes from 207.226.20.30: icmp_seq=0 ttl=50 time=168 ms
    64 bytes from 207.226.20.30: icmp_seq=1 ttl=50 time=168 ms
    64 bytes from 207.226.20.30: icmp_seq=2 ttl=50 time=168 ms

  20. #20
    Join Date
    Apr 2004
    Location
    Florida, USA
    Posts
    186
    From Irvine, California:
    Pinging 207.226.20.30 with 32 bytes of data:

    Reply from 207.226.20.30: bytes=32 time=23ms TTL=54
    Reply from 207.226.20.30: bytes=32 time=40ms TTL=54
    Reply from 207.226.20.30: bytes=32 time=17ms TTL=54
    Reply from 207.226.20.30: bytes=32 time=45ms TTL=54

    Ping statistics for 207.226.20.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 45ms, Average = 31ms

  21. #21
    Thanks for posting those ping times for me everyone. I ran a traceroute and the problem was one hop from my server, so I don't know why everyone else was getting good ping times and I and my friends weren't. The pings to all the servers within my ISP's (Time Warner Cable) network were all incredible until it reached the "outside world".

    Anyway, it returned to normal several hours after my post about ping times.

  22. #22
    Join Date
    Jul 2004
    Posts
    351
    From Europe:
    Pinging 207.226.20.30 with 32 bytes of data:

    Reply from 207.226.20.30: bytes=32 time=206ms TTL=56
    Reply from 207.226.20.30: bytes=32 time=205ms TTL=56
    Reply from 207.226.20.30: bytes=32 time=206ms TTL=56
    Reply from 207.226.20.30: bytes=32 time=206ms TTL=56

    Ping statistics for 207.226.20.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 205ms, Maximum = 206ms, Average = 205ms

  23. #23
    Join Date
    Jan 2005
    Posts
    78
    I used DNSStuff.com but I'm on the East Coast:

    Pinging 207.226.20.30 [207.226.20.30]:

    Ping #1: Got reply from 207.226.20.30 in 137ms [TTL=48]
    Ping #2: Got reply from 207.226.20.30 in 132ms [TTL=48]
    Ping #3: Got reply from 207.226.20.30 in 136ms [TTL=48]
    Ping #4: Got reply from 207.226.20.30 in 130ms [TTL=48]

    Done pinging 207.226.20.30!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •