RE: NT4 -> 2003 DNS/Domain Name headache
From: Gary (gary_at_silicon.removethisbit.co.nz)
Date: 03/24/04
- Next message: Scott Abel: "Group Policy Logon Script issue - Win2k3"
- Previous message: Wesley: "Re: Migration from a single NT PDC to a new 2003 AD DC"
- In reply to: Joe Wu [MSFT]: "RE: NT4 -> 2003 DNS/Domain Name headache"
- Next in thread: Joe Wu [MSFT]: "RE: NT4 -> 2003 DNS/Domain Name headache"
- Reply: Joe Wu [MSFT]: "RE: NT4 -> 2003 DNS/Domain Name headache"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Mar 2004 14:02:07 -0800
Thanks,
I set up some test machines and went through the upgrade.
Ive hit one strange problem - The PDC I used had dual
onboard NICs, IPs 10.1.1.1 /8 and 10.1.1.2 /8. Only
10.1.1.1 was connected to the network.
After completing the upgrade there is no communication at
all through the 10.1.1.1 NIC. It wont even ping the bdc
(10.1.1.3) or the client (10.1.1.4), and these cant ping
back to the pdc.
I changed the IP of this nic to 10.1.1.5, but still no go.
I then changed it to obtain its address from dhcp (from
dhcp server on the live network), and it can ping in and
out ok to 'live machines' (192.168.1.x subnet), so it
doesnt looking like a driver problem.
Finally, I connected the second nic (10.1.1.2) to the
network, and everything works. The bdc synchronised, the
client can log on via the pdc, etc etc. Only oustanding
problem is why the nic connected during the upgrade wont
allow any connections!
any ideas?
- Next message: Scott Abel: "Group Policy Logon Script issue - Win2k3"
- Previous message: Wesley: "Re: Migration from a single NT PDC to a new 2003 AD DC"
- In reply to: Joe Wu [MSFT]: "RE: NT4 -> 2003 DNS/Domain Name headache"
- Next in thread: Joe Wu [MSFT]: "RE: NT4 -> 2003 DNS/Domain Name headache"
- Reply: Joe Wu [MSFT]: "RE: NT4 -> 2003 DNS/Domain Name headache"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|