On 23/09/22 23:22, Sebastian Arcus wrote:
On 23/09/2022 22:16, Sebastian Arcus wrote:
[...]
I an update on progress, but to be honest I can't really make sense
of what it means. Both the server and the client had 'fragment 1300'
in the configs - which I didn't include in my post as I assumed the
problem can't have anything to do with MTU's - since traffic through
the vpn tunnel was working. Through trial and error I discovered that
commenting out 'fragment 1300' on the client, all of a sudden all the
smb traffic starts flowing through the lan. I tested several times,
enabled and disabled 'fragment 1300', and restarted the computer to
be sure - and so far it really seems like it was the culprit. But
frankly that doesn't make any sort of sense to me. I'm going back at
the end of next week to this site to re-run the tests again and again
to be sure - because I can't make sense of why 'fragment 1300' would
have been causing smb traffic to be routed through the tunnel. If
anyone has any ideas, they are very welcome?
Actually, testing things remotely again, I can answer this particular
question myself. Having 'fragment 1300' only on the server effectively
breaks the tunnel - which I didn't realise when I was on site. That is
why it seemed to fix things - as with a disconnected tunnel, it forced
traffic through the lan. I will have to go back there next week and
look again at things using netstat, as per Selva's suggestion
ah, that makes sense, that removing it on one side breaks the tunnel.
Things to try next:
- increase verbosity on the samba server and check the logs when the
client connects; not sure if the IP address will be logged, but it might
give you a hint
- on the windows client, how are accessing the drive ? using IP? using
DNS name? using Netbios name?
- also, things you can test on the Windows 10 client in a
Command/Console window:
nbtstat -c
nbtstat -n
nbtstat -A 192.168.112.1 ## the samba server IP
nbtstat -a Sambaserver ## the samba server Name
both with the VPN up and down - if the Sambaserver names resolves to a
.114 address when the VPN is up, then you've found your problem.
HTH,
JJK
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
