We got a server from them about 5 days ago.

Today (now) we can't reach it since 40 minutes. Support doesn't respond, their phone number on the whois info is wrong.

Can anybody reach this server?: 208.255.246.190

This one was thought to be our primary nameserver but i think we can't do it because of the availibility.
We where working on some stylesheets and all of the sudden it went (the network) down. :(

traceroute to 208.255.246.190 (208.255.246.190), 30 hops max, 38 byte packets
1 voxtreme-gw.cft1.vdi.net (66.78.13.1) 0.657 ms 0.819 ms 0.475 ms
2 cftnnj-gw.cft1.vdi.net (216.74.127.225) 0.955 ms 0.770 ms 0.464 ms
3 pos2-1.hsipaccess1.Weehawken1.Level3.net (63.211.89.149) 1.114 ms 1.400 ms 1.124 ms
4 lo0.mp1.Weehawken1.Level3.net (209.247.8.253) 2.065 ms 2.301 ms 2.235 ms
5 so-3-0-0.mp1.Atlanta1.Level3.net (64.159.1.45) 19.594 ms 20.111 ms 20.124 ms
6 pos8-0.core1.Atlanta1.Level3.net (64.159.3.61) 20.172 ms 19.864 ms 19.554 ms
7 unknown.Level3.net (209.0.227.162) 20.905 ms 20.666 ms 20.357 ms
8 180.at-5-1-0.XR2.ATL5.ALTER.NET (152.63.82.210) 20.447 ms 21.062 ms 21.481 ms
9 0.so-1-0-0.XL2.ATL5.ALTER.NET (152.63.85.193) 20.962 ms 20.845 ms 20.596 ms
10 0.so-2-0-0.XL1.ATL5.ALTER.NET (152.63.85.185) 20.892 ms 20.656 ms 21.267 ms
11 0.so-7-0-0.XL1.MIA4.ALTER.NET (152.63.86.189) 36.155 ms 35.700 ms 35.496 ms
12 0.so-4-1-0.XL2.MIA4.ALTER.NET (152.63.86.186) 35.905 ms 35.711 ms 35.802 ms
13 0.so-3-0-0.XR2.MIA4.ALTER.NET (152.63.101.45) 35.698 ms 36.195 ms 36.191 ms
14 176.ATM5-0.GW1.MIA4.ALTER.NET (146.188.233.165) 36.038 ms 36.276 ms 36.010 ms
15 208.255.246.1 (208.255.246.1) 43.089 ms 40.337 ms 40.324 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *

Man, this sux. 4 hours later still nothing. Can anybody please try to trace the above mentioned server or does anybody know how to reach awebhosting NOW?

A Web Hosting (NETBLK-UU-208-255-246)
2910 Via Vizcaya
Lake Worth, FL 33461
US

Netname: UU-208-255-246
Netblock: 208.255.246.0 - 208.255.246.255

Coordinator:
Keefer, David (DK571-ARIN) dkeefer@awebhosting.net
+1-866-424-4678


Was that the wrong number? Obviously the 555-1212 is wrong (heh). That number is what needs to be registered with ARIN, usually provided to the upstream provider as a contact #. It's in AT&T's phonebook as belonging to AWebHosting, too, so it's probably legit.

The reason traceroutes fail is because they filter them out or something along that line). I was accused of portscanning them by tracing routing. Heh. Good luck.

From VDI:

traceroute to 208.255.246.190 (208.255.246.190), 30 hops max, 38 byte packets
1 eolwa-gw.cft1.vdi.net (66.78.14.97) 0.897 ms 0.238 ms 0.159 ms
2 g0-0.core1.cftnnj.inet.vdi.net (216.74.127.225) 0.689 ms 0.371 ms 0.374 ms
3 pos2-1.hsipaccess1.Weehawken1.Level3.net (63.211.89.149) 1.135 ms 1.113 ms 2.130 ms
4 lo0.mp1.Weehawken1.Level3.net (209.247.8.253) 4.794 ms 1.942 ms 2.313 ms
5 so-3-0-0.mp1.Atlanta1.Level3.net (64.159.1.45) 19.711 ms 19.265 ms 20.613 ms
6 pos8-0.core1.Atlanta1.Level3.net (64.159.3.61) 19.665 ms 19.376 ms 19.586 ms
7 unknown.Level3.net (209.0.227.162) 20.183 ms 20.169 ms 20.571 ms
8 180.at-6-1-0.XR2.ATL5.ALTER.NET (152.63.82.218) 20.226 ms 20.246 ms 20.420 ms
9 0.so-1-0-0.XL2.ATL5.ALTER.NET (152.63.85.193) 20.472 ms 20.407 ms 20.572 ms
10 0.so-2-0-0.XL1.ATL5.ALTER.NET (152.63.85.185) 20.660 ms 20.611 ms 22.194 ms
11 0.so-7-0-0.XL1.MIA4.ALTER.NET (152.63.86.189) 35.533 ms 35.906 ms 36.215 ms
12 0.so-4-1-0.XL2.MIA4.ALTER.NET (152.63.86.186) 35.549 ms 35.548 ms 35.296 ms
13 0.so-3-0-0.XR2.MIA4.ALTER.NET (152.63.101.45) 35.208 ms 35.692 ms 35.816 ms
14 176.ATM5-0.GW1.MIA4.ALTER.NET (146.188.233.165) 36.140 ms 36.882 ms 35.758 ms
15 208.255.246.1 (208.255.246.1) 80.489 ms 41.551 ms 40.407 ms
16 * * *
17 * * *
18 * * *
19 * * *

