first just to clarify..your samba server called "GATEWAY" is also your
(ipsec?) vpn server that you are trying to access?
In your smb.conf below you have specified your 192.168.0.1 interface as
the only one to listen on. Maybe adding something like ppp+ will help,
but you still might find samba problematic on temporary interfaces. We
solved this by using a separate pc for a router/gateway/firewall.
Richard Coates.
On Tue, 2003-08-19 at 19:51, Przemyslaw Borkowski wrote:> I have a little network 192.168.0.0/24 with few computers, samba 2.2.8a on
192.168.0.1 with config file below
> [global]
> workgroup = LOCAL
> netbios name = GATEWAY
> server string = Server
> interfaces = 192.168.0.1
> bind interfaces only = Yes
> encrypt passwords = Yes
> update encrypted = Yes
> map to guest = Bad User
> local master = yes
> preferred master = yes
> wins support = Yes
> os level = 0
>
> Also I have pptp based VPN with config:
>
>
> <pptpd.conf>
> option /etc/ppp/options.ppp1
> debug
> localip 192.168.2.1
> remoteip 192.168.2.100-200
> pidfile /var/run/pptpd.pid
>
> <options.ppp1>
> lock
> debug
> name pptpd
> mtu 1450
> mru 1450
> proxyarp
> auth
> +chap
> +chapms-v2
> ipcp-accept-local
> ipcp-accept-remote
> lcp-echo-failure 3
> lcp-echo-interval 5
> deflate 0
> mppe-128
> mppe-stateless
> ms-wins 192.168.0.1
> ms-dns 192.168.0.1
>
>
>
> In local subnet all works fine. But when I connect to local net by VPN, I
have information that I dont have rights to browse local subnet. But when i try
to ping host in local subnet by name. Wins resolves it for me.
> ie.
>
> C:\WINDOWS\Pulpit>ping aga
>
> Badanie aga.local.net [192.168.0.24] z u?yciem 32 bajt?w danych:
>
> Odpowied? z 192.168.0.24: bajt?w=32 czas<10ms TTL=128
> Odpowied? z 192.168.0.24: bajt?w=32 czas<10ms TTL=128
> Odpowied? z 192.168.0.24: bajt?w=32 czas<10ms TTL=128
> Odpowied? z 192.168.0.24: bajt?w=32 czas<10ms TTL=128
>
>
> Can anyone help me to find misconfiguration ?
>
> :)
> przemys?aw Borkowski