[Samba] problem over vpn
Roberto Scattini
roberto.scattini at gmail.com
Tue Jun 25 08:58:29 MDT 2013
hi all,
i have a Samba version 3.2.5 server running in a debian 5.0.8 (a little
old, i know...).
the network setup is:
-one local office using samba
-one remote office (we call it cberg) using samba remotely over a vpn
(linksys-cisco)
-another remote office (we call it colon) using samba remotely over a vpn
(linksys-cisco)
the local office and colon office are working fine
the remote office cberg WAS working fine, until they changed internet
supplier...
now, the problem is that i can browse the shares, but when i want to open a
file, i get an error (after some time) saying something like: "The
specified network name is no longer available".
since then, i have been talking with the network admin about the problem. i
suppose that the problem was caused by the change of the internet supplier
(i was pointing to some MTU problem, since it is a wireless connection). so
i changed the mtu size of the linksys (in the remote office), but the
problem is still there.
i checked connectivity of the two hosts and it is working ok.
i have captured traffic in both ends, but my knowledge is a little limited
here, so if you want i can provide them in some place in the internets.
smbstatus shows the PC connected ("home" machine), among others:
Samba version 3.2.5
PID Username Group Machine
-------------------------------------------------------------------
29130 user1 users1 quiriconi (::ffff:192.168.62.183)
25144 user2 users2 ventas4 (::ffff:100.100.100.21)
26319 user2 users2 home (::ffff:192.168.1.101)
here i have some samba logs of that PC:
[2013/06/25 09:46:22, 1] smbd/service.c:close_cnum(1409)
home (::ffff:192.168.1.101) closed connection to service compras
[2013/06/25 09:48:18, 1] smbd/service.c:make_connection_snum(1198)
home (::ffff:192.168.1.101) connect to service administracion initially
as user forvis (uid=1024, gid=1024) (pid 26463)
[2013/06/25 09:49:27, 1] smbd/service.c:make_connection_snum(1198)
home (::ffff:192.168.1.101) connect to service administracion initially
as user forvis (uid=1024, gid=1024) (pid 26495)
[2013/06/25 09:50:02, 1] smbd/service.c:make_connection_snum(1198)
home (::ffff:192.168.1.101) connect to service bases initially as user
forvis (uid=1024, gid=1018) (pid 26495)
[2013/06/25 09:51:09, 1] smbd/service.c:close_cnum(1409)
home (::ffff:192.168.1.101) closed connection to service bases
[2013/06/25 09:51:09, 1] smbd/service.c:close_cnum(1409)
home (::ffff:192.168.1.101) closed connection to service administracion
[2013/06/25 09:51:09, 1] smbd/service.c:make_connection_snum(1198)
home (::ffff:192.168.1.101) connect to service bases initially as user
forvis (uid=1024, gid=1018) (pid 26608)
[2013/06/25 09:51:09, 1] smbd/service.c:make_connection_snum(1198)
home (::ffff:192.168.1.101) connect to service administracion initially
as user forvis (uid=1024, gid=1024) (pid 26608)
[2013/06/25 09:52:17, 1] smbd/service.c:close_cnum(1409)
home (::ffff:192.168.1.101) closed connection to service administracion
[2013/06/25 09:52:17, 1] smbd/service.c:close_cnum(1409)
home (::ffff:192.168.1.101) closed connection to service bases
[2013/06/25 09:52:17, 1] smbd/service.c:make_connection_snum(1198)
home (::ffff:192.168.1.101) connect to service bases initially as user
forvis (uid=1024, gid=1018) (pid 26638)
[2013/06/25 09:52:17, 1] smbd/service.c:make_connection_snum(1198)
home (::ffff:192.168.1.101) connect to service administracion initially
as user forvis (uid=1024, gid=1024) (pid 26638)
[2013/06/25 10:03:17, 0] lib/util_sock.c:write_data(1141)
[2013/06/25 10:03:17, 0] lib/util_sock.c:get_peer_addr_internal(1683)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/06/25 10:03:17, 0] smbd/process.c:srv_send_smb(74)
Error writing 51775 bytes to client. -1. (Transport endpoint is not
connected)
[2013/06/25 10:03:17, 0] lib/util_sock.c:write_data(1141)
[2013/06/25 10:03:17, 0] lib/util_sock.c:get_peer_addr_internal(1683)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/06/25 10:03:17, 0] smbd/process.c:srv_send_smb(74)
Error writing 75 bytes to client. -1. (Transport endpoint is not
connected)
[2013/06/25 10:04:26, 0] lib/util_sock.c:write_data(1141)
[2013/06/25 10:04:26, 0] lib/util_sock.c:get_peer_addr_internal(1683)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/06/25 10:04:26, 0] smbd/process.c:srv_send_smb(74)
Error writing 51775 bytes to client. -1. (Transport endpoint is not
connected)
[2013/06/25 10:04:26, 1] smbd/service.c:close_cnum(1409)
home (::ffff:192.168.1.101) closed connection to service administracion
which could be the problem?
can anybody help me debug this?
thanks in advance!
--
Roberto Scattini
More information about the samba
mailing list