What is the operating system of the client computers?? If they are also
NT4.0, they still rely on netbios name resolution. Assuming they are NT4.0
or W9X, then try disabling the requirement for SMB signing on the Windows
2003 servers/domain controllers. You can do such in Local Security Policy
[or better yet Domain Controller Security Policy for domain controllers
only] by going to security settings/local policies/security options and
disabling the setting for "Microsoft network server:digitally sign
communications(always). Also make sure that the Windows 2003 servers are
also wins clients assuming wins is being used which it should be if
NT4.0/W9X computers are still being used. --- Steve
"Joe" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We have a windows NT based network on which we are in the process of
> migrating to a 2003 network. On the NT network we had a machine that was
> the PDC and it ran Exchange. We have installed a Windows 2003 server
> which is a DC on a new active directory domain and we have setup all of
> the workstations to log into the new 2003 domain. We established a trust
> between the 2003 and NT domains and used the Exchange server on the NT
> domain. We have now migrated all Exchange to the 2003 domain, so we are
> not using anything from the old domain.
>
> If we shut down the NT PDC we have several machines that slow down to a
> crawl and experience problems. Mainly the problems relate to trying to
> access files on the NT file server that was a member server of the NT
> domain and is now joined to the 2003 domain. When we fire up the old NT
> PDC again, the speed and browsing issues go away.
>
> We have the 2003 server running DNS and DHCP. All workstations are set to
> get DNS information automatically and the stations experiencing the
> problems definitely are using the new 2003 server for DNS.
>
> Any ideas on why this is happening and how to fix it?
>
> Thanks,
>
> Joe
>
|