Web sites and/or the servers on which they reside do occasionally go down. BigBytes Internet runs monitoring software that alerts us at the first sign that one of our web servers is not responding, and a network engineer is immediately dispatched to investigate the problem.
However, if you notice that you cannot access your site, here are some simple steps you should perform before contacting support to report an outage:
Define the nature of the problem.
Can you view your site with a browser? Is the problem limited to uploading or publishing your web site, accessing email or only a certain service of your web site? What error messages are you getting? This info will help BigBytes support more effectively assist you with the problem.
Take a quick inventory of what has changed.
Jot down a quick list of anything that might have changed on your PC or your local network since you were last able to successfully access your site.
Check your domain status via WHOIS
Look up your domain at Network Solutions or via our domain lookup utility. Are BigBytes Internet's DNS Servers listed on your domain record? You should see NSx.BIGBYTES.NET and NSx.BIGBYTES.NET (x represents a number) listed as your DNS Servers. If not, and you are a new customer, your domain transfer is still in process.
Check the last date your domain record was updated
Oops. Are you close to your annual domain registration renewal date? If your domain record was recently updated (look for the "last updated" line of the record and check the date), it is possible that your domain is on hold for an outstanding annual renewal payment. You will need to contact your domain registrar to determine if there is an outstanding annual renewal fee due for your domain name.
Ping your web site address
"Pinging" sends a request to a remote web server (such as the one where your web site resides) and listens for a reply. See below for instructions on how to "ping" your site. Send your "ping" results to support@bigbytes.net
Traceroute to your web site.
Like using the ping command, a "traceroute" sends a request to your web site and listens for a reply. A traceroute will track every step necessary to connect from your computer to your web site. It will give you a list of all the ISP routers and IP addresses that your request travels through to access your web site. It can help determine if your web site is down, or the problem is a router or connection somewhere on the Internet between you and your web site. See below for instructions on how to "traceroute" to your site. Send your "traceroute" results to support@bigbytes.net
Are your behind a Proxy Server or Firewall?
Check with your company's network administrator to see if you are connecting to the Internet through a proxy server or firewall. If so, BigBytes support will need this information to assist you and more quickly identify the problem you are experiencing.
Have you recently transferred your domain name to BigBytes?
Make sure that your old ISP has completely disabled your old web hosting account and removed your domain from their DNS records. If your old ISP has not removed your account, you may not be able to access your new account. Also try dumping your web browser's cache and rebooting your computer.
Send us your error messages and traceroute results
You can submit a trouble ticket and receive an incident tracking number via our Online Help Desk
WHAT ERROR MESSAGE ARE YOU GETTING?
Error Message: "The server does not have a DNS entry" (Netscape) or "A connection with the server could not be established" (Internet Explorer)
Explanation: The domain name is not being resolved.
Possible reasons:
Your domain name registration has not been completed by the InterNIC.
Your domain name has been registered, but the name has not propagated through the main root servers on the Internet. Wait 24-72 hours and your domain should then be working.
Your computer has lost the connection to your Internet Service Provider. Make sure your are connected to your ISP.
You are connected to your ISP, but there is a problem with their DNS servers. If you cannot reach many sites this is probably the problem.
You are connected to your ISP but there is a routing problem somewhere between you and us. Tips on how to diagnose this are below.
Error Message: "There was no response. The server could be down or not responding" (Netscape) or "A connection with the server could not be established" (Internet Explorer)
Explanation: No connection could be made to the server.
Possible reasons:
You are not connected to your Internet Service Provider. Check your connection to your ISP.
You are connected to your Internet Service Provider but there is a routing problem somewhere between you and us. Tips on how to diagnose this are below.
The web server could be down. Check our network notices page.
Your individual web site could be down. This can happen on a Microsoft® FrontPage® enabled web sites if your connection to the web server did not terminate properly after publishing to your web site. This can also happen if an error occurs while publishing with Visual Interdev.
HOW TO USE PING TO DETERMINE THE IP ADDRESS OF YOUR WEB SITE
Use the "ping" command that is available in Windows 95, 98 and Windows NT. This allows you to ping your web site and receive a reply that includes the IP address of your site.
In Windows, click on the START button
Click PROGRAMS
Locate and Click on MS-DOS prompt (or COMMAND PROMPT depending upon your version of Windows)
Type the following command at the prompt:
ping www.yourwebsite.com
Send the results of your ping to BigBytes Support
Here's an example of a successful ping to www.bigbytes.net:
C:\\>ping www.bigbytes.net
Pinging www.bigbytes.net [216.180.250.190] with 32 bytes of data:
Reply from 216.180.250.190: bytes=32 time=10ms TTL=126
Reply from 216.180.250.190: bytes=32 time<10ms TTL=126
Reply from 216.180.250.190: bytes=32 time=10ms TTL=126
Reply from 216.180.250.190: bytes=32 time=10ms TTL=126
Ping statistics for 216.180.250.190
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 7ms
HOW TO DIAGNOSE A ROUTING PROBLEM USING TRACERT
Use the "tracert" command that is available in Windows 95, 98 and Windows NT. This allows you to trace the route over the internet from you to BigBytes.
In Windows, click on the START button
Click PROGRAMS
Locate and Click on MS-DOS prompt (or COMMAND PROMPT depending upon your version of Windows)
Type the following command at the prompt:
tracert www.yourwebsite.com
Here's an example of a successful tracert to www.bigbytes.net:
C:\\>tracert www.bigbytes.net
Tracing route to bigbytes.net [216.180.250.190]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.127
2 46 ms 46 ms 46 ms 210.213.156.1.pldt.net [210.213.156.1]
3 51 ms 46 ms 46 ms 210.1.65.73
4 49 ms 46 ms 46 ms 210.14.0.34
5 45 ms 46 ms 46 ms 210.14.0.9
6 232 ms 234 ms 234 ms POS5-3.IG3.SAC1.ALTER.NET [157.130.214.149]
7 224 ms 234 ms 234 ms 0.so-0-1-0.XR2.SAC1.ALTER.NET [152.63.54.126]
8 228 ms 234 ms 234 ms 0.so-0-0-0.XL2.SAC1.ALTER.NET [152.63.54.1]
9 223 ms 234 ms 234 ms 0.so-6-0-0.XL2.SCL2.ALTER.NET [152.63.54.129]
10 545 ms 859 ms 686 ms 0.so-6-0-0.BR1.SCL2.ALTER.NET [152.63.57.49]
11 232 ms 234 ms 234 ms 204.255.168.70
12 233 ms 249 ms 234 ms so-4-3-0.mpr4.sjc2.us.above.net [64.125.30.85]
13 264 ms 263 ms 265 ms so-2-3-0.cr1.dfw2.us.above.net [64.125.29.50]
14 274 ms 281 ms 281 ms so-3-1-0.mpr1.iah1.us.above.net [64.125.30.229]
15 279 ms 281 ms 281 ms so-0-0-0.mpr2.iah1.us.above.net [64.125.31.62]
16 295 ms 296 ms 296 ms so-4-0-0.mpr1.atl6.us.above.net [64.125.29.69]
17 295 ms 296 ms 296 ms so-0-0-0.mpr2.atl6.us.above.net [64.125.27.50]
18 295 ms 296 ms 296 ms 64.124.11.26.available.above.net [64.124.11.26]
19 310 ms 312 ms 312 ms gig0-1.l3-atl-1.gnax.net [209.51.131.6]
20 311 ms 312 ms 296 ms 216.180.250.190
Trace complete.
If there is a routing problem on the Internet that is beyond the control of you or us, you might see results like this:
Tracing route to bigbytes.net [216.180.250.190]
1 <1 ms <1 ms <1 ms 192.168.0.127
2 46 ms 46 ms 46 ms 210.213.156.1.pldt.net [210.213.156.1]
3 51 ms 46 ms 46 ms 210.1.65.73
4 49 ms 46 ms 46 ms 210.14.0.34
5 45 ms 46 ms 46 ms 210.14.0.9
6 232 ms 234 ms 234 ms POS5-3.IG3.SAC1.ALTER.NET [157.130.214.149]
7 * * *
8 * * *
9 * * *
10 * * * (etc... repeated many times)
Results such as above could indicate excessive Internet traffic at an exchange point, a routing problem, a fiber cut, or some other severed link between you and us. You'll notice that the tracert stops before it reaches BigBytes's network. In this case, the connection failed just beyond ALTER.NET (ms POS5-3.IG3.SAC1.ALTER.NET).
If the problem appears to be somewhere between us and you, unfortunately there's probably not much either of us can do about it other than to wait for it to clear up.
If the problem appears to be with your ISP's network, you may want to notify them of the condition so that they can take corrective measures.
If the problem is within our network and involves connectivity to all of our web servers, we most likely already know about it because of our network and connectivity monitoring systems.
If the problem appears to be just your web site (and BigBytes's site, other sites hosted by BigBytes and/or other sites on the Internet are reachable), you may need to contact us to restart your individual virtual web.
