crm-serv
asked on
Connectivity to server lost after successfully joining domain
I am running Vista Business on Dell laptop with it set to use DHCP. TCP/IP configuration from DHCP works fine. When I join it to a Win2k domain and reboot Vista reports it cannot find a domain server for authentication. At that point TCP/IP has an APIPA address and no connectivity.
Configuring a fixed IP address connectivity resumes and I can authenticate on the domain controller.
After reading many EE posts and solutions I have not found a solution for my problem.
How can I use DHCP with Vista Business?
Thanks for your help with this.
Configuring a fixed IP address connectivity resumes and I can authenticate on the domain controller.
After reading many EE posts and solutions I have not found a solution for my problem.
How can I use DHCP with Vista Business?
Thanks for your help with this.
ASKER
WinXP PCs are able to connect with no problem, that is, they receive the correct TCP/IP info from DHCP.
The primary DC is running Win2k in native mode. There is a secondary DC running Longhorn. Both have been on line when the laptop failure to obtain addressing has occurred.
DNS is setup with an integrated AD zone.
The Vista laptop is able to get IP settings from DHCP when it is a workgroup member. This changes after joining the domain.
The primary DC is running Win2k in native mode. There is a secondary DC running Longhorn. Both have been on line when the laptop failure to obtain addressing has occurred.
DNS is setup with an integrated AD zone.
The Vista laptop is able to get IP settings from DHCP when it is a workgroup member. This changes after joining the domain.
ASKER
Correction: I have just retested the behavior when the laptop is in a workgroup and it is not getting correct IP setup from DHCP.
That is a change from the original behavior when in a workgroup.
That is a change from the original behavior when in a workgroup.
I'd start by disabling the IPv6 interface on the Vista PC.... and see if that fixes it.
Here is a (rather long) article about Vista and IPv6 http://www.microsoft.com/technet/community/columns/cableguy/cg1005.mspx
Here is a (rather long) article about Vista and IPv6 http://www.microsoft.com/technet/community/columns/cableguy/cg1005.mspx
ASKER
I disabled IPv6 and set connection to "get address automatically".
I logged on with a domain account ( using cached credentials ) and found that ipconfig still shows an APIPA address when set to 'automatic' for the connection I am using.
I have read that Vista has a very short time out set for checking for a DHCP server compared to WinXP. Is there a way to configure the time out value?
I logged on with a domain account ( using cached credentials ) and found that ipconfig still shows an APIPA address when set to 'automatic' for the connection I am using.
I have read that Vista has a very short time out set for checking for a DHCP server compared to WinXP. Is there a way to configure the time out value?
Hummm.... let's try this. Go to the registry and post the values you find at the following key:
HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Se rvices\Tcp ip\Paramet ers\Interf aces\{0611 63D3-03CF- 41E6-820C- B54C8D0882 D0}
(note, the actual GUID might be different on your PC). It should look something like this:
[HKEY_LOCAL_MACHINE\SYSTEM \CurrentCo ntrolSet\S ervices\Tc pip\Parame ters\Inter faces\{061 163D3-03CF -41E6-820C -B54C8D088 2D0}]
"UseZeroBroadcast"=dword:0 0000000
"EnableDeadGWDetect"=dword :00000001
"EnableDHCP"=dword:0000000 1
"NameServer"=""
"Domain"=""
"RegistrationEnabled"=dwor d:00000001
"RegisterAdapterName"=dwor d:00000000
"DhcpIPAddress"="192.168.0 .6"
"DhcpSubnetMask"="255.255. 255.0"
"DhcpServer"="192.168.0.1"
"Lease"=dword:00015180
"LeaseObtainedTime"=dword: 46a9d9a9
"T1"=dword:46aa8269
"T2"=dword:46aaf889
"LeaseTerminatesTime"=dwor d:46ab2b29
"AddressType"=dword:000000 00
"IsServerNapAware"=dword:0 0000000
"DhcpConnForceBroadcastFla g"=dword:0 0000001
"DhcpInterfaceOptions"=hex :fc,00,00, 00,00,00,0 0,00,00,00 ,00,00,00, 00,00,00,2 2,\
da,a9,46,06,00,00,00,00,00 ,00,00,04, 00,00,00,0 0,00,00,00 ,29,2b,ab, 46,c0,a8,\
00,01,03,00,00,00,00,00,00 ,00,04,00, 00,00,00,0 0,00,00,29 ,2b,ab,46, c0,a8,00,\
01,33,00,00,00,00,00,00,00 ,04,00,00, 00,00,00,0 0,00,29,2b ,ab,46,00, 01,51,80,\
3b,00,00,00,00,00,00,00,04 ,00,00,00, 00,00,00,0 0,29,2b,ab ,46,00,01, 1e,e0,3a,\
00,00,00,00,00,00,00,04,00 ,00,00,00, 00,00,00,2 9,2b,ab,46 ,00,00,a8, c0,01,00,\
00,00,00,00,00,00,04,00,00 ,00,00,00, 00,00,29,2 b,ab,46,ff ,ff,ff,00, 36,00,00,\
00,00,00,00,00,04,00,00,00 ,00,00,00, 00,29,2b,a b,46,c0,a8 ,00,01,35, 00,00,00,\
00,00,00,00,01,00,00,00,00 ,00,00,00, 29,2b,ab,4 6,05,00,00 ,00
"IPAutoconfigurationAddres s"="0.0.0. 0"
"DhcpNameServer"="192.168. 0.1"
"DhcpDefaultGateway"=hex(7 ):31,00,39 ,00,32,00, 2e,00,31,0 0,36,00,38 ,00,2e,00, 30,\
00,2e,00,31,00,00,00,00,00
"DhcpSubnetMaskOpt"=hex(7) :32,00,35, 00,35,00,2 e,00,32,00 ,35,00,35, 00,2e,00,3 2,\
00,35,00,35,00,2e,00,30,00 ,00,00,00, 00
HKEY_LOCAL_MACHINE\SYSTEM\
(note, the actual GUID might be different on your PC). It should look something like this:
[HKEY_LOCAL_MACHINE\SYSTEM
"UseZeroBroadcast"=dword:0
"EnableDeadGWDetect"=dword
"EnableDHCP"=dword:0000000
"NameServer"=""
"Domain"=""
"RegistrationEnabled"=dwor
"RegisterAdapterName"=dwor
"DhcpIPAddress"="192.168.0
"DhcpSubnetMask"="255.255.
"DhcpServer"="192.168.0.1"
"Lease"=dword:00015180
"LeaseObtainedTime"=dword:
"T1"=dword:46aa8269
"T2"=dword:46aaf889
"LeaseTerminatesTime"=dwor
"AddressType"=dword:000000
"IsServerNapAware"=dword:0
"DhcpConnForceBroadcastFla
"DhcpInterfaceOptions"=hex
da,a9,46,06,00,00,00,00,00
00,01,03,00,00,00,00,00,00
01,33,00,00,00,00,00,00,00
3b,00,00,00,00,00,00,00,04
00,00,00,00,00,00,00,04,00
00,00,00,00,00,00,04,00,00
00,00,00,00,00,04,00,00,00
00,00,00,00,01,00,00,00,00
"IPAutoconfigurationAddres
"DhcpNameServer"="192.168.
"DhcpDefaultGateway"=hex(7
00,2e,00,31,00,00,00,00,00
"DhcpSubnetMaskOpt"=hex(7)
00,35,00,35,00,2e,00,30,00
ASKER
graye, thanks for the help with this. I captured two versions of the Registry entries - 1) TCP/IP set to obtain address automatically and 2 ) with a fixed IP set. There are shown below by corresponding number just listed.
Version 1:
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Se rvices\Tcp ip \Parameters\Interfaces\{4C B26316-E95 5-4612-BA8 1-AE21AB99 960E} Class Name: <NO CLASS> Last Write Time: 7/28/2007 - 3:12 PM Value 0 Name: UseZeroBroadcast Type: REG_DWORD Data: 0
Value 1 Name: EnableDeadGWDetect Type: REG_DWORD Data: 0x1
Value 2 Name: EnableDHCP Type: REG_DWORD Data: 0x1
Value 3 Name: NameServer Type: REG_SZ Data:
Value 4 Name: Domain Type: REG_SZ Data:
Value 5 Name: RegistrationEnabled Type: REG_DWORD Data: 0x1
Value 6 Name: RegisterAdapterName Type: REG_DWORD Data: 0
Value 7 Name: DhcpServer Type: REG_SZ Data: 255.255.255.255
Value 8 Name: Lease Type: REG_DWORD Data: 0xa8c00
Value 9 Name: LeaseObtainedTime Type: REG_DWORD Data: 0x46a7add4
Value 10 Name: T1 Type: REG_DWORD Data: 0x46acf3d4
Value 11 Name: T2 Type: REG_DWORD Data: 0x46b0e854
Value 12 Name: LeaseTerminatesTime Type: REG_DWORD Data: 0x46b239d4
Value 13 Name: AddressType Type: REG_DWORD Data: 0
Value 14 Name: IsServerNapAware Type: REG_DWORD Data: 0
Value 15 Name: DhcpConnForceBroadcastFlag Type: REG_DWORD Data: 0x1
Value 16 Name: IPAutoconfigurationAddress Type: REG_SZ Data: 169.254.207.171
Value 17 Name: IPAddress Type: REG_MULTI_SZ Data:
Value 18 Name: SubnetMask Type: REG_MULTI_SZ Data:
Value 19 Name: DefaultGateway Type: REG_MULTI_SZ Data:
Value 20 Name: DhcpIPAddress Type: REG_SZ Data: 0.0.0.0
Value 21 Name: DhcpSubnetMask Type: REG_SZ Data: 255.0.0.0
Value 22 Name: ActiveConfigurations Type: REG_MULTI_SZ Data: Alternate_{4CB26316-E955-4 612-BA81-A E21AB99960 E}
Version 2:
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Se rvices\Tcp ip\Paramet ers\Interf aces\{4CB2 6316-E955- 4612-BA81- AE21AB9996 0E}
Class Name: <NO CLASS>
Last Write Time: 7/28/2007 - 2:14 PM
Value 0
Name: UseZeroBroadcast
Type: REG_DWORD
Data: 0
Value 1
Name: EnableDeadGWDetect
Type: REG_DWORD
Data: 0x1
Value 2
Name: EnableDHCP
Type: REG_DWORD
Data: 0
Value 3
Name: NameServer
Type: REG_SZ
Data: 192.168.0.2,4.2.2.1
Value 4
Name: Domain
Type: REG_SZ
Data:
Value 5
Name: RegistrationEnabled
Type: REG_DWORD
Data: 0x1
Value 6
Name: RegisterAdapterName
Type: REG_DWORD
Data: 0
Value 7
Name: DhcpServer
Type: REG_SZ
Data: 255.255.255.255
Value 8
Name: Lease
Type: REG_DWORD
Data: 0xa8c00
Value 9
Name: LeaseObtainedTime
Type: REG_DWORD
Data: 0x46a7add4
Value 10
Name: T1
Type: REG_DWORD
Data: 0x46acf3d4
Value 11
Name: T2
Type: REG_DWORD
Data: 0x46b0e854
Value 12
Name: LeaseTerminatesTime
Type: REG_DWORD
Data: 0x46b239d4
Value 13
Name: AddressType
Type: REG_DWORD
Data: 0
Value 14
Name: IsServerNapAware
Type: REG_DWORD
Data: 0
Value 15
Name: DhcpConnForceBroadcastFlag
Type: REG_DWORD
Data: 0x1
Value 16
Name: IPAutoconfigurationAddress
Type: REG_SZ
Data: 0.0.0.0
Value 17
Name: IPAddress
Type: REG_MULTI_SZ
Data: 192.168.0.20
Value 18
Name: SubnetMask
Type: REG_MULTI_SZ
Data: 255.255.255.0
Value 19
Name: DefaultGateway
Type: REG_MULTI_SZ
Data: 192.168.0.1
Value 20
Name: DhcpIPAddress
Type: REG_SZ
Data: 0.0.0.0
Value 21
Name: DhcpSubnetMask
Type: REG_SZ
Data: 255.0.0.0
Value 22
Name: ActiveConfigurations
Type: REG_MULTI_SZ
Data: Alternate_{4CB26316-E955-4 612-BA81-A E21AB99960 E}
Version 1:
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\
Value 1 Name: EnableDeadGWDetect Type: REG_DWORD Data: 0x1
Value 2 Name: EnableDHCP Type: REG_DWORD Data: 0x1
Value 3 Name: NameServer Type: REG_SZ Data:
Value 4 Name: Domain Type: REG_SZ Data:
Value 5 Name: RegistrationEnabled Type: REG_DWORD Data: 0x1
Value 6 Name: RegisterAdapterName Type: REG_DWORD Data: 0
Value 7 Name: DhcpServer Type: REG_SZ Data: 255.255.255.255
Value 8 Name: Lease Type: REG_DWORD Data: 0xa8c00
Value 9 Name: LeaseObtainedTime Type: REG_DWORD Data: 0x46a7add4
Value 10 Name: T1 Type: REG_DWORD Data: 0x46acf3d4
Value 11 Name: T2 Type: REG_DWORD Data: 0x46b0e854
Value 12 Name: LeaseTerminatesTime Type: REG_DWORD Data: 0x46b239d4
Value 13 Name: AddressType Type: REG_DWORD Data: 0
Value 14 Name: IsServerNapAware Type: REG_DWORD Data: 0
Value 15 Name: DhcpConnForceBroadcastFlag
Value 16 Name: IPAutoconfigurationAddress
Value 17 Name: IPAddress Type: REG_MULTI_SZ Data:
Value 18 Name: SubnetMask Type: REG_MULTI_SZ Data:
Value 19 Name: DefaultGateway Type: REG_MULTI_SZ Data:
Value 20 Name: DhcpIPAddress Type: REG_SZ Data: 0.0.0.0
Value 21 Name: DhcpSubnetMask Type: REG_SZ Data: 255.0.0.0
Value 22 Name: ActiveConfigurations Type: REG_MULTI_SZ Data: Alternate_{4CB26316-E955-4
Version 2:
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\
Class Name: <NO CLASS>
Last Write Time: 7/28/2007 - 2:14 PM
Value 0
Name: UseZeroBroadcast
Type: REG_DWORD
Data: 0
Value 1
Name: EnableDeadGWDetect
Type: REG_DWORD
Data: 0x1
Value 2
Name: EnableDHCP
Type: REG_DWORD
Data: 0
Value 3
Name: NameServer
Type: REG_SZ
Data: 192.168.0.2,4.2.2.1
Value 4
Name: Domain
Type: REG_SZ
Data:
Value 5
Name: RegistrationEnabled
Type: REG_DWORD
Data: 0x1
Value 6
Name: RegisterAdapterName
Type: REG_DWORD
Data: 0
Value 7
Name: DhcpServer
Type: REG_SZ
Data: 255.255.255.255
Value 8
Name: Lease
Type: REG_DWORD
Data: 0xa8c00
Value 9
Name: LeaseObtainedTime
Type: REG_DWORD
Data: 0x46a7add4
Value 10
Name: T1
Type: REG_DWORD
Data: 0x46acf3d4
Value 11
Name: T2
Type: REG_DWORD
Data: 0x46b0e854
Value 12
Name: LeaseTerminatesTime
Type: REG_DWORD
Data: 0x46b239d4
Value 13
Name: AddressType
Type: REG_DWORD
Data: 0
Value 14
Name: IsServerNapAware
Type: REG_DWORD
Data: 0
Value 15
Name: DhcpConnForceBroadcastFlag
Type: REG_DWORD
Data: 0x1
Value 16
Name: IPAutoconfigurationAddress
Type: REG_SZ
Data: 0.0.0.0
Value 17
Name: IPAddress
Type: REG_MULTI_SZ
Data: 192.168.0.20
Value 18
Name: SubnetMask
Type: REG_MULTI_SZ
Data: 255.255.255.0
Value 19
Name: DefaultGateway
Type: REG_MULTI_SZ
Data: 192.168.0.1
Value 20
Name: DhcpIPAddress
Type: REG_SZ
Data: 0.0.0.0
Value 21
Name: DhcpSubnetMask
Type: REG_SZ
Data: 255.0.0.0
Value 22
Name: ActiveConfigurations
Type: REG_MULTI_SZ
Data: Alternate_{4CB26316-E955-4
I don't see anything in there that stands out...
How about the event logs... what do you have for the "event source" of DHCP
How about the event logs... what do you have for the "event source" of DHCP
ASKER
Sorry for the slow response.
The System log has repeated warnings with Event ID 1004 "The DHCP Client service is shutting down. Access denied". This is with the NiC configured with a fixed IP.
Changed NIC config to auto acquire address. After reboot found new message in the log with same content as above.
Also in Network and Sharing Center there is a message "The dependency service or group failed to start".
The System log has repeated warnings with Event ID 1004 "The DHCP Client service is shutting down. Access denied". This is with the NiC configured with a fixed IP.
Changed NIC config to auto acquire address. After reboot found new message in the log with same content as above.
Also in Network and Sharing Center there is a message "The dependency service or group failed to start".
OK... at least we're getting somewhere....
Check the account used by the DHCP service (it should be "Local System")... make sure the service is set to Automatic
Check the account used by the DHCP service (it should be "Local System")... make sure the service is set to Automatic
ASKER
The DHCP Client service is set to "Automatic".
The account it is set to run under is "Local Service". This is configured in the "Log on as: This account" option and specifies a password.
I changed the "Log on as" setting to "Local System account" and tried to start the service. The attempt failed with error 1709: "The account specified for this service is different from the account specified for other servies running in the same process.
I rebooted the system leaving the "Log on as Local System account". Same error occurred trying to start DHCP Client service.
The account it is set to run under is "Local Service". This is configured in the "Log on as: This account" option and specifies a password.
I changed the "Log on as" setting to "Local System account" and tried to start the service. The attempt failed with error 1709: "The account specified for this service is different from the account specified for other servies running in the same process.
I rebooted the system leaving the "Log on as Local System account". Same error occurred trying to start DHCP Client service.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
graye,
Thanks for the help. Your initial post indicated your success with Vista in the scenario I am trying to implement so Vista works in a Win2k Server domain environment.
I think I will do a clean install of Vista and try to get it setup again for automatic addressing.
Thanks for the help. Your initial post indicated your success with Vista in the scenario I am trying to implement so Vista works in a Win2k Server domain environment.
I think I will do a clean install of Vista and try to get it setup again for automatic addressing.
ASKER
After the clean installation ( using the OEM image ) the system has functioned normally. Perhaps this is one approach to the alternate Vista PC test you proposed.
Thanks for the help
Thanks for the help
Yeah, we'll just have to chaulk it up to "one of those things"
What you're describing is a typical scenario that many of us (including me) are running now. Tell us more about your DHCP (or DNS) server setup