HP CIFS Windows 2000 Interoperability (October 2002)

CIFS/9000 and Windows 2000 Interoperability

Hewlett-Packard

• The client maps the root share (single namespace)

• The client user clicks on a subdirectory, which is really a DFSLink. The

operation is sent as a Query for DFSLink

• The server responds that it has no such local path. The operation is sent

as a Path Not Covered

• The client then knows that it must get a referral from the server

• The server sends a referral response that tells the client where to connect

• The operation is completed with the standard drive mapping protocol

7.4 CIFS/9000 and DFS

The referral protocol exchange occurs exclusively on the client –to-DFS root server

connection. To the DFSLink (the actual file server) the operation appears as just another

ordinary connection mapping protocol, as long as the standard UNC (Universal Naming

Convention) format is used (\\RootServerName\namespace). The CIFS/9000 Server

operates as a “Leaf Node”, which is the common name for DFSLink. The CIFS/9000 server

can only operate as a leaf node – it cannot be a root node.

7.4.1 CIFS/9000 Connection Sequence

A Network Monitor trace series shows the query-referral transaction sequence from a

Windows 2000 Pro client to a CIFS/9000 server:

W2000 Client

W2000 Server

CIFS/9000 Server

Map Drive

Pass

Thru

Auth Reply

Complete

Protocol Negotiation

Map DriveMap Drive

Pass

Thru

Pass

Thru

Auth ReplyAuth Reply

CompleteComplete

Protocol NegotiationProtocol Negotiation

Map Root ShareMap Root Share

Query for DFSLinkQuery for DFSLink

Path Not CoveredPath Not Covered

Get ReferralGet Referral

Referral ResponseReferral Response