“Fail to see Active Directory” DHCP Error 1059
Where are you from, Frank? If you're in the US, Virgin Mobile will start selling iPhone 4 and 4S'es for prepaid customers at the end of this month (June 29, as they say).
They'll be selling them through the Sprint Network, RadioShack and Best Buy. The only surcharge they announced was a $15.00/mo flat fee to unlock the tethering feature.
Plans start at $30.00/mo and no, they are not on a contract basis — after all, this is what prepaid services are all about, isn't it? You will, however, have to reach deeper into your pocket to buy the terminal, as the retail prices are of $549.00 for the 8 GB iPhone 4 and $649.00 for the 16 GB iPhone 4S.
To resolve this issue, identify and fix any network connectivity problems between the DHCP server and domain controller by doing the following:
Determine if there is a network connectivity problem by using the ping command.
Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem.
To perform these tasks, refer to the following sections.
Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
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.
If the ping was successful, you will receive a reply similar to the following:
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=20ms TTL=59
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=6ms TTL=59
At the command prompt, type ping IP_address, where IP_address is the IP address of the domain controller, and then press ENTER.
If you can successfully ping the domain controller by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.
If you cannot successfully ping the domain controller by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.
