[Samba] smbmount to Win2k dying after kernel/samba upgrades

[samba at transparentmeat.net]

Really odd problem that I'm having, and I'm totally clueless as to whats
causing it.

Scenario:
2 mounts from a W2K machine to a Linux box.  The Win2k box gets powered
down overnight.  Obviously during this, if i do a df it freezes because it
cant reach the drives.  I used to be able to boot the machine back up in
the morning and it would see the drives again.  Not anymore.  The same
occurs even if I reboot the win2k box and it comes back in 2 minutes.  Im
totally clueless.  I can umount then mount again and it'll work, but it
wont fix itself after a reboot.


Information which might be helpful:

Environment:
Slackware Linux on the -current tree (close to v9.1)
Kernel brought to 2.6.0 from source
Samba 3.0.1 from source (./configure --with-smbmount)

Which look like this when correctly mounted:
//blitzwing/c         39067648  29671424   9396224  76% /blitzwing/cdrive
//blitzwing/jimothy   39067648  29671424   9396224  76% /blitzwing/write

My lines in /etc/fstab (drives get mounted out of rc.local)
//blitzwing/c   /blitzwing/cdrive       smbfs   ip=192.168.1.2,ro,username=linux,password=XXXXXX
//blitzwing/jimothy     /blitzwing/write        smbfs   ip=192.168.1.2,rw,username=linux,password=XXXXXX

Error lines from 'dmesg' on machine thats failing
smb_add_request: request [c69f8ec0, mid=6] timed out!
SMB connection re-established (-5)
smb_lookup: find //Documents and Settings failed, error=-512
smb_add_request: request [c351be60, mid=13] timed out!
smb_lookup: find //Documents and Settings failed, error=-5
smb_add_request: request [c3929ec0, mid=13] timed out!
SMB connection re-established (-5)
SMB connection re-established (-5)
smb_add_request: request [c46f0ec0, mid=54] timed out!
smb_add_request: request [c46f0ec0, mid=25] timed out!
smb_add_request: request [c440eee0, mid=56] timed out!


I upgraded to the new kernel and latest Samba at the same time, and I cant
tell which thing is causing the issue (if its either at all)

Does anyone have ANY clue what could be causing this?   Im
wondering if theres something different in 2.6.0 that I failed to compile
in, or if theres something I did wrong with the 3.0.1 compile.

Also, I have a similar setup (version of slackware, kernel, and samba)
running almost exactly the same; the only difference being im connecting
to a Windows XP Pro machine instead of Win2K and it works perfectly.  I
can reboot without issue, and it finds my drives/shares no problem.

(output from dmesg on the box connecting to winxp:
SMB connection re-established (-5)
SMB connection re-established (-5)
SMB connection re-established (-5)
SMB connection re-established (-5)
SMB connection re-established (-5)
SMB connection re-established (-5)
SMB connection re-established (-5)



I can paste up anything else that might be needed to figure out whats
going on.  Any help at all would be greatly appreciated.  Thanks