OpenVPN

Have you tried connecting to the shares on the server's LAN IP?  I have 
not used OpenVPN on Windows, but I suspect that file sharing is not 
enabled/allowed on the TUN adapter.

Michael Sharp wrote:

>I have a sever/client setup successfully. The client can connect to the
>VPN server just fine and I can run VNC over the connection just fine.
>
>Both client and server are running the latest OpenVPN software and both
>are XP
>
>Server's TUN IP is 10.66.77.1 and the client is 10.66.77.5
>Servers LAN IP is 192.168.1.100
>
>On the router, port 1194 (UDP) is forwarded to the VPN server. Also, ports
>137-138 (UDP), 445 (TCP), and 139 (TCP) is forwarded to the VPN server.
>
>For testing purposes, I even dropped both the server and clients windows
>firewall.
>
>>From the connected clent, I cannot browse shares (\\10.66.77.1) and map
>shares. The error is that the PATH 10.66.77.1 dosent exist. But I can
>reach 10.66.77.1 via VNC.
>
>Are there any server/cleint setting I may be missing that prevents
>browsing shares?
>
>Server config:
>port 1194
>proto udp
>dev tun
>ca ca.crt
>cert server.crt
>key server.key
>dh dh1024.pem
>server 10.66.77.0/24 255.255.255.0
>ifconfig-pool-persist ipp.txt
>client-to-client
>keepalive 10 120
>tls-auth ta.key 0
>comp-lzo
>persist-key
>persist-tun
>verb 3
>
>Client config:
>client
>dev tun
>proto udp
>remote (MYIP) 1194
>resolv-retry infinite
>nobind
>persist-key
>persist-tun
>mute-replay-warnings
>ca ca.crt
>cert client1.crt
>key client1.key
>ns-cert-type server
>tls-auth ta.key 1
>comp-lzo
>verb 3
>  
>

I just checked and I was able to browse shares using the \\<ip
address\<share name>  and the \\<ip address>  It prompted me for a
userid ID and password as it should but it worked like a charm.

Jerry and Jim, yea I just got everything working like I wanted. It seems =
I
overlooked the documentation that says bridging must used to browse share=
s
and not tunneling.

Thanks to all.

Michael



On Thu, March 2, 2006 4:41 pm, Jim Drash wrote:
> I just checked and I was able to browse shares using the \\<ip
> address\<share name>  and the \\<ip address>  It prompted me for a
> userid ID and password as it should but it worked like a charm.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=12164=
2
> _______________________________________________
> Openvpn-users mailing list
> Openvpn-users@...
> https://lists.sourceforge.net/lists/listinfo/openvpn-users
>

On 3/2/06, Michael Sharp <ms@...> wrote:
> Jerry and Jim, yea I just got everything working like I wanted. It seems =
I
> overlooked the documentation that says bridging must used to browse share=
s
> and not tunneling.
>
> Thanks to all.

This is incorrect. I use shares over multiple subnets all the time.

It is easier to browse shares with bridging, but it can be done with
routiing.  It just requires a more through understanding of Windows
name resolution, routing and firewalls (Windows XP default firewall
allows more access to systems on the local subnet).


P.S. Please don't top post.
--
Leonard Isham, CISSP
Ostendo non ostento.