join domain

Hi,

I'm trying to join a vista machine to a Windows 2008 domain.. It takes
forever.. I'm not having the same issue with XP machines. They join and
build the desktop right away..

On the vista machine. I join the domain, it reboots. I sign on and it
takes about 30 to 40 minutes to login and build the desktop... I have a
similar what period just to sign off.

I'm not sure why I'm not experiencing this with XP machines?

Thanks
George

"George" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi,
>
> I'm trying to join a vista machine to a Windows 2008 domain.. It takes
> forever.. I'm not having the same issue with XP machines. They join and
> build the desktop right away..
>
> On the vista machine. I join the domain, it reboots. I sign on and it
> takes about 30 to 40 minutes to login and build the desktop... I have a
> similar what period just to sign off.
>
> I'm not sure why I'm not experiencing this with XP machines?
>
> Thanks
> George
>


I believe this is a classic DNS issue. However, difficult to tell with the
limited info provided. Please post an ipconfig /all from the Vista machine,
XP machine and from the DC. This will help us evaluate the machines' configs
and provide a better diagnosis.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

XP client Machine: (this client comes right up)

IP- 172.22.5.15
Subnet - 255.255.0.0
Gateway - 172.22.1.1
DHCP - 172.22.3.1
DNS - 172.22.3.1
172.22.3.3

DC1 - (windows 2008 NOT rc2)

IP - 172.22.3.1
Subnet - 255.255.0.0
Gateway - 172.22.1.1
DNS - 127.0.0.1 (I'm going to tinker with this.. I know it's the IP
to it's self I'll plug in 172.22.3.1
172.22.3.3 here and see what happens)


DC2 - (windows 2008 NOT rc2)

IP - 172.22.3.3
Subnet - 255.255.0.0
Gateway - 172.22.1.1
DNS - 172.22.3.1
127.0.0.1

Windows 7 Client - (this client comes right up like XP)

IP - 172.22.5.4
Subnet - 255.255.0.0
Gateway - 172.22.1.1
DHCP - 172.22.3.1
DNS - 172.22.3.1
172.22.3.3

Window Vista Client - (this client takes forever to come to the desktop)

IP - 172.22.5.10
Subnet - 255.255.0.0
Gateway - 172.22.1.1
DHCP - 172.22.3.1
DNS - 172.22.3.1
172.22.3.3



"Ace Fekay [MVP-DS, MCT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "George" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hi,
>>
>> I'm trying to join a vista machine to a Windows 2008 domain.. It takes
>> forever.. I'm not having the same issue with XP machines. They join and
>> build the desktop right away..
>>
>> On the vista machine. I join the domain, it reboots. I sign on and it
>> takes about 30 to 40 minutes to login and build the desktop... I have a
>> similar what period just to sign off.
>>
>> I'm not sure why I'm not experiencing this with XP machines?
>>
>> Thanks
>> George
>>
>
>
> I believe this is a classic DNS issue. However, difficult to tell with the
> limited info provided. Please post an ipconfig /all from the Vista
> machine, XP machine and from the DC. This will help us evaluate the
> machines' configs and provide a better diagnosis.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
> MCSA 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
> Microsoft MVP - Directory Services
>
> If you feel this is an urgent issue and require immediate assistance,
> please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>

Hello George,

For the DC/DNS servers configure them also with the other DNS as secondary
on the NIC. And you are correct use the real ip address instead of the loopback
ip 127.0.0.1.

