Hi,
I recently bought a new pc with win 8.1 preinstalled.
Previously I used a win 7 machine which worked just fine.
I configured openvpn the same way as before and it
connects just fine. Routing between the two subnets
also work (192.168.0.0 and 192.168.2.0).
I can ping and connect to my http server on the
192.168.2.0 network.
The only thing which does not work is samba.
Windows Explorer simply refuses to connect to my
server (192.168.2.2).
I believe it's some sort of strange win 8.1 "security feature".
Unfortunately I was unable to find anything after searching
for hours...
Any clues?
Thanks,
Ralf / roop
[solved] Windows 8.1 strange problem with samba shares
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
-
- OpenVpn Newbie
- Posts: 3
- Joined: Thu Jun 11, 2015 7:59 pm
- Traffic
- OpenVPN Protagonist
- Posts: 4066
- Joined: Sat Aug 09, 2014 11:24 am
Re: Windows 8.1 strange problem with samba shares
It is probably your W81 Firewall ..
For further help please post your Openvpn configs and logs.
For further help please post your Openvpn configs and logs.
-
- OpenVpn Newbie
- Posts: 3
- Joined: Thu Jun 11, 2015 7:59 pm
Re: Windows 8.1 strange problem with samba shares
Sorry,
my time is kinda limited at the moment.
Here's my config file:
Log will follow as soon as I got more time.
Thanks.
Ralf / roop
my time is kinda limited at the moment.
Here's my config file:
Code: Select all
dev tun
tls-client
remote [removed] 1194
tun-mtu 1500
mssfix 1400
pull
proto udp
#not needed...
#script-security 2
ca ca.crt
auth-user-pass pw.txt
comp-lzo
reneg-sec 0
keepalive 3 10
# log-append /Data/openvpn.log
Thanks.
Ralf / roop
-
- OpenVpn Newbie
- Posts: 3
- Joined: Thu Jun 11, 2015 7:59 pm
Re: Windows 8.1 strange problem with samba shares
Hi,
I wrote a post but it never showed up in this thread.
BUT your post helped a lot! Thank you so much!
In fact it was an firewall issue.
Thanks,
Ralf / roop
I wrote a post but it never showed up in this thread.
BUT your post helped a lot! Thank you so much!
In fact it was an firewall issue.
Thanks,
Ralf / roop