Hello,We are having issues when joining Vista/Server08 to our corporate domain. After it is joined to the domain and rebooted, the machine originally comes back up fine (able to log in, pull valid ip address, etc.) As soon as the machine is rebooted again, network connectivity is lost and the machine pulls a "169." ip address. I am able to somewhat work around this by setting a static IP address. However, not everything works correctly (remote desktop, etc). Anyone have an idea of what is causing this? A quick search online will show that this issue is widespread but I am unable to find a resolution. Any help is appreciated...Barret

Hi Barret, Thank you for posting. Based on my research, I would like to suggest the following to check the issue: 1. Ensure your DHCP server was Authorized in AD console. In Windows Server 2003, DHCP servers in an Active Directory-based domain must be authorized to prevent rogue DHCP servers from coming online. Any Windows Server 2003 DHCP Server that determines itself to be unauthorized will not manage clients. Authorize a DHCP server =============== 1) Click Start , click Programs , click Administrative Tools , and then click DHCP . NOTE : You must be logged on to the server with an account that is a member of the Enterprise Administrators group. 2) In the console tree of the DHCP snap-in, select the new DHCP server. If there is a red arrow in the lower-right corner of the server object, the server has not yet been authorized. 3) Right-click the server, and then click Authorize . 4) After a few moments, right-click the server again, and then click Refresh . There should be a green arrow in the lower-right corner to indicate that the server has been authorized. 2. Check if other computer works well. 3. As a test, please disjoin the computer from the domain to see if it works. This will help us identify whether the issue is related to the domain join operation. Please let us how it works. Thanks. Nicholas Li - MSFT