| Author |
Tue W2K Professional Question of the Day
|
|
| wbafrank 2002-07-09, 6:46 pm |
|  And today's poser is ....
Q9. Alison has 30 computers running Windows 2000 Professional configured as DHCP clients. The DHCP Server is a RedHat Linux 7.3 Box and is located on the same subnet. Sometimes these Windows 2000 Professional clients do not recieve IP Address information from the RedHat 7.3 DHCP Server and instead assign themselves IP Address information via APIPA.
When this happens these Windows 2000 Professional clients cannot communicate with ANY other computers on the network except other Windows 2000 Professional clients with APIPA derived IP Address Information.
Alison would like to disable APIPA on these workstations, which of the following is the correct method of doing this?
A. There currently is no way to disable Automatic Private IP Addressing in Windows 2000. The best solution to the problem would be to remove the non- Windows 2000 DHCP Server.
B. In the TCP/IP Properties for the network adapter configured as a DHCP client, change the setting for "Obtain an IP Address Automatically" to "No".
C. Change the value of the PopupFlag value in the following registry key from 00 to 01:
HKEY_CURRENT_USER\USER\Current
ControlSet\Services\VxD\DHCP
D. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\Curr
entControlSet\Services\ Tcpip\Parameters\Interfaces\ad
apter_name
Add an entry for IPAutoconfigurationEnabled: REG_DWORD and assign it a value of 0.
Good Luck .... see you tomorrow for the answer!! | |
| markmyrie 2002-07-09, 7:26 pm |
| Damn, I got to get studying----->> no clue!! | |
| philly54ab 2002-07-09, 7:36 pm |
| I would suggest changing the automatc update to a static one. You have to input the actual address of the server to go too. | |
| Deja-vue 2002-07-09, 8:18 pm |
| Ha! D! final Answer!
Win 95 and 98 use the DHCP until the lease expires. Then loses connections.
Win 2000, after losing the DHCP Server,assigns itself the APIPA.The range is from 169.254.0.0 to 169.254.255.255, i think.(correct me if i'm wrong here).
The only way to disable APIPA is the Registry-hack mentioned above! | |
| denis_baribeau 2002-07-09, 8:41 pm |
| Yep ( D ) for sure
Answer C would apply to windows 98 | |
|
|
| NetChild1985 2002-07-10, 1:34 am |
| Agree with "D"! | |
| Surender 2002-07-10, 7:35 am |
| d | |
|
|
| robertmillar 2002-07-10, 1:33 pm |
| D | |
| Gareth Leung 2002-07-10, 2:31 pm |
| D | |
| Deja-vue 2002-07-10, 6:51 pm |
| Alison seems to be a busy woman these days.
| |
| wbafrank 2002-07-11, 9:35 am |
| quote:
Originally posted by wbafrank
And today's poser is ....
Q9. Alison has 30 computers running Windows 2000 Professional configured as DHCP clients. The DHCP Server is a RedHat Linux 7.3 Box and is located on the same subnet. Sometimes these Windows 2000 Professional clients do not recieve IP Address information from the RedHat 7.3 DHCP Server and instead assign themselves IP Address information via APIPA. When this happens these Windows 2000 Professional clients cannot communicate with ANY other computers on the network except other Windows 2000 Professional clients with APIPA derived IP Address Information. Alison would like to disable APIPA on these workstations, which of the following is the correct method of doing this?
A. There currently is no way to disable Automatic Private IP Addressing in Windows 2000. The best solution to the problem would be to remove the non- Windows 2000 DHCP Server.
B. In the TCP/IP Properties for the network adapter configured as a DHCP client, change the setting for "Obtain an IP Address Automatically" to "No".
C. Change the value of the PopupFlag value in the following registry key from 00 to 01:
HKEY_CURRENT_USER\USER\Current
ControlSet\Services\VxD\DHCP
D. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\Curr
entControlSet\Services\ Tcpip\Parameters\Interfaces\ad
apter_name
Add an entry for IPAutoconfigurationEnabled: REG_DWORD and assign it a value of 0.
And the answer is ....
Correct Answer: D
Windows 2000 uses Automatic Private IP Addressing (APIPA) to automate Internet Protocol (IP) configuration of network connections. To disable this feature, perform the following steps:
1. Open Registry Editor
2. In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\Curr
entControlSet\ Services\Tcpip\Parameters\Inte
rfaces\adapter_name
3. Create the following entry:
IPAutoconfigurationEnabled: REG_DWORD
4. Assign a value of 0 to disable Automatic Private IP Addressing (APIPA) support for the selected network adapter.
As with all questions on MS exams - you never know exactly what level of detail is going to be required. The big hint between the two Registry options though is that one is USER and the other is SYSTEM. You should know the basics of what the main registry hives are used for:
HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE
HKEY_USERS
HKEY_CURRENT_CONFIG
You won't really be expected to know anything more than this. A generalized understanding of the registry hives is helpful - but you don't need to memorize all of the underlying detail. | |
| enforcer 2002-07-12, 4:03 pm |
| I can't thank you enough for this one WBAfrank, this was a problem i've been having on my home network, i kept turning the workstation on too soon after the server and it kept using the apipa, and it was annoying the hell out of me.
Thanks |
|
|
|
