Bug 4672 - win2k clients cannot connect since 3.0.25a upgrade, but XP can
win2k clients cannot connect since 3.0.25a upgrade, but XP can
Product: Samba 3.0
Classification: Unclassified
Component: nmbd
x86 Linux
: P3 critical
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2007-05-31 10:37 UTC by Ken Ortiz
Modified: 2009-12-11 08:01 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Ken Ortiz 2007-05-31 10:37:28 UTC
When running under 3.0.22 on linux, I could connect to shares with XP and win2k.  Since upgrading to 3.0.25a yesterday, I can connect with XP, but NOT win2k.  The client generates a very generic error:
The network request is not supported

There is nothing in smbd or nmbd log to help troubleshoot.  I realize win2k is old, but it's necessary for two of our machines, and critical we be able to connect to these samba shares.  Here is my smb.conf.  Some things have been added in fix attempts, such as msdfs settings.  Win2k clients have also been rebooted several times.  Any help is greatly appreciated.

   netbios name = LES4

   domain master = no
   local master = no
   preferred master = no
   os level = 0
   security = share
   guest account = nobody

   interfaces =
   bind interfaces only = Yes

   debug level = 1
   socket options = TCP_NODELAY
   read raw = yes
   workgroup = NERO

   host msdfs = Yes

  lock directory = /usr/local/samba/var/locks
   share modes = yes

  comment = Temporary file space
  path = /raid5/backup/imgs
  read only = no
  public = yes
  max connections = 0
  msdfs root = yes
Comment 1 Jeremy Allison 2007-05-31 15:29:05 UTC
Please set up client machine specific logs eg. :

log file = /var/log/samba/log.%m

set the log to debug level 10 and try to connect from
a failing client. This should tell us more aboout what is
going on.


Comment 2 Karolin Seeger 2009-12-11 08:01:22 UTC
No feedback from the reporter for a very long time.
Closing out bug report.
Please reopen if it's still an issue in a current Samba version.