ProliantFan
Technical User
Hi all,
I'm have some trouble with a migration. The problem is either with wins or DNS.
Situation:
We have an Old NT4.0 domain and a newer 2003 domain. The 2003 domain i cannot touch because it's mantained by the central company. But the NT4 domain is connected with the 2003 domain.
On our own NT4.0 domain we have a pdc en bdc both running dns wins and dhcp. We want to migrate these functions to windows 2003 servers.
I have installed these on 2 windows 2003 servers that have become members of the new ad domain and replicated the dns with the older nt4.0 dns. I also recreated the dhcp with an export (dhcpexim) and an import with netsh.
Wins didn't get recreated execpt for the static mappings.
The problem i'm having is:
Last week we launched the new servers DNS Wins and DHCP seem to work fine except for some clients. We have clients in the old domain (that i can manage) and we have clients in the new domain. In the dhcp options we changed the old wins and dns server ip adresses to the adresses of the new servers. DHCP works fine because the clients do get the right options.
But!!!!
If a client that is still member of the old domain logs on, the netlogon scripts will not run if we define the new wins server address in dhcp. If we add the old wins server address in the dhcp options and set it as first in the list the logon scripts will run. I think it's a problem with DNS but i can't seem to find it.
I synced dns with the old PDC as stated above and last friday evening i set the new 2003 dns server to primary. I also recreated the reverse lookup (just copied the files from the old server) and manually added a dns entry for the old pdc en bdc. DNS and Wins are still running on the old NT4.0 servers because our sbc team still need to update their servers first and because something doesn't work.
We need to keep wins because the domain controllers (nt4.0) still need to be migrated and this won't happen till end of the year.
Anyone have an suggestion?
I'm have some trouble with a migration. The problem is either with wins or DNS.
Situation:
We have an Old NT4.0 domain and a newer 2003 domain. The 2003 domain i cannot touch because it's mantained by the central company. But the NT4 domain is connected with the 2003 domain.
On our own NT4.0 domain we have a pdc en bdc both running dns wins and dhcp. We want to migrate these functions to windows 2003 servers.
I have installed these on 2 windows 2003 servers that have become members of the new ad domain and replicated the dns with the older nt4.0 dns. I also recreated the dhcp with an export (dhcpexim) and an import with netsh.
Wins didn't get recreated execpt for the static mappings.
The problem i'm having is:
Last week we launched the new servers DNS Wins and DHCP seem to work fine except for some clients. We have clients in the old domain (that i can manage) and we have clients in the new domain. In the dhcp options we changed the old wins and dns server ip adresses to the adresses of the new servers. DHCP works fine because the clients do get the right options.
But!!!!
If a client that is still member of the old domain logs on, the netlogon scripts will not run if we define the new wins server address in dhcp. If we add the old wins server address in the dhcp options and set it as first in the list the logon scripts will run. I think it's a problem with DNS but i can't seem to find it.
I synced dns with the old PDC as stated above and last friday evening i set the new 2003 dns server to primary. I also recreated the reverse lookup (just copied the files from the old server) and manually added a dns entry for the old pdc en bdc. DNS and Wins are still running on the old NT4.0 servers because our sbc team still need to update their servers first and because something doesn't work.
We need to keep wins because the domain controllers (nt4.0) still need to be migrated and this won't happen till end of the year.
Anyone have an suggestion?