thr3ads.net - samba - [Samba] Problems with Windows 2003 connecting a Samba server [May 2007]

If this information is useful, please help other people find it:
Share via:

Chan Jason

2007-May-29 20:12 UTC

[Samba] Problems with Windows 2003 connecting a Samba server

Hi list,
   I am encountering a problem in connecting a Windows 2003 to a Samba
3.0.21b server. The Samba server is configured to have a security share option,
so that no password is needed. I can connect to the
server by typing "net use z: \\192.168.51.1\data", and it is
successful. However, if I try to do "dir z:", no file found! Same
behaviour are found in Windows operation, i.e. type
"\\192.168.51.1\data" under Run box in Start Menu. Strangely, another
server with 3.0.14a does not have such problem, and another Windows XP
does not have such problem too! They can view the files in share
easily.

Here comes the log file:
[2007/05/30 04:13:15, 1] smbd/service.c:close_cnum(885)
  192.168.2.37 (192.168.2.37) closed connection to service data
[2007/05/30 04:15:35, 1] smbd/service.c:make_connection_snum(693)
  192.168.2.37 (192.168.2.37) connect to service data initially as
user nobody (uid=99, gid=99) (pid 30283)
[2007/05/30 04:17:00, 1] smbd/service.c:close_cnum(885)
  192.168.2.37 (192.168.2.37) closed connection to service data
[2007/05/30 04:17:00, 1] smbd/service.c:make_connection_snum(693)
  192.168.2.37 (192.168.2.37) connect to service data initially as
user nobody (uid=99, gid=99) (pid 30301)
[2007/05/30 04:18:08, 1] smbd/service.c:close_cnum(885)
  192.168.2.37 (192.168.2.37) closed connection to service data

Here comes the testparm:
[global]
        unix charset = big5
        workgroup = CC
        netbios name = CCSERVER
        server string = Samba Server
        security = SHARE
        log file = /var/log/samba/%m.log
        max log size = 50
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        printcap name = /etc/printcap
        dns proxy = No
        cups options = raw

[homes]
        comment = Home Directories
        read only = No
        browseable = No

[printers]
        comment = All Printers
        path = /var/spool/samba
        printable = Yes
        browseable = No

[data]
        comment = Public Data
        path = /data
        read only = No
        create mask = 0777
        guest ok = Yes

Also here is the traffic log:
  0.000000 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [SYN]
Seq=2266364078 Ack=0 Win=65535 Len=0
  0.000356 192.168.2.37 -> 192.168.51.1 TCP 1903 > netbios-ssn [SYN]
Seq=1017632209 Ack=0 Win=65535 Len=0
  0.010996 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [SYN,
ACK] Seq=1194648936 Ack=2266364079 Win=5808 Len=0
  0.011333 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [ACK]
Seq=2266364079 Ack=1194648937 Win=65535 Len=0
  0.011445 192.168.2.37 -> 192.168.51.1 SMB Negotiate Protocol Request
  0.011599 192.168.51.1 -> 192.168.2.37 TCP netbios-ssn > 1903 [SYN,
ACK] Seq=1190050630 Ack=1017632210 Win=5808 Len=0
  0.011758 192.168.2.37 -> 192.168.51.1 TCP 1903 > netbios-ssn [RST]
Seq=1017632210 Ack=1017632210 Win=0 Len=0
  0.022912 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
Seq=1194648937 Ack=2266364216 Win=6432 Len=0
  0.024424 192.168.51.1 -> 192.168.2.37 SMB Negotiate Protocol Response
  0.025427 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path:
\\192.168.51.1\DATA
  0.039981 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
Response; Tree Connect AndX
  0.040262 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
QUERY_PATH_INFORMATION, Path:
  0.051879 192.168.51.1 -> 192.168.2.37 SMB Transaction2 Response
QUERY_PATH_INFORMATION
  0.052291 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
FIND_FIRST2, Pattern: \*
  1.519710 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
