Figure 10: Trace of a failing MS DFS referral due to client being unable to resolve node name in referral response.
In the screen shot for Figure 10, we see the ‘STATUS_PATH_NOT_COVERED’, followed by the ‘GET_DFS_REFERRAL’. THEN we see a number of packets involving name lookup for the server ‘ceres’, who is the server we got a MS DFS referral for. Note the highlighted line ‘Name Query Response’. In the detail window of the above screenshot, you see that this is a NEGATIVE response –
‘Requested name does not exist’. SO – the referral functioned properly – the client is trying to find the server we referred it to, but is unsuccessful. From the trace, it clearly cannot find the server named ‘ceres’. Why?
First, let’s check to make sure that the server and share we are setting the link up to is correct. On the HP CIFS Server
# /opt/samba/bin/smbclient //ceres/shared_stuff
added interface ip=16.113.9.137 bcast=16.113.63.255 nmask=255.255.192.0 Password:
Domain=[DON1] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
smb: \> dir |
|
|
|
|
. | D | 0 | Tue Nov | 2 14:42:02 2004 |
.. | D | 0 | Tue Nov | 2 14:42:02 2004 |
ceres_test.txt | A |
| 29 Mon May 24 09:06:10 2004 | |
34717 blocks of size 524288. 32348 blocks available
smb: \>quit
Ok, so WE can find the server and share just fine from the HP CIFS Server making the MS DFS referral.
