It turns out that by default TELNET was not packaged with Windows 7. Apparently this was also true for Windows Vista.
Telnet is known to be insecure and so by default, Microsoft now DISABLES any likely security holes. Whenever you can, you should always use SSH.
That being said, you can enable Telnet this way:
Programs And Features
Turn Windows features on or off
Check Telnet Client
After that you can start Telnet via the "CMD" - Command Prompt.
I get these errors regularly in the Windows Server 2003 Event Log: Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Time: 4:37:05 PM
DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.
Article: "Google Chrome: The Official Start of the Cloud Era"
Author Lawrence Walsh says: "Google Chrome is being dismissed by competitors and analysts, but it may just be the official beginning of the cloud computing era by freeing users from big, heavy PCs and operating systems."