FIND_FIRST2, Pattern: \*
  1.530914 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
Seq=1194652038 Ack=2266364728 Win=7504 Len=0
 51.023255 192.168.2.37 -> 192.168.51.1 SMB Echo Request
 51.033769 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
Seq=1194652038 Ack=2266364781 Win=7504 Len=0
 85.150658 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [FIN,
ACK] Seq=2266364781 Ack=1194649246 Win=65226 Len=0
 85.169401 192.168.51.1 -> 192.168.2.37 NBSS NBSS Continuation Message
 85.169910 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [ACK]
Seq=2266364782 Ack=1194649246 Win=65226 Len=0
 85.170486 192.168.2.37 -> 192.168.51.1 TCP 1904 > microsoft-ds [SYN]
Seq=3224569487 Ack=0 Win=65535 Len=0
 85.170724 192.168.2.37 -> 192.168.51.1 TCP 1905 > netbios-ssn [SYN]
Seq=494418265 Ack=0 Win=65535 Len=0
 85.179785 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [SYN,
ACK] Seq=1275220318 Ack=3224569488 Win=5808 Len=0
 85.180158 192.168.2.37 -> 192.168.51.1 TCP 1904 > microsoft-ds [ACK]
Seq=3224569488 Ack=1275220319 Win=65535 Len=0
 85.180250 192.168.2.37 -> 192.168.51.1 SMB Negotiate Protocol Request
 85.183753 192.168.51.1 -> 192.168.2.37 TCP netbios-ssn > 1905 [SYN,
ACK] Seq=1269633862 Ack=494418266 Win=5808 Len=0
 85.183982 192.168.2.37 -> 192.168.51.1 TCP 1905 > netbios-ssn [RST]
Seq=494418266 Ack=494418266 Win=0 Len=0
 85.191855 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
Seq=1275220319 Ack=3224569625 Win=6432 Len=0
 85.193117 192.168.51.1 -> 192.168.2.37 SMB Negotiate Protocol Response
 85.194151 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
Request, User: anonymous; Tree Connect AndX, Path: \\192.168.51.1\IPC$
 85.208996 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
Response; Tree Connect AndX
 85.211152 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path:
\\192.168.51.1\DATA
 85.224557 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
Response; Tree Connect AndX
 85.224909 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
QUERY_PATH_INFORMATION, Path:
 85.236465 192.168.51.1 -> 192.168.2.37 SMB Transaction2 Response
QUERY_PATH_INFORMATION
 85.236938 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
FIND_FIRST2, Pattern: \*
 86.510090 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
FIND_FIRST2, Pattern: \*
 86.519567 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
Seq=1275223532 Ack=3224570399 Win=8576 Len=0
 96.526425 192.168.2.37 -> 192.168.51.1 SMB Tree Disconnect Request
 96.536065 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
Seq=1275223532 Ack=3224570438 Win=8576 Len=0

(Yes, they are in 2 subnets because they are connected by an IPSec
tunnels.. however other client that does not exhibit the problem are
under the same tunnel!)

If a level 10 log is needed, just tell me and I will post it here.

Any help is appeciated. Thanks very much!

Regards,
Jason Chan

Guenter Kukkukk

2007-May-29 21:15 UTC

head link

[Samba] Problems with Windows 2003 connecting a Samba server

