Workgroup versus Domain?

[Guest]

I "renamed" my workstations so that they were part of our network domain, the
same domain as the network server (Windows 2000 Server). I moved the
workstations profiles so that the users retained their settings with the
domain logon. However, now the logons take five minutes to load settings,
even though the profiles are on the local disk of each workstation. Why is
it now taking so long? The logons were virtually instantaneous when the
workstations were defined as part of a workgroup rather than as part of the
domain. Help!

 

[Lanwench [MVP - Exchange]]

See reply to your other post.

 

[Richard G. Harper]

Are the clients set up to use only the network DNS to resolve names? If not
they need to be, and the network DNS server should be set up to look outside
the network (autoforward) to resolve names outside.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

How do I accomplish this on the clients (workstations) and on the server?
Specific steps will be greatly appreciated. Thanks.

Are the clients set up to use only the network DNS to resolve names? If not
they need to be, and the network DNS server should be set up to look outside
the network (autoforward) to resolve names outside.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

I "renamed" my workstations so that they were part of our network domain,
the
same domain as the network server (Windows 2000 Server). I moved the
workstations profiles so that the users retained their settings with the
domain logon. However, now the logons take five minutes to load settings,
even though the profiles are on the local disk of each workstation. Why
is
it now taking so long? The logons were virtually instantaneous when the
workstations were defined as part of a workgroup rather than as part of
the
domain. Help!

 

[Lanwench [MVP - Exchange]]

How do I accomplish this on the clients (workstations)

Ideally, by changing it in your DHCP scope options.

and on the
server?

In the IP settings of your server's NIC. Then create forwarders in your DNS
server itself - to your ISP's DNS servers. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Specific steps will be greatly appreciated. Thanks.

Are the clients set up to use only the network DNS to resolve names?
If not they need to be, and the network DNS server should be set up
to look outside the network (autoforward) to resolve names outside.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

I "renamed" my workstations so that they were part of our network
domain, the
same domain as the network server (Windows 2000 Server). I moved
the workstations profiles so that the users retained their settings
with the domain logon. However, now the logons take five minutes
to load settings, even though the profiles are on the local disk of
each workstation. Why is
it now taking so long? The logons were virtually instantaneous
when the workstations were defined as part of a workgroup rather
than as part of the
domain. Help!

 

[Guest]

How do I change "it" in the DHCP scope of the clients (workstations)? I need
more detail, as I am just a chaplain trying to set up a network. I go the
detailed info at the link you gave. I need the same type of detail for

"Ideally, by changing it in your DHCP scope options."

Thanks

How do I accomplish this on the clients (workstations)

Ideally, by changing it in your DHCP scope options.

and on the
server?

In the IP settings of your server's NIC. Then create forwarders in your DNS
server itself - to your ISP's DNS servers. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Specific steps will be greatly appreciated. Thanks.

Are the clients set up to use only the network DNS to resolve names?
If not they need to be, and the network DNS server should be set up
to look outside the network (autoforward) to resolve names outside.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


message I "renamed" my workstations so that they were part of our network
domain, the
same domain as the network server (Windows 2000 Server). I moved
the workstations profiles so that the users retained their settings
with the domain logon. However, now the logons take five minutes
to load settings, even though the profiles are on the local disk of
each workstation. Why is
it now taking so long? The logons were virtually instantaneous
when the workstations were defined as part of a workgroup rather
than as part of the
domain. Help!

 

[Ron Lowe]

Are the clients set up to use only the network DNS to resolve names? If

How do I accomplish this on the clients (workstations) and on the server?
Specific steps will be greatly appreciated. Thanks.

Here's my usual lecture on how to set up DNS in a domain:

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers:

HOWTO: Remove the Root Zone (Dot Zone)
http://support.microsoft.com/default.aspx?kbid=298148

The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

 

[Guest]

I checked my test workstation with ipconfig/all. There were two DNS servers
listed, both of which are not my Win2K server. How do I change this to point
to my Win2K server?

 

