> Read inline please.
>
> In news:DE298716-F309-4EA1-8B52-C10AB0CD7D27[ at ]microsoft.com,
> Deena <Deena[ at ]discussions.microsoft.com> typed:
> > I have set up a Windows 2003 Server R2 with a domain, DNS server and
> > file server. I followed the wizard to do this and when I check the
> > server management wizard it tells me that it is set up correctly.
> >
> > I have created a container with two users and a group. Both users
> > are part of the group. I have created a share for home directories
> > and assigned a directory to each user. When the user logs in they
> > can read and write to their home directory.
> >
> > On my workstation (Windows XP Pro) I have entered the domain name.
> > The only user on the workstation is one administrator. The user
> > created on the server is not the same name as the administrator user
> > on the workstation.
> >
> > Problem 1: When I log in as either user the login process takes a
> > minimum of 4 minutes.
> >
> > Problem 2: I create a Group Policy and link it to the container
> > using GPMC. When I test the policy with the modeling program, it
> > comes back saying that the settings are working. However, when I log
> > in to a workstation, the policy is not applied. I kept it simple,
> > just saying not to show My Documents on the Start menu.
> >
> > As an attempt to fix this, I downloaded from Microsoft a set of Common
> > Desktop Management Scenarios, imported and linked one to my
> > container. They pass the model test but when logging to a
> > workstation, the Group Policies are not applied.
> >
> > As suggested in one list serve that I read, I have entered the server
> > IP address in the network properties for the DNS. This did not seem
> > to make a difference at all. The same problems occur whether I log
> > in from a wireless laptop or from a wired desktop.
> >
> > Also, I have applied my group policies to user containers only, not to
> > computers. I am not sure if my users are roaming users or not. In
> > their profile I have mapped their home folder to a server shared
> > folder which I thought would make them roaming.
> >
> > Any help would be greatly appreciated. I am about ready to throw in
> > the towel!
>
> The Domain Controller should be using its own address for DNS, and the
> Workstation should also be using the Domain Controller's IP for DNS (only)
> If there is only one DC, then you can only have the one DC listed in TCP/IP
> properties for DNS. Do not use any external DNS in TCP/IP properties of any
> DC or domain member.
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
>
http://www.lonestaramerica.com/>
http://support.wftx.us/>
http://message.wftx.us/> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
>
http://home.in.tum.de/~jain/software/oe-quotefix/> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
>
http://www.oehelp.com/OEBackup/Default.aspx> ===================================
>
>
>
One thing to append. If you need external dns resolution then the AD server