As you are not posting the real ipconfig /all, we can not see if there is
anything else creating the problem. So none of the machines uses external
DNS servers also on another NIC not posted here? So the DCs only use one
NIC and only this is connected to the network?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> XP client Machine: (this client comes right up)
>
> IP- 172.22.5.15
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DHCP - 172.22.3.1
> DNS - 172.22.3.1
> 172.22.3.3
> DC1 - (windows 2008 NOT rc2)
>
> IP - 172.22.3.1
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DNS - 127.0.0.1 (I'm going to tinker with this.. I know it's
> the IP
> to it's self I'll plug in 172.22.3.1
> 172.22.3.3 here and see what happens)
> DC2 - (windows 2008 NOT rc2)
>
> IP - 172.22.3.3
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DNS - 172.22.3.1
> 127.0.0.1
> Windows 7 Client - (this client comes right up like XP)
>
> IP - 172.22.5.4
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DHCP - 172.22.3.1
> DNS - 172.22.3.1
> 172.22.3.3
> Window Vista Client - (this client takes forever to come to the
> desktop)
>
> IP - 172.22.5.10
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DHCP - 172.22.3.1
> DNS - 172.22.3.1
> 172.22.3.3
> "Ace Fekay [MVP-DS, MCT]" <(E-Mail Removed)> wrote in
> message news:(E-Mail Removed)...
>
>> "George" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>
>>> Hi,
>>>
>>> I'm trying to join a vista machine to a Windows 2008 domain.. It
>>> takes forever.. I'm not having the same issue with XP machines.
>>> They join and build the desktop right away..
>>>
>>> On the vista machine. I join the domain, it reboots. I sign on and
>>> it takes about 30 to 40 minutes to login and build the desktop... I
>>> have a similar what period just to sign off.
>>>
>>> I'm not sure why I'm not experiencing this with XP machines?
>>>
>>> Thanks
>>> George
>> I believe this is a classic DNS issue. However, difficult to tell
>> with the limited info provided. Please post an ipconfig /all from the
>> Vista machine, XP machine and from the DC. This will help us evaluate
>> the machines' configs and provide a better diagnosis.
>>
>> -- Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit
>> among responding engineers, and to help others benefit from your
>> resolution.
>>
>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007,
>> MCSE &
>> MCSA 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>> Microsoft MVP - Directory Services
>> If you feel this is an urgent issue and require immediate assistance,
>> please contact Microsoft PSS directly. Please check
>> http://support.microsoft.com for regional support phone numbers.
>>

"George" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> XP client Machine: (this client comes right up)
>
> IP- 172.22.5.15
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DHCP - 172.22.3.1
> DNS - 172.22.3.1
> 172.22.3.3
>
> DC1 - (windows 2008 NOT rc2)
>
> IP - 172.22.3.1
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DNS - 127.0.0.1 (I'm going to tinker with this.. I know it's the IP
> to it's self I'll plug in 172.22.3.1
> 172.22.3.3 here and see what happens)
>
>
> DC2 - (windows 2008 NOT rc2)
>
> IP - 172.22.3.3
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DNS - 172.22.3.1
> 127.0.0.1
>
> Windows 7 Client - (this client comes right up like XP)
>
> IP - 172.22.5.4
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DHCP - 172.22.3.1
> DNS - 172.22.3.1
> 172.22.3.3
>
> Window Vista Client - (this client takes forever to come to the desktop)
>
> IP - 172.22.5.10
> Subnet - 255.255.0.0
> Gateway - 172.22.1.1
> DHCP - 172.22.3.1
> DNS - 172.22.3.1
> 172.22.3.3
>
>

As Meinolf said, it would have been better to see the actual ipconfig /all,
which I think would have been easier by copying and pasting to your post.
There is other info when using a /all that we look at, such as Prim DNS
suffix, if any routing parameters are enabled, search suffix, NetBIOS, mode,
etc, which DHCP doesn't handle, or even the domain name if its a single
label name or if there are any DNS non-supported characters in the name,
which affects Vista's ability to resolve host names compared to XP and 7.

Nontheless as far as the Vista machine, basically it's grabbing a config
from the same DHCP as the 7 machine, so the ip config doesn't appear to be a
factor. I assume there is no GPO affecting this machine's settings regarding
network settings, or even the Windows fireall, etc?

Ace