Discussion
Here's the problem. We have a Windows 2000 server SP4 acting as an active Directory controller. I am trying to setup Exchange 2003 on a new 2003 server which is a member of the AD. The problem is that I am getting a error "DNS_RCODE_ERROR" when trying to use netdiag to verify the DNS service. According to MS this is due to having a single label domain. I have put on both Servers the recommended fixes with no effect. Any body com across this???
Whats the actual response code? I think it should give you a number. Here is an extract from RFC 1035 showing Rcodes and their reference which may be of help:
1 Format error - The name server was unable to interpret the query.
2 Server failure - The name server was unable to process this query due to a problem with the name server.
3 Name Error - Meaningful only for responses from an authoritative name server, this code signifies that the domain name referenced in the query does not exist.
4 Not Implemented - The name server does not support the requested kind of query.
5 Refused - The name server refuses to perform the specified operation for policy reasons. For example, the server may not wish to provide the information to the particular requester, or a name server may not wish to perform a particular operation (e.g., zone transfer) for particular data.
>> Edited by jam1et on Thursday 1st July 13:32
1 Format error - The name server was unable to interpret the query.
2 Server failure - The name server was unable to process this query due to a problem with the name server.
3 Name Error - Meaningful only for responses from an authoritative name server, this code signifies that the domain name referenced in the query does not exist.
4 Not Implemented - The name server does not support the requested kind of query.
5 Refused - The name server refuses to perform the specified operation for policy reasons. For example, the server may not wish to provide the information to the particular requester, or a name server may not wish to perform a particular operation (e.g., zone transfer) for particular data.
>> Edited by jam1et on Thursday 1st July 13:32
The Win 2003 server can join a 2k domain as a member server. It can also join as a DC but essentially what you are doing then is upgrading to a win2003 domain. To do this you need to run a forestprep and domainprep on the AD then do a dc promotion on the 2003 server. Its quite involved but there are plenty of white papers on it at microsoft. If you only have one 2k server currently acting as a DC its probably wise to upgrade the whole domain to 2003 so you can then have both machines running as Domain Contollers for redundancy. Although its a lot of work, it seems daft to waste the oportunity of having two DC's and the benefits of a 2003 domain.
>> Edited by jam1et on Thursday 1st July 17:21
>> Edited by jam1et on Thursday 1st July 17:21
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff