Drive mapping no longer works on Windows 2000 PCs

[Boyce, Nick]

Two things :

1)  I'm almost sure that Samba needs to be at version 2.0.x (I think 2.0.7
actually) to cope with the changes to the SMB protocol that Microsoft
introduced with Win2K; you're using 1.9.17p4, so I don't see how this can
*ever* have worked with your Win2K PCs ....     (others will correct me if
I'm wrong here)

For VMS there are two ports (two "branches") of Samba 2.x : 2.0.3, and
2.0.6, so if I'm right about 2.0.7 being needed then you're out of luck.

2)  PLEASE don't send HTML-format email to this mailing list - many regard
it as an abomination and spawn of the devil, and personally I regard it as a
major security hazard, and can't help shuddering as I open such messages.
There's no need for it, and it verges on discourtesy to send it to a
technical mailing list - especially in these days of HTML-email-borne
viruses (you've heard of Nimda, right ?)

Cheers,

Nick Boyce
Systems Team, Southwest Solution Centre, Bristol, UK 


-----Original Message-----
From: Tschida, Jim [mailto:JTschida at dexteraxle.com]
Sent: 28 September 2001 19:35
To: 'samba-vms at samba.org'
Subject: Drive mapping no longer works on Windows 2000 PCs


We recently upgraded two PCs from NT 4 to Windows 2000.  Samba worked for
about two weeks but now drive mapping doesn't work anymore.   SMB.CONF
hasn't changed over that period. The error from logs follows.  Bugs.txt says
it could be hardware failure but PCs at NT4 and windows '95 still work
great.  What changed?  Workload on the server?  Security patches on these
two PCs?
 
 
Samba version 1.9.17p4
Digital TCP/IP Services for OpenVMS Alpha Version V4.1 - ECO Level 2
on a AlphaServer 4100 5/466 4MB running OpenVMS V7.1
 
 
The log shows this text for every attempt to map a drive:
===============================================================
INTERNAL ERROR: Signal 10 in pid 38071 (1.9.17p4)
Please read the file BUGS.txt in the distribution
===============================================================
Last message was SMBsesssetupX
size=130
smb_com=0x73
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=24
smb_flg2=7
smb_tid=0
smb_pid=65279
smb_uid=0
smb_mid=192
smt_wct=13
smb_vwv[0]=117 (0x75)
smb_vwv[1]=100 (0x64)
smb_vwv[2]=65535 (0xFFFF)
smb_vwv[3]=50 (0x32)
smb_vwv[4]=0 (0x0)
smb_vwv[5]=38071 (0x94B7)
smb_vwv[6]=0 (0x0)
smb_vwv[7]=1 (0x1)
smb_vwv[8]=0 (0x0)
smb_vwv[9]=0 (0x0)
smb_vwv[10]=0 (0x0)
smb_vwv[11]=212 (0xD4)
smb_vwv[12]=0 (0x0)
smb_bcc=39
 0  0  0 57 69 6E 64 6F   77 73 20 32 30 30 30 20   ...Windo  ws 2000 
32 31 39 35  0 57 69 6E   64 6F 77 73 20 32 30 30   2195.Win  dows 200
30 20 35 2E 30  0  0   0 5.0..
===============================================================
vms_mkdir: /samba_root/log/corefiles, mode: 0000700
Dumping core in /samba_root/log/corefiles
===============================================================
 
Thanks,
 
Jim Tschida