HP CIFS Windows 2000 Interoperability (October 2002)

CIFS/9000 and Windows 2000 Interoperability
Hewlett-Packard
39
6.4 Name Address Resolution: CIFS/9000
Interoperability
When designing a windows 2000 domain, the DNS design has a profound effect upon the
overall ADS design. Both should be considered during the initial Windows 2000 ADS design
phase.
The integration of CIFS/9000 into the Windows 2000 domain often implies the pre-existence
of HP-UX in the enterprise. When this is true, the usage of BIND DNS is probable, and
therefore the integration of the DNS platforms becomes an issue. Windows 2000 DNS can
cause problems for BIND DNS because of the extensions and the lack of adherence to
specifications. The preferred method to protect a BIND DNS domain from Windows 2000
DDNS is to create a sub-zone for DDNS to exist in. This can provide protection for:
• Zone transfers
o WINS
§ Windows 2000 zone transfers contain WINS records
§ BIND does not recognize WINS records
§ Do not transfer a W2000 zone to a BIND secondary
o UTF-8
§ Do not transfer Windows 2000 UTF-8 records to a BIND
secondary
• Windows 2000 Global Catalog Server
o Hosts located in a _msdcs subzone have an illegal DNS name
o Hostname._msdcs.hp.com – “_” is not a legal RFC 952 character
• Clients delete conflicting names
o If a client is configured with a name that already exists in the DNS
domain, it will delete the old record and add itself
With NetBIOS and WINS enabled, the connectivity diagram looks like:
• A Windows 2000 client will locate the domain controller (or any other Windows
domain resource) using DDNS
FIND CIFS/9000
–
W2000 DDNS
FIND CIFS/9000
–
W2000 DDNS
FIND DC – W2000 DDNSFIND DC – W2000 DDNS
W2000 Client
W2000 Server
CIFS/9000 Server
Find DC
–
NetBIOS/WINS
Find DC
–
NetBIOS/WINS