From RackShack:

traceroute to 208.255.246.190 (208.255.246.190), 30 hops max, 38 byte packets
1 216.40.247.1 (216.40.247.1) 0.895 ms 0.234 ms 0.118 ms
2 tayhou-223-1.ev1.net (207.218.223.1) 0.280 ms 0.408 ms 0.281 ms
3 s10-0-1.gw01.hsto.eli.net (216.190.70.17) 11.585 ms 12.103 ms 11.440 ms
4 a8-0--171.cr02.dlls.eli.net (207.173.115.73) 11.550 ms 12.300 ms 11.385 m
s
5 so-1-0-0--0.er01.dlls.eli.net (207.173.114.118) 11.691 ms 13.210 ms 11.80
9 ms
6 220.ATM1-0.BR3.DFW9.ALTER.NET (204.255.174.17) 12.266 ms 12.454 ms 12.605
ms
7 177.at-6-1-0.XR2.DFW9.ALTER.NET (152.63.100.166) 13.524 ms 13.083 ms 12.3
40 ms
8 0.so-2-0-0.XL2.DFW9.ALTER.NET (152.63.102.5) 13.036 ms 13.081 ms 13.684 m
s
9 0.so-0-0-0.TL2.DFW9.ALTER.NET (152.63.2.181) 14.101 ms 13.653 ms 13.779 m
s
10 0.so-1-1-0.TL2.ATL5.ALTER.NET (152.63.0.1) 40.118 ms 80.230 ms 40.162 ms
11 0.so-4-1-0.XL2.MIA4.ALTER.NET (152.63.86.186) 55.779 ms 54.935 ms 55.117 ms
12 0.so-3-0-0.XR2.MIA4.ALTER.NET (152.63.101.45) 54.572 ms 93.893 ms 54.894 ms
13 176.ATM5-0.GW1.MIA4.ALTER.NET (146.188.233.165) 54.451 ms 54.673 ms 54.720 ms
14 208.255.246.1 (208.255.246.1) 58.944 ms 61.131 ms 60.336 ms
15 * * *
16 * * *

Sorry :(

You guys better watch it with those traceroutes. They are going to contact your provider saying you are running portscans on them....

Originally posted by Dilhole
You guys better watch it with those traceroutes. They are going to contact your provider saying you are running portscans on them....

Who cares? You can go to traceroute.org and traceroute from thousands different locations! This would give them a hard time to contact all providers :emlaugh:
BUT, it leaves the fact that i can not contact my server from anywhere contracted last week (5 days ago), nobody is reachable and i will cancel the contract next week, sad, sad :rolleyes:

Lmao - I'll let ya know if they do.

The traceroutes didn't get through, so they can hardly classify them as portscans.

Anybody else on this forum having a dedicated with them?
Let me know if yes and if it's reachable. PM me your IP so that i can check.
It's now nearly 9 hours down and no tech :(
Thanks

microsol,

WHAT ARE YOU TALKING ABOUT!!!

We have not heard from you since Feb 17th, 2002 @ 5:44 PM.
(The same day you posted this thread)

When you stated, "We where redesigning some stylesheets when all the sudden we couln't contact anymore."

Before this, you where asking about how to modify the kernel.
(Which you can do anything you wish to the OS, since this is a self managed server.)
Along with other software you had compiled on the server.

When we looked at the server it had a configuration error on the screen, and we rebooted ther server for you.
This was the last technical request we received from you.

Also in your welcome kit, it NOTED that ICMP is blocked at the router (showing at 208.255.246.1), and PING's do NOT work.

Also included on your welcome kit contained an emergency e-mail address and a 24/7/365 local number number.

If you are having connectivity or hardware problems, please refer to your welcome kit, which will have our technical contact information (e-mail and phone).

As you can see on the date and state in your last post, this thread is old :rolleyes:
Anyway, we did not modify the kernel nor did we ask you to do so. All we asked for was for a copy of the kernel-headers rpm as we had to install gcc and other stuff which comes normally with an dedicated server installation ;)

Yes, and we offered to install them, but you declined.
You had mentioend you would download them and install them yourself's.

For some reason gcc did not install when we did the standrd RedHat 7.2 install on your box.

Also if you remember you declined on the server contract to allow any tech support logins on your box for troubleshooting.

You do have all of our contact information included in the welcome kit, correct?

If not, please let us know, and we can resend it to you again. :)

Originally posted by Awebhosting
Yes, and we offered to install them, but you declined.
You had mentioend you would download them and install them yourself's.
For some reason gcc did not install when we did the standrd RedHat 7.2 install on your box.

:eek:
We installed all required software, dozends of perl modules, basic services and so gcc successful.

You do have all of our contact information included in the welcome kit, correct?

If not, please let us know, and we can resend it to you again. :)

Yes, this information was in one of the emails.

Just to say ONE thing: I bought for my company a server in mid february. Since then: NO PROBLEM. Traceroute fails every time (firewall I think) but VERY GOOD connectivity. WE even think at buying 3/4 more servers from them.

David was my contact and was very keen and helpful...

BUT: I'm not doing shared hosting on a $99 server and expect it to host 999999999 websites. Perhaps that's the difference.