Archived from groups: microsoft.public.win2000.dns (More info?)
Background: client of mine had a Windows 2000 server with multiple clients, not sure what the structure was (domain I think, but may have been in a workgroup). To this mix they added an SBS2003 server, not sure how the W2K server was playing at that time (getting clarification on that). In this new structure, the W2K server has been both a DC and member server, and of course SBS box a DC. No matter how we configure the W2K server, I get the following on the SBS box:
1. Group policy is messed up. I can't browse any of the SBS local shares logged in as admin on the SBS box, getting 'access denied' when browsing network places. I can see them there and with a net use, but trying to browse them asks for id/pw, which are not recognized. Getting events 103, and 1058 every 5 minutes, and other gp funkiness as well. Much research on the web lead me to several workarounds, none of which worked, and KB 842804 and 830905, hotfixes which, again, didn't work
2. The reason I put this here instead of an SBS group: netdiag is failing on the DNS test as follows:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.16.2'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
Also getting NetBT event 4321, basically saying that the server can't be named since it's already named.
Replication doesn't fix it, netdiag /fix doesn't fix it either. Also several dcdiag tests yield 'access denied'. My thoughts are that perhaps the DNS issues are causing the group policy issues. If the W2K server had been running AD, with perhaps a single-level domain name (Astro), and now they've added an sbs box with an astro.local domain name, without properly downgrading the original domain, could that cause these types of problems? And if my speculation is correct, is there anything that could be done to fix it short of re-building the domain (with SBS, as that is what they want)? Appreciate any input.
Randy Knapp
Background: client of mine had a Windows 2000 server with multiple clients, not sure what the structure was (domain I think, but may have been in a workgroup). To this mix they added an SBS2003 server, not sure how the W2K server was playing at that time (getting clarification on that). In this new structure, the W2K server has been both a DC and member server, and of course SBS box a DC. No matter how we configure the W2K server, I get the following on the SBS box:
1. Group policy is messed up. I can't browse any of the SBS local shares logged in as admin on the SBS box, getting 'access denied' when browsing network places. I can see them there and with a net use, but trying to browse them asks for id/pw, which are not recognized. Getting events 103, and 1058 every 5 minutes, and other gp funkiness as well. Much research on the web lead me to several workarounds, none of which worked, and KB 842804 and 830905, hotfixes which, again, didn't work
2. The reason I put this here instead of an SBS group: netdiag is failing on the DNS test as follows:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.16.2'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
Also getting NetBT event 4321, basically saying that the server can't be named since it's already named.
Replication doesn't fix it, netdiag /fix doesn't fix it either. Also several dcdiag tests yield 'access denied'. My thoughts are that perhaps the DNS issues are causing the group policy issues. If the W2K server had been running AD, with perhaps a single-level domain name (Astro), and now they've added an sbs box with an astro.local domain name, without properly downgrading the original domain, could that cause these types of problems? And if my speculation is correct, is there anything that could be done to fix it short of re-building the domain (with SBS, as that is what they want)? Appreciate any input.
Randy Knapp
Facebook
Twitter
Instagram