Bug 5351 - Windows Vista received "The parameter is incorrect" error.
Windows Vista received "The parameter is incorrect" error.
Product: Samba 3.0
Classification: Unclassified
Component: Config Files
x64 Other
: P3 major
: none
Assigned To: Gerald (Jerry) Carter
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2008-03-25 12:12 UTC by Eddie Chen
Modified: 2008-03-25 12:50 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Eddie Chen 2008-03-25 12:12:42 UTC
We have 4 samba servers all running RHEL4u5 samba version 3.0.27a, and one of the 4 servers is not allowing Windows Vista to access its samba shares. When we issue dir \\bb02f79.unx.sas.com\sasgen, it returned "The Parameter is incorrect", and others listed files.

We compared their config file, and everything are the same except netbios name.

Here is the error log:
[2008/03/19 15:50:58, 3] smbd/error.c:error_packet_set(106)error packet at smbd/sesssetup.c(105) cmd=115 (SMBsesssetupX) NT_STATUS_INVALID_PARAMETER
[2008/03/19 15:51:09, 3] smbd/process.c:timeout_processing(1328) timeout_processing: End of file from client (client has disconnected).
[2008/03/19 15:51:09, 3] smbd/sec_ctx.c:set_sec_ctx(241)setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/03/19 15:51:09, 3] smbd/connection.c:yield_connection(69)Yielding connection to 
[2008/03/19 15:51:09, 3] smbd/server.c:exit_server_common(768)Server exit (normal exit)

Samba config file:
        netbios name    = BB02F79
        workgroup = CARYNT
        server string = PC Bubble Samba Server
        log file = /var/log/samba/%m.log
        log level = 3
        max log size = 10240
        security = domain
        encrypt passwords = yes
        password server = *
        socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536
        deadtime = 15
        max smbd processes = 5000
        local master = no
        wins support = yes 
        wins server = 
        dns proxy = no
        oplocks = no

Thank you for helping, as our vista users are dead in the water.

Comment 1 Gerald (Jerry) Carter 2008-03-25 12:24:54 UTC
Believe to fixed in 3.0.28a.  Please retest.  Thanks.  Reopen if necessary.
Comment 2 Gerald (Jerry) Carter 2008-03-25 12:25:16 UTC
marking as fixed.
Comment 3 Eddie Chen 2008-03-25 12:26:26 UTC
but why other servers with 3.0.27a worked?
Comment 4 Gerald (Jerry) Carter 2008-03-25 12:50:22 UTC
Vista changes things.  Would you test and let me know if 3.0.28a solves the issue for you?  Thanks.