Am Dienstag, 29. Mai 2007 22:12 schrieb Chan Jason:> Hi list,
>    I am encountering a problem in connecting a Windows 2003 to a Samba
> 3.0.21b server. The Samba server is configured to have a security >
share option, so that no password is needed. I can connect to the
> server by typing "net use z: \\192.168.51.1\data", and it is
> successful. However, if I try to do "dir z:", no file found! Same
> behaviour are found in Windows operation, i.e. type
> "\\192.168.51.1\data" under Run box in Start Menu. Strangely,
another
> server with 3.0.14a does not have such problem, and another Windows XP
> does not have such problem too! They can view the files in share
> easily.
> 
> Here comes the log file:
> [2007/05/30 04:13:15, 1] smbd/service.c:close_cnum(885)
>   192.168.2.37 (192.168.2.37) closed connection to service data
> [2007/05/30 04:15:35, 1] smbd/service.c:make_connection_snum(693)
>   192.168.2.37 (192.168.2.37) connect to service data initially as
> user nobody (uid=99, gid=99) (pid 30283)
> [2007/05/30 04:17:00, 1] smbd/service.c:close_cnum(885)
>   192.168.2.37 (192.168.2.37) closed connection to service data
> [2007/05/30 04:17:00, 1] smbd/service.c:make_connection_snum(693)
>   192.168.2.37 (192.168.2.37) connect to service data initially as
> user nobody (uid=99, gid=99) (pid 30301)
> [2007/05/30 04:18:08, 1] smbd/service.c:close_cnum(885)
>   192.168.2.37 (192.168.2.37) closed connection to service data
> 
> Here comes the testparm:
> [global]
>         unix charset = big5
>         workgroup = CC
>         netbios name = CCSERVER
>         server string = Samba Server
>         security = SHARE
>         log file = /var/log/samba/%m.log
>         max log size = 50
>         socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>         printcap name = /etc/printcap
>         dns proxy = No
>         cups options = raw
> 
> [homes]
>         comment = Home Directories
>         read only = No
>         browseable = No
> 
> [printers]
>         comment = All Printers
>         path = /var/spool/samba
>         printable = Yes
>         browseable = No
> 
> [data]
>         comment = Public Data
>         path = /data
>         read only = No
>         create mask = 0777
>         guest ok = Yes
> 
> Also here is the traffic log:
>   0.000000 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [SYN]
> Seq=2266364078 Ack=0 Win=65535 Len=0
>   0.000356 192.168.2.37 -> 192.168.51.1 TCP 1903 > netbios-ssn [SYN]
> Seq=1017632209 Ack=0 Win=65535 Len=0
>   0.010996 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [SYN,
> ACK] Seq=1194648936 Ack=2266364079 Win=5808 Len=0
>   0.011333 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [ACK]
> Seq=2266364079 Ack=1194648937 Win=65535 Len=0
>   0.011445 192.168.2.37 -> 192.168.51.1 SMB Negotiate Protocol Request
>   0.011599 192.168.51.1 -> 192.168.2.37 TCP netbios-ssn > 1903 [SYN,
> ACK] Seq=1190050630 Ack=1017632210 Win=5808 Len=0
>   0.011758 192.168.2.37 -> 192.168.51.1 TCP 1903 > netbios-ssn [RST]
> Seq=1017632210 Ack=1017632210 Win=0 Len=0
>   0.022912 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
> Seq=1194648937 Ack=2266364216 Win=6432 Len=0
>   0.024424 192.168.51.1 -> 192.168.2.37 SMB Negotiate Protocol Response
>   0.025427 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
> Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path:
> \\192.168.51.1\DATA
>   0.039981 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
> Response; Tree Connect AndX
>   0.040262 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> QUERY_PATH_INFORMATION, Path:
>   0.051879 192.168.51.1 -> 192.168.2.37 SMB Transaction2 Response
> QUERY_PATH_INFORMATION
>   0.052291 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>   1.519710 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>   1.530914 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
> Seq=1194652038 Ack=2266364728 Win=7504 Len=0
>  51.023255 192.168.2.37 -> 192.168.51.1 SMB Echo Request
>  51.033769 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
> Seq=1194652038 Ack=2266364781 Win=7504 Len=0
>  85.150658 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [FIN,
> ACK] Seq=2266364781 Ack=1194649246 Win=65226 Len=0
>  85.169401 192.168.51.1 -> 192.168.2.37 NBSS NBSS Continuation Message
>  85.169910 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [ACK]
> Seq=2266364782 Ack=1194649246 Win=65226 Len=0
>  85.170486 192.168.2.37 -> 192.168.51.1 TCP 1904 > microsoft-ds [SYN]
> Seq=3224569487 Ack=0 Win=65535 Len=0
>  85.170724 192.168.2.37 -> 192.168.51.1 TCP 1905 > netbios-ssn [SYN]
> Seq=494418265 Ack=0 Win=65535 Len=0
>  85.179785 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [SYN,
> ACK] Seq=1275220318 Ack=3224569488 Win=5808 Len=0
>  85.180158 192.168.2.37 -> 192.168.51.1 TCP 1904 > microsoft-ds [ACK]
> Seq=3224569488 Ack=1275220319 Win=65535 Len=0
>  85.180250 192.168.2.37 -> 192.168.51.1 SMB Negotiate Protocol Request
>  85.183753 192.168.51.1 -> 192.168.2.37 TCP netbios-ssn > 1905 [SYN,
> ACK] Seq=1269633862 Ack=494418266 Win=5808 Len=0
>  85.183982 192.168.2.37 -> 192.168.51.1 TCP 1905 > netbios-ssn [RST]
> Seq=494418266 Ack=494418266 Win=0 Len=0
>  85.191855 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
> Seq=1275220319 Ack=3224569625 Win=6432 Len=0
>  85.193117 192.168.51.1 -> 192.168.2.37 SMB Negotiate Protocol Response
>  85.194151 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
> Request, User: anonymous; Tree Connect AndX, Path: \\192.168.51.1\IPC$
>  85.208996 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
> Response; Tree Connect AndX
>  85.211152 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
> Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path:
> \\192.168.51.1\DATA
>  85.224557 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
> Response; Tree Connect AndX
>  85.224909 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> QUERY_PATH_INFORMATION, Path:
>  85.236465 192.168.51.1 -> 192.168.2.37 SMB Transaction2 Response
> QUERY_PATH_INFORMATION
>  85.236938 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>  86.510090 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>  86.519567 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
> Seq=1275223532 Ack=3224570399 Win=8576 Len=0
>  96.526425 192.168.2.37 -> 192.168.51.1 SMB Tree Disconnect Request
>  96.536065 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
> Seq=1275223532 Ack=3224570438 Win=8576 Len=0
> 
> (Yes, they are in 2 subnets because they are connected by an IPSec
> tunnels.. however other client that does not exhibit the problem are
> under the same tunnel!)
> 
> If a level 10 log is needed, just tell me and I will post it here.
> 
> Any help is appeciated. Thanks very much!
> 
> Regards,
> Jason Chan
Hi Jason,

