xp client over ipsec vpn problem

[kristjanslo]

Hi,


is there anybody with knowledge on vpn connected samba clients. I have managed samba (3.0.24-11.fc6) working fine on LAN, even optimized MTU, rwin, ...


I googled huge amount of pages on the topic. At the current I have working ipsec vpn (using netgear FV114 router and Netgear Prosafe vpn client). Actually connecting to a share works, but is very slow - and checking with tethereal shows that it is producing huge amount of traffic (as pasted below). Experimenting with xmit size, MTU (FYI seems that max MTU allowed by netgear vpn client is < 1400), rwin seems to have little or no effect.

So, if someone sees something in the log or has an idea, please let me know.


regards,
Kristjan


1199662165.288773 192.168.1.32 -> 192.168.10.102 SMB Close Response, FID: 0x301b
1199662165.335831 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv
1199662165.336038 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_FILE_IS_A_DIRECTORY
1199662165.385236 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv
1199662165.385461 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x301e
1199662165.435453 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x301e, Query File Internal Info
1199662165.435667 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x301e, QUERY_FILE_INFO
1199662165.486626 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x301e, Query File Basic Info
1199662165.486826 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x301e, QUERY_FILE_INFO
1199662165.534997 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x301e, Query File Standard Info
1199662165.535226 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x301e, QUERY_FILE_INFO
1199662165.585301 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x301e, Query File EA Info
1199662165.585516 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x301e, QUERY_FILE_INFO
1199662165.636474 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv\:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
1199662165.636674 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_OBJECT_PATH_NOT_FOUND
1199662165.686089 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
1199662165.686278 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_OBJECT_PATH_NOT_FOUND
1199662165.736007 192.168.10.102 -> 192.168.1.32 SMB Close Request, FID: 0x301e
1199662165.736209 192.168.1.32 -> 192.168.10.102 SMB Close Response, FID: 0x301e
1199662165.786488 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv
1199662165.786696 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_FILE_IS_A_DIRECTORY
1199662165.836576 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv
1199662165.836805 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x3021
1199662165.887051 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3021, Query File Internal Info
1199662165.887256 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3021, QUERY_FILE_INFO
1199662165.936507 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3021, Query File Basic Info
1199662165.936727 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3021, QUERY_FILE_INFO
1199662165.987355 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3021, Query File Standard Info
1199662165.987550 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3021, QUERY_FILE_INFO
1199662166.035892 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3021, Query File EA Info
1199662166.036033 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3021, QUERY_FILE_INFO
1199662166.087615 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv\:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
1199662166.087806 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_OBJECT_PATH_NOT_FOUND
1199662166.137234 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
1199662166.137450 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_OBJECT_PATH_NOT_FOUND
1199662166.186638 192.168.10.102 -> 192.168.1.32 SMB Close Request, FID: 0x3021
1199662166.186833 192.168.1.32 -> 192.168.10.102 SMB Close Response, FID: 0x3021
1199662166.239330 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv
1199662166.239552 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_FILE_IS_A_DIRECTORY
1199662166.286961 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv
1199662166.287193 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x3024
1199662166.337217 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3024, Query File Internal Info
1199662166.337428 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3024, QUERY_FILE_INFO
1199662166.388625 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3024, Query File Basic Info
1199662166.388843 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3024, QUERY_FILE_INFO
1199662166.438711 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3024, Query File Standard Info
1199662166.438922 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3024, QUERY_FILE_INFO
1199662166.488734 192.168.10.102 -> 192.168.1.32 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x3024, Query File EA Info
1199662166.488951 192.168.1.32 -> 192.168.10.102 SMB Trans2 Response, FID: 0x3024, QUERY_FILE_INFO
1199662166.538743 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv\:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
1199662166.538948 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_OBJECT_PATH_NOT_FOUND
1199662166.588585 192.168.10.102 -> 192.168.1.32 SMB NT Create AndX Request, Path: \Arhiv:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
1199662166.588784 192.168.1.32 -> 192.168.10.102 SMB NT Create AndX Response, FID: 0x0000, Error: STATUS_OBJECT_PATH_NOT_FOUND

 

[IRudebwoy]

Welcome to samba. SMB is a chatty protocol and works best in a LAN environment. Furthermore, broadcasts don't work well across a WAN link. Using FTP or even SCP to transfer files is far more efficient use of bandwidth.

What was the issue?

Oh yea! Slowness. Unless you increase bandwidth you will not see much gains in speed no matter what you do.

Have Fun!