samba - Aug 2004 - XP SP2 client doesn't find netbios alias servers

After upgrading XP to SP2, I can no longer connect to server aliases.
The client reports an error 53, "The network path was not found", when
doing "net use * \\prof\profile.
Mapping to a share on the real netbios name works fine.

Anyone else seen this?

Setup:

samba-3.0.6.rc2

smb.conf

[global]

netbios aliases = PROF
include = /etc/samba/smb.%L

smb.prof

[profile]
       path = /data/samba/profile
       csc policy = disable
       profile acls = yes
       read only = No
       create mask = 0600
       directory mask = 0700
       browseable = No

Here's a tethereal dump on the server of the client trying to map
\\prof\profile.
 
  0.004914 158.36.98.105 -> 158.36.146.4 TCP 1042 > microsoft-ds [SYN]
Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
  0.005004 158.36.146.4 -> 158.36.98.105 TCP microsoft-ds > 1042 [SYN,
ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460
  0.005258 158.36.98.105 -> 158.36.146.4 TCP 1042 > microsoft-ds [ACK]
Seq=1 Ack=1 Win=65535 Len=0
  0.005323 158.36.98.105 -> 158.36.146.4 TCP [TCP ZeroWindow] 1043 >
netbios-ssn [RST, ACK] Seq=73 Ack=1 Win=0 Len=0
  0.005740 158.36.98.105 -> 158.36.146.4 SMB Negotiate Protocol Request
  0.005804 158.36.146.4 -> 158.36.98.105 TCP microsoft-ds > 1042 [ACK]
Seq=1 Ack=138 Win=5840 Len=0
  0.032163 158.36.146.4 -> 158.36.98.105 SMB Negotiate Protocol Response
  0.033356 158.36.98.105 -> 158.36.146.4 SMB Session Setup AndX Request,
NTLMSSP_NEGOTIATE
  0.042391 158.36.146.4 -> 158.36.98.105 SMB Session Setup AndX Response,
NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED
  0.043079 158.36.98.105 -> 158.36.146.4 SMB Session Setup AndX Request,
NTLMSSP_AUTH
  0.082958 158.36.146.4 -> 158.36.98.105 TCP microsoft-ds > 1042 [ACK]
Seq=408 Ack=670 Win=7504 Len=0
  0.174161 158.36.146.4 -> 158.36.98.105 SMB Session Setup AndX Response
  0.174956 158.36.98.105 -> 158.36.146.4 SMB Tree Connect AndX Request, Path:
\\PROF\IPC$
  0.175042 158.36.146.4 -> 158.36.98.105 TCP microsoft-ds > 1042 [ACK]
Seq=520 Ack=748 Win=7504 Len=0
  0.183905 158.36.146.4 -> 158.36.98.105 SMB Tree Connect AndX Response
  0.188154 158.36.98.105 -> 158.36.146.4 SMB Session Setup AndX Request,
NTLMSSP_NEGOTIATE
  0.194760 158.36.146.4 -> 158.36.98.105 SMB Session Setup AndX Response,
NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED
  0.224158 158.36.98.105 -> 158.36.146.4 SMB Session Setup AndX Request,
NTLMSSP_AUTH
  0.262950 158.36.146.4 -> 158.36.98.105 TCP microsoft-ds > 1042 [ACK]
Seq=848 Ack=1356 Win=9648 Len=0
  0.563920 158.36.146.4 -> 158.36.98.105 SMB Session Setup AndX Response
  0.564622 158.36.98.105 -> 158.36.146.4 SMB Tree Connect AndX Request, Path:
\\PROF\PROFILE
  0.564706 158.36.146.4 -> 158.36.98.105 TCP microsoft-ds > 1042 [ACK]
Seq=960 Ack=1440 Win=9648 Len=0
  0.576723 158.36.146.4 -> 158.36.98.105 SMB Tree Connect AndX Response,
Error: STATUS_BAD_NETWORK_NAME

Sten Sletbak wrote:
> After upgrading XP to SP2, I can no longer connect to server aliases.
<snip>
> Mapping to a share on the real netbios name works fine.
I've seen that against real Win2K servers also using AD DNS. I always
thought it was a M$ feature that you had to net use to either the real NetBIOS
computername or the ipaddress. We have various
scripts which resolve the name, then net use to the ipaddress. Doing so allows
you to net use to the alias... wrapping the net use in a script that is.

So, what is the truth on this. Must it be the real name or IP, or should aliases
work in the M$ world... since Samba usually does not "add features" M$
does not offer I would think it behaves the same
way a M$ server box would.

-- 
Michael Lueck
Lueck Data Systems

Remove the upper case letters NOSPAM to contact me directly.

In article <slrnchpcsv.o2u.Sten.Sletbak@valium.p52.hio.no>, Sten Sletbak
wrote:
> After upgrading XP to SP2, I can no longer connect to server aliases.
> The client reports an error 53, "The network path was not found",
when
> doing "net use * \\prof\profile.
> Mapping to a share on the real netbios name works fine.
> 
> Anyone else seen this?
> 
> Setup:
> 
> samba-3.0.6.rc2
> 
> smb.conf
> 
> [global]
> 
> netbios aliases = PROF
> include = /etc/samba/smb.%L
> 
> smb.prof
> 
> [profile]
>        path = /data/samba/profile
>        csc policy = disable
>        profile acls = yes
>        read only = No
>        create mask = 0600
>        directory mask = 0700
>        browseable = No
smb.conf

[global]
smb ports = 139

It turned out that the old smbd daemons weren't properly killed when I first
tested this option...
"#Killall -9 smbd;service smb start" did the trick.

NB!
Do not play with this option when you got users logged on, as the clients are
still talking to
port 445.

So it was not the client not finding the alias server, but rather %L not
substituting correctly.
>From the smb.conf manual page:
%L
the NetBIOS name of the server. This allows you to change your config based on
what the client calls you.
Your server can have a "dual personality".
This parameter is not available when Samba listens on port 445, as clients no
longer send this information.


Sten