Event ID 1001, DHCP Client Lease Validity?

Probably this error is pretty much a non-issue and I haven't a clue if the affected W7P machine, even runs Windows Server 2008 R2 (or any windows server for that matter).Is this 'server' thing, software that is by default installed (and I'm guessing it's only used when the machine networks with another machine, home/work groups)?As for if and what version the W7P machine even 'runs', the only loosely provided instructions I've found (by clicking the event log's link to information about the error), results in a webpage... Event ID 1001 ..which sort of implies to me that the W7P machine might be running 'Windows Server 2008 R2', if only because the event log error report's link led me to that web page's article, ie; the article says it applies to Windows Server 2008 R2.I tried following the article's mentions of checking to see what version of 'server' that is installed, but step 2 seems too poorly written for me to follow what's actually be said...Determine if there is a network connectivity problem To determine if there is a network connectivity problem between the‚ DHCP‚ server and domain controller: At the DHCP server, click Start, click Run, type cmd, and then click OK. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the domain controller (for example, server1.contoso.com), and then press ENTER. What's unclear to me is where it alludes to..."..where server_FQDN is the fully qualified domain name (FQDN) of the domain controller"...I see the article provides an example, but the example seems as obscure as it's parent reference.How does a user determine the "fully qualified domain name (FQDN) of the domain controller"?If that obscurity isn't bad enough, the article then lists a second step "1" stating..."At the command prompt, type ping IP_address, where IP_address is the IP address of the domain controller, and then press ENTER."..and again I haven't a clue as to what's being said, ie; we're not born with a 'domain controller's IP address' tattooed on our forehead, so how's that detail determined?Further down in the article, it lists a step 4 stating..."Type ping IP_address, where IP_address is the IP address assigned to the computer. If you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver. " ..and step 5 states..."Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers."..and as the article doesn't detail how to determine the machine's 'IP Address' and doesn't detail how to determine 'P address assigned to the DNS server', again I'm left reading an otherwise virtually useless article.