have a look at http://lists.samba.org/archive/samba/2005-July/108767.html.
Does that approach solve your needs?

Cheers, Guenter

Chan Jason

2007-May-30 12:34 UTC

head link

[Samba] Re: Problems with Windows 2003 connecting a Samba server

Dear Guenter (and list),
   The article refers to to problem with 2003 and Samba v3, however on
the same machine, I can connect to another samba server with version
3.0.14a. Despite the version differ, the 3.0.14a needs user password,
however I set the problematic server to have "security = share", that
is no need to enter any password to access any file.

   Also, another Windows 2003 within the subnet shows the similar
problem. I do think there is an issue between Windows 2003 as client
and Samba version > 3.0.14 (or related to security=share???)

   For information, the explorer replys "Specified Path cannot be used
(I translated from Chinese, so it may differ)" when trying to access
the share location from Run diaglog box.

   Again, thanks for your help!

Yours sincerely,
Jason Chan
>From: Guenter Kukkukk <linux@kukkukk.com>
>To: samba@lists.samba.org
>Date: Tue, 29 May 2007 23:13:12 +0200
>Subject: Re: [Samba] Problems with Windows 2003 connecting a Samba server
>Am Dienstag, 29. Mai 2007 22:12 schrieb Chan Jason:
> Hi list,
>    I am encountering a problem in connecting a Windows 2003 to a Samba
> 3.0.21b server. The Samba server is configured to have a security >
share option, so that no password is needed. I can connect to the
> server by typing "net use z: \\192.168.51.1\data", and it is
> successful. However, if I try to do "dir z:", no file found! Same
> behaviour are found in Windows operation, i.e. type
> "\\192.168.51.1\data" under Run box in Start Menu. Strangely,
another
> server with 3.0.14a does not have such problem, and another Windows XP
> does not have such problem too! They can view the files in share
> easily.
>
> Here comes the log file:
> [2007/05/30 04:13:15, 1] smbd/service.c:close_cnum(885)
>   192.168.2.37 (192.168.2.37) closed connection to service data
> [2007/05/30 04:15:35, 1] smbd/service.c:make_connection_snum(693)
>   192.168.2.37 (192.168.2.37) connect to service data initially as
> user nobody (uid=99, gid=99) (pid 30283)
> [2007/05/30 04:17:00, 1] smbd/service.c:close_cnum(885)
>   192.168.2.37 (192.168.2.37) closed connection to service data
> [2007/05/30 04:17:00, 1] smbd/service.c:make_connection_snum(693)
>   192.168.2.37 (192.168.2.37) connect to service data initially as
> user nobody (uid=99, gid=99) (pid 30301)
> [2007/05/30 04:18:08, 1] smbd/service.c:close_cnum(885)
>   192.168.2.37 (192.168.2.37) closed connection to service data
>
> Here comes the testparm:
> [global]
>         unix charset = big5
>         workgroup = CC
>         netbios name = CCSERVER
>         server string = Samba Server
>         security = SHARE
>         log file = /var/log/samba/%m.log
>         max log size = 50
>         socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>         printcap name = /etc/printcap
>         dns proxy = No
>         cups options = raw
>
> [homes]
>         comment = Home Directories
>         read only = No
>         browseable = No
>
> [printers]
>         comment = All Printers
>         path = /var/spool/samba
>         printable = Yes
>         browseable = No
>
> [data]
>         comment = Public Data
>         path = /data
>         read only = No
>         create mask = 0777
>         guest ok = Yes
>
> Also here is the traffic log:
>   0.000000 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [SYN]
> Seq=2266364078 Ack=0 Win=65535 Len=0
>   0.000356 192.168.2.37 -> 192.168.51.1 TCP 1903 > netbios-ssn [SYN]
> Seq=1017632209 Ack=0 Win=65535 Len=0
>   0.010996 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [SYN,
> ACK] Seq=1194648936 Ack=2266364079 Win=5808 Len=0
>   0.011333 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [ACK]
> Seq=2266364079 Ack=1194648937 Win=65535 Len=0
>   0.011445 192.168.2.37 -> 192.168.51.1 SMB Negotiate Protocol Request
>   0.011599 192.168.51.1 -> 192.168.2.37 TCP netbios-ssn > 1903 [SYN,
> ACK] Seq=1190050630 Ack=1017632210 Win=5808 Len=0
>   0.011758 192.168.2.37 -> 192.168.51.1 TCP 1903 > netbios-ssn [RST]
> Seq=1017632210 Ack=1017632210 Win=0 Len=0
>   0.022912 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
> Seq=1194648937 Ack=2266364216 Win=6432 Len=0
>   0.024424 192.168.51.1 -> 192.168.2.37 SMB Negotiate Protocol Response
>   0.025427 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
> Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path:
> \\192.168.51.1\DATA
>   0.039981 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
> Response; Tree Connect AndX
>   0.040262 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> QUERY_PATH_INFORMATION, Path:
>   0.051879 192.168.51.1 -> 192.168.2.37 SMB Transaction2 Response
> QUERY_PATH_INFORMATION
>   0.052291 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>   1.519710 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>   1.530914 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
> Seq=1194652038 Ack=2266364728 Win=7504 Len=0
>  51.023255 192.168.2.37 -> 192.168.51.1 SMB Echo Request
>  51.033769 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1902 [ACK]
> Seq=1194652038 Ack=2266364781 Win=7504 Len=0
>  85.150658 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [FIN,
> ACK] Seq=2266364781 Ack=1194649246 Win=65226 Len=0
>  85.169401 192.168.51.1 -> 192.168.2.37 NBSS NBSS Continuation Message
>  85.169910 192.168.2.37 -> 192.168.51.1 TCP 1902 > microsoft-ds [ACK]
> Seq=2266364782 Ack=1194649246 Win=65226 Len=0
>  85.170486 192.168.2.37 -> 192.168.51.1 TCP 1904 > microsoft-ds [SYN]
> Seq=3224569487 Ack=0 Win=65535 Len=0
>  85.170724 192.168.2.37 -> 192.168.51.1 TCP 1905 > netbios-ssn [SYN]
> Seq=494418265 Ack=0 Win=65535 Len=0
>  85.179785 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [SYN,
> ACK] Seq=1275220318 Ack=3224569488 Win=5808 Len=0
>  85.180158 192.168.2.37 -> 192.168.51.1 TCP 1904 > microsoft-ds [ACK]
> Seq=3224569488 Ack=1275220319 Win=65535 Len=0
>  85.180250 192.168.2.37 -> 192.168.51.1 SMB Negotiate Protocol Request
>  85.183753 192.168.51.1 -> 192.168.2.37 TCP netbios-ssn > 1905 [SYN,
> ACK] Seq=1269633862 Ack=494418266 Win=5808 Len=0
>  85.183982 192.168.2.37 -> 192.168.51.1 TCP 1905 > netbios-ssn [RST]
> Seq=494418266 Ack=494418266 Win=0 Len=0
>  85.191855 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
> Seq=1275220319 Ack=3224569625 Win=6432 Len=0
>  85.193117 192.168.51.1 -> 192.168.2.37 SMB Negotiate Protocol Response
>  85.194151 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
> Request, User: anonymous; Tree Connect AndX, Path: \\192.168.51.1\IPC$
>  85.208996 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
> Response; Tree Connect AndX
>  85.211152 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX
> Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path:
> \\192.168.51.1\DATA
>  85.224557 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX
> Response; Tree Connect AndX
>  85.224909 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> QUERY_PATH_INFORMATION, Path:
>  85.236465 192.168.51.1 -> 192.168.2.37 SMB Transaction2 Response
> QUERY_PATH_INFORMATION
>  85.236938 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>  86.510090 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request
> FIND_FIRST2, Pattern: \*
>  86.519567 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
> Seq=1275223532 Ack=3224570399 Win=8576 Len=0
>  96.526425 192.168.2.37 -> 192.168.51.1 SMB Tree Disconnect Request
>  96.536065 192.168.51.1 -> 192.168.2.37 TCP microsoft-ds > 1904 [ACK]
> Seq=1275223532 Ack=3224570438 Win=8576 Len=0
>
> (Yes, they are in 2 subnets because they are connected by an IPSec
> tunnels.. however other client that does not exhibit the problem are
> under the same tunnel!)
>
> If a level 10 log is needed, just tell me and I will post it here.
>
> Any help is appeciated. Thanks very much!
>
> Regards,
> Jason Chan
>
>Hi Jason,
>
>have a look at http://lists.samba.org/archive/samba/2005-July/108767.html.
>Does that approach solve your needs?
>
>Cheers, Guenter

Maybe Matching Threads

Search for more maybe matching threads

samba - May 2007 - Problems with Windows 2003 connecting a Samba server

[Samba] Problems with Windows 2003 connecting a Samba server

[Samba] Problems with Windows 2003 connecting a Samba server

[Samba] Re: Problems with Windows 2003 connecting a Samba server

Maybe Matching Threads