Hello everyone,
I'm having the same problem as someone else has had. I've paraphrased
it here:

>I've added a Windows 2000-member server to my SBS2000 to run Terminal
Services, after I try to log on using the domain administrator account and
>password, the "Loading your personal settings" dialog box is displayed a
extremly long time (like 20 mins) before the desktop appears.
>Log on by using a local administrator account works normally.
>The member server is part of an active directory enviroment. However, it is
not a domain controller.

They got the following reply:

>I fixed it by adding the Primary DNS Suffix option to DHCP, to reflect my
domain name.

The problem is I have no idea what they mean by this (you guessed it, I'm a
tinkerer, not a professional), if anyone could give me some guidance on how
this is achieved it would be greatly appreciated.

Regards

Darren

Re: Terminal Services - Primary DNS Suffix option to DHCP by Javier

Javier
Wed Oct 13 20:17:10 CDT 2004

Hi Darren!

The problem is that any PC or member server in an SBS domain should always
point to the SBS server for DNS. If you run "ipconfig /all" on the TS box it
should say the IP of the SBS under DNS.

Are you using the DHCP from the SBS box? If not, your first step should be
to disable whatever is running DHCP on your lan and then reactivate the SBS
DHCP. Then go to this link and follow the "additional setup" (part c):
http://www.smallbizserver.net/Default.aspx?tabid=52

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"Darren Meredith" <dpm@netcon.net.au> wrote in message
news:Ubkbd.19$GC6.1000@nnrp1.ozemail.com.au...
> Hello everyone,
> I'm having the same problem as someone else has had. I've paraphrased
> it here:
>
>>I've added a Windows 2000-member server to my SBS2000 to run Terminal
> Services, after I try to log on using the domain administrator account and
>>password, the "Loading your personal settings" dialog box is displayed a
> extremly long time (like 20 mins) before the desktop appears.
>>Log on by using a local administrator account works normally.
>>The member server is part of an active directory enviroment. However, it
>>is
> not a domain controller.
>
> They got the following reply:
>
>>I fixed it by adding the Primary DNS Suffix option to DHCP, to reflect my
> domain name.
>
> The problem is I have no idea what they mean by this (you guessed it, I'm
> a
> tinkerer, not a professional), if anyone could give me some guidance on
> how
> this is achieved it would be greatly appreciated.
>
> Regards
>
> Darren
>
>