1. My guess is that you have public DNS value in workstation NIC properties. There should be only IP of first DC W2K3.
2. It is usefull to fill suffix of local domain (FQDN)
3. Do not solve logon script before adding workstation into domain. Remember that when workstation is added to domain, it is in Computers. Move workstation from Computers to new OU, say Workstations. Apply computer GPO to OU=Workstations.
4. Use network monitor to troubleshoot network traffic
Regards
Milos

Need to support users over the internet? click here try our remote control online beta

Hi,
May I know the result after ten minutes login? Cannot connect to domain server, or join domain or log on or just network mappings failed?
What is the role of Windows server 2008? Is it a DC? Do you mean that your DC, DNS and DHCP servers run on the same 2003 server? If not, you may set DC IP as the workstation DNS for a test. Also, you could refresh DNS.

Need to support users over the internet? click here try our remote control online beta

The DC(s) is Windows Server 2003, and one Windows Server 2008. The DNS and DHCP servers run on the 2003 server. There is a login script which runs as well which sets up all of the network shares. This fails. The machine boot fine,
but login takes like 10 min.
I have done the following to no avail:
1) change the Local Security Policy on both server and workstation.
2) disable Symantec Endpoint Protection on both servers and workstation (on workstation, uninstalled)

I can ping the Windows 2008 server with no problem. When I do a net view of the server, it fails. When I do a net view (with no parameters), it lists all of the computers in the domain.
Please help !!!!

Need to support users over the internet? click here try our remote control online beta

1. My guess is that you have public DNS value in workstation NIC properties. There should be only IP of first DC W2K3.
2. It is usefull to fill suffix of local domain (FQDN)
3. Do not solve logon script before adding workstation into domain. Remember that when workstation is added to domain, it is in Computers. Move workstation from Computers to new OU, say Workstations. Apply computer GPO to OU=Workstations.
4. Use network monitor to troubleshoot network traffic
Regards
Milos

There is an amazing pack of free network admin tools. click here to download it

Hi,
May I know the result after ten minutes login? Cannot connect to domain server, or join domain or log on or just network mappings failed?
What is the role of Windows server 2008? Is it a DC? Do you mean that your DC, DNS and DHCP servers run on the same 2003 server? If not, you may set DC IP as the workstation DNS for a test. Also, you could refresh DNS.

Need to support users over the internet? click here try our remote control online beta