[Lanwench [MVP - Exchange]]

How do I change "it" in the DHCP scope of the clients (workstations)?

You don't change the options there.

If you're using DHCP, you change it on the DHCP server itself - in the scope
options. I'm presuming you're using your Windows 2000 server as your DHCP
server - if you run ipconfig /all at a client, a) is DHCP enabled and b)
what's the IP address of the DHCP server? If this is your Windows server,
good - if it's your Internet router, not so good.

http://support.microsoft.com/default.aspx?scid=kb;en-us;300429&sd=tech
explains how to configure/modify the Windows 2000 DHCP server. If you're
using your router as the DHCP server, I suggest you disable that on the
router & set it up in Windows instead.

If you're using static IP addresses for some reason, you need to visit each
server & workstation, log in w/admin rights, and manually change everything
you need. I'm very lazy and prefer DHCP.

I need more detail, as I am just a chaplain trying to set up a
network. I go the detailed info at the link you gave. I need the
same type of detail for

"Ideally, by changing it in your DHCP scope options."

Thanks

How do I accomplish this on the clients (workstations)

Ideally, by changing it in your DHCP scope options.

and on the
server?

In the IP settings of your server's NIC. Then create forwarders in
your DNS server itself - to your ISP's DNS servers. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Specific steps will be greatly appreciated. Thanks.

:

Are the clients set up to use only the network DNS to resolve
names? If not they need to be, and the network DNS server should
be set up to look outside the network (autoforward) to resolve
names outside.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


message I "renamed" my workstations so that they were part of our network
domain, the
same domain as the network server (Windows 2000 Server). I moved
the workstations profiles so that the users retained their
settings with the domain logon. However, now the logons take
five minutes to load settings, even though the profiles are on
the local disk of each workstation. Why is
it now taking so long? The logons were virtually instantaneous
when the workstations were defined as part of a workgroup rather
than as part of the
domain. Help!

 

[Ron Lowe]

I checked my test workstation with ipconfig/all. There were two DNS
servers
listed, both of which are not my Win2K server. How do I change this to
point
to my Win2K server?

Well, the option is to be found in:
Network Connections folder;
R-click the LAN connection, Properties;
Scroll down the list of items, and select Internet Protocol (TCP/IP);
Click the Properties button;
And that's where the DNS entries go.

However, like I say, I'd normally set this on the Server itself, on the DHCP
server.
Then have the clients set to obtain it automatically.

The person who set up your server will know how to do this.
It sounds like you are a little out of your depth
I think you might want to get the person who set up the domain involved.

 

[Guest]

Thanks Ron. I set the client to retrieve the DNS info from the server. I
configured the server properly (I think) in the DNS, WINS, and DHCP admin
tools.

Out of my depth? Absolutely. However, ain't nobody else swimmin' and no
lifeguards except guys like you. Thanks for the help.

I have been in full-time Christian vocational work since 1996. Before that
I spent 17 years as an aerospace engineer (scientific programming
specialist). Network administration was one of my chores. However, our
servers were Digital Equipment (Alpha's), one NT server (which I let someone
else handle), and Sun (Unix) boxes. I think that I can get the Windows stuff
with a little help from guys like you. Thanks again.

 

[Lanwench [MVP - Exchange]]

Thanks Ron. I set the client to retrieve the DNS info from the
server. I configured the server properly (I think) in the DNS, WINS,
and DHCP admin tools.

Out of my depth? Absolutely. However, ain't nobody else swimmin'
and no lifeguards except guys like you. Thanks for the help.

I have been in full-time Christian vocational work since 1996.
Before that I spent 17 years as an aerospace engineer (scientific
programming specialist). Network administration was one of my
chores. However, our servers were Digital Equipment (Alpha's), one
NT server (which I let someone else handle), and Sun (Unix) boxes. I
think that I can get the Windows stuff with a little help from guys
like you. Thanks again.

We never sleep. Sad, isn't it?
Post back if you need more help.<snip>