SmoothDesigners

3DES – Triple Digital Encryption Standard
ACL – Access Control List
AES - Advanced Encryption Standard
AES256 – Advanced Encryption Standards 256bit
AH - Authentication Header
ALE - Annualized Loss Expectancy
ARO - Annualized Rate of Occurrence
ARP - Address Resolution Protocol
AUP - Acceptable Use Policy
BIOS – Basic Input / Output System
BOTS – Network Robots
CA – Certificate Authority
CAN - Controller Area Network
CCTV - Closed-circuit television
CHAP – Challenge Handshake Authentication Protocol
CRL – Certification Revocation List
DAC – Discretionary Access Control
DDOS – Distributed Denial of Service
DES – Digital Encryption Standard
DHCP – Dynamic Host Configuration Protocol
DLL - Dynamic Link Library
DMZ – Demilitarized Zone
DNS – Domain Name Service (Server)
DOS – Denial of Service
EAP - Extensible Authentication Protocol
ECC - Elliptic Curve Cryptography
FTP – File Transfer Protocol
GRE - Generic Routing Encapsulation
HIDS – Host Based Intrusion Detection System
HIPS – Host Based Intrusion Prevention System
HTTP – Hypertext Transfer Protocol
HTTPS – Hypertext Transfer Protocol over SSL
HVAC – Heating, Ventilation Air Conditioning
ICMP - Internet Control Message Protocol
ID – Identification
IM - Instant messaging
IMAP4 - Internet Message Access Protocol v4
IP - Internet Protocol
IPSEC – Internet Protocol Security
IRC - Internet Relay Chat
ISP – Internet Service Provider
KDC - Key Distribution Center
L2TP – Layer 2 Tunneling Protocol
LANMAN – Local Area Network Manager
LDAP – Lightweight Directory Access Protocol
MAC – Mandatory Access Control / Media Access Control
MAC - Message Authentication Code
MAN - Metropolitan Area Network
MD5 – Message Digest 5
MSCHAP – Microsoft Challenge Handshake Authentication
Protocol
MTU - Maximum Transmission Unit
NAC – Network Access Control
NAT – Network Address Translation
NIDS – Network Based Intrusion Detection System
NIPS – Network Based Intrusion Prevention System
NOS – Network Operating System
NTFS - New Technology File System
NTLM – New Technology LANMAN
NTP - Network Time Protocol
OS – Operating System
OVAL – Open Vulnerability Assessment Language
PAP – Password Authentication Protocol
PAT - Port Address Translation
PBX – Private Branch Exchange
PGP – Pretty Good Privacy
PII – Personally Identifiable Information
PKI – Public Key Infrastructure
PPP - Point-to-point Protocol
PPTP – Point to Point Tunneling Protocol
RAD - Rapid application development
RADIUS – Remote Authentication Dial-in User Server
RAID – Redundant Array of Inexpensive Disks
RAS – Remote Access Server
RBAC – Role Based Access Control
RBAC – Rule Based Access Control
RSA – Rivest, Shamir, & Adleman
S/MIME – Secure / Multipurpose internet Mail Extensions
SCSI - Small Computer System Interface
SHA – Secure Hashing Algorithm
SHTTP – Secure Hypertext Transfer Protocol
SLA – Service Level Agreement
SLE - Single Loss Expectancy
SMTP – Simple Mail Transfer Protocol
SNMP - Simple Network Management Protocol
SPIM - Spam over Internet Messaging
SSH – Secure Shell
SSL – Secure Sockets Layer
SSO – Single Sign On
STP – Shielded Twisted Pair
TACACS – Terminal Access Controller Access Control System
TCP/IP – Transmission Control Protocol / Internet Protocol
TKIP - Temporal Key Integrity Protocol
TKIP – Temporal Key Interchange Protocol
TLS – Transport Layer Security
TPM – Trusted Platform Module
UPS - Uninterruptable Power Supply
URL - Universal Resource Locator
USB – Universal Serial Bus
UTP – Unshielded Twisted Pair
VLAN – Virtual Local Area Network
VoIP - Voice over IP
VPN – Virtual Private Network
WEP – Wired Equivalent Privacy
WPA – Wi-Fi Protected Access

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate the following registry key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
4. To change the company name, do the following:

   In the right pane, double-click RegisteredOrganization. Under Value data, type the name that you want, and then click OK.

5. To change the name of the registered owner, do the following:

   In the right pane, double-click RegisteredOwner. Under Value data, type the name that you want, and then click OK.

6. Click Exit on the File menu to quit Registry Editor.

You can use a web.config file with the following:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

<configuration>
    <system.webServer>
        <staticContent>
            <mimeMap fileExtension=".EXTENSION" mimeType="MIME/TYPE" />
     </staticContent>
    </system.webServer>
</configuration>
 
Example:
<configuration>
    <system.webServer>
        <staticContent>
            <mimeMap fileExtension=".test" mimeType="text/html" />
     </staticContent>
    </system.webServer>
</configuration>

General

Bplans.com: Business Plan Information
CCH: Business Owner’s Toolkit
FindLaw.com
Gigalaw.com: Legal Information for Internet Professionals
IRS (United States)
King and Spalding: Useful Links
Law for Internet
Legally, Whose Web Site Is It Anyway? by Jeffrey W. Rose, Attorney
MyCorporation.com
Small Business Administration (United States)

Australian

Australian Law Online
National Library of Australia: Australian Law on the Internet
Oznetlaw

Documents

AllBusiness.com: Forms and Agreements
Legal Forms Kit (Some Free)

Free Legal Advice

FreeAdvice
LawStreet.com

Trademarks and Copyrights

Copyright Articles for Web Site Designers and Site Owners by Ivan Hoffman, B.A., J.D. Attorney
Gregory H. Guillot: All About Trademarks
Nolo: Getting Permission to Publish: Ten Tips for Webmasters
PlagiarismToday
Trademark Center: Trademark Search

Here is a rundown of what happened to our server over the last few days.

—————

This evening at 4:55pm CDT in our H1 data center, electrical gear shorted, creating an explosion and fire that knocked down three walls surrounding our electrical equipment room. Thankfully, no one was injured. In addition, no customer servers were damaged or lost.

We have just been allowed into the building to physically inspect the damage. Early indications are that the short was in a high-volume wire conduit. We were not allowed to activate our backup generator plan based on instructions from the fire department.

This is a significant outage, impacting approximately 9,000 servers and 7,500 customers. All members of our support team are in, and all vendors who supply us with data center equipment are on site. Our initial assessment, although early, points to being able to have some service restored by mid-afternoon on Sunday. Rest assured we are working around the clock.

—————-

As previously committed, I would like to provide an update on where we stand following yesterday’s explosion in our H1 data center. First, I would like to extend my sincere thanks for your patience during the past 28 hours. We are acutely aware that uptime is critical to your business, and you have my personal commitment that The Planet team will continue to work around the clock to restore your service.

As you have read, we have begun receiving some of the equipment required to start repairs. While no customer servers have been damaged or lost, we have new information that damage to our H1 data center is worse than initially expected. Three walls of the electrical equipment room on the first floor blew several feet from their original position, and the underground cabling that powers the first floor of H1 was destroyed.

There is some good news, however. We have found a way to get power to Phase 2 (upstairs, second floor) of the data center and to restore network connectivity. We will be powering up the air conditioning system and other necessary equipment within the next few hours. Once these systems are tested, we will begin bringing the 6,000 servers online. It will take four to five hours to get them all running.

We have brought in additional support from Dallas to have more hands and eyes on site to help with any servers that may experience problems. The call center has also brought in double staff to handle the increase in tickets we’re expecting. Hopefully by sunrise tomorrow Phase 2 will be well on its way to full production.

Let me next address Phase 1 (first floor) of the data center and the affected 3,000 servers. The news is not as good, and we were not as lucky. The damage there was far more extensive, and we have a bigger challenge that will require a two-step process. For the first step, we have designed a temporary method that we believe will bring power back to those servers sometime tomorrow evening, but the solution will be temporary. We will use a generator to supply power through next weekend when the necessary gear will be delivered to permanently restore normal utility power and our battery backup system. During the upcoming week, we will be working with those customers to resolve issues.

—————-

Late last night, I told you we hoped to have power to the 6,000 servers in Phase 2 of our H1 data center by midnight, with all servers up by early morning. I am glad to say we came close, just a few hours after sunrise. At this time, 100% of our servers in Phase 2 have power, and our technicians are working with customers on any remaining server issues. We are confident all remaining issues will be resolved shortly.

I also explained the significant challenge we faced in the other phase where the actual explosion occurred. Our team came up with a creative way to restore power quicker than the 4-5 day outage. We decided not to wait for equipment for the electrical room completely, opting instead for a temporary solution to get power to the 3,000 servers. That solution involves using generator power for the next 10 -12 days until all the new equipment arrives to rebuild the electrical room for Phase 1. I explained that we expected to have a temporary solution in place by midnight tonight, with servers powered up tomorrow. The good news is that as you read this letter, the power is restored, and the temporary solution is in effect. Within the next two hours, the remaining 3,000 servers have power. We have overstaffed our data centers again to help during this initial power up.

This now leaves us facing step two of this process, which requires getting all of the equipment delivered and then rebuilding the electrical room to its original standard. To make the cutover to the rebuilt electrical room, the operations group believed it would take a maintenance outage of 24-48 hours. I have good news on that front. It’s not perfect, but at present we now believe the maintenance window will be just 4-6 hours. That’s still too long, and we will continue this week to find ways to reduce the time. Given that there will be some outage for the cutover, we will execute this step at midnight on a Saturday, either June 7 or June 14. We want to pick the most appropriate time to minimize impact to you.

I must admit that I am amazed. We are almost 18 hours ahead of schedule with this phase, thanks to our great suppliers and of course the great folks working here at The Planet. This could never have happened without the help of both, and I want to thank all of them.

There is still more work to do, but the progress is terrific. We will continue to work any and all customer issues, and we face the challenge of putting the permanent power fix in place for Phase 1. Nonetheless, there is still good news based on what I told you last night.

————————–
(The Server was up from around 3:30pm till 2:20am)
————————–

Around 2:20 AM CDT, the backup generator being used to power H1 Phase | experienced an electrical issue resulting in service loss for Phase I; Phase II remains unaffected at this time. Our data center operations and facilities teams immediately began investigating the cause of the failure to restore power to the Computer Room Air Conditioner (CRAC) units and Power Distribution Units (PDUs) for Phase I.

The staff successfully tested the 2 megawatt generator without load, so they began powering up the CRAC units and PDUs to restore service to Phase I. While working through this power restoration, the generator’s breakers were tripped by their internal electronics. The generator is rated to handle more than the load required to power the phase, and the generator itself is fully functional, but the breaker system must be replaced to guarantee stable power distribution.

We have attempted to locate a replacement generator and are evaluating the time necessary to repair the breakers on the current generator so we can restore power as quickly as possible. We do not have an ETA for power restoration, but we will be updating you hourly with our current status or sooner, as developments warrant.

——–

Fixing the faulty breaker on the generator powering H1 Phase 1 was not successful. we have located a second generator that is currently being delivered to the facility. It is expected to arrive this afternoon and we will provide additional information regarding the new generator at that time.