Hello there!
I did just install a SSL VPN like described in the PDF document " fortigate-sslvpn-40-mr3.pdf"
I did install it as it was decribed there, so, the Webportal works over an ISDN line with the SSLVPNclient software. But what makes me wonder, is this: why does the local Ping not work for my local computers behind the Router? I can do a Ping with the Portal feature (Ping, HTTP, ...), but locally, in a cmd, it won' t work. Also, I can' t browse my Homenetwork. Of course, with the Portal, I can get to the SMB shares in the browser.
So, you think, I did some misconfiguration? Or do I have here some misunderstanding, how a SSLVPN works? I always thought, having configured a VPN, I can browse the homenetwork like sitting behind a local screen.
This is the Ipconfig:
Hostname. . . . . . . . . . . . . : Stephan
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert. . . . . . . : Ja
WINS-Proxy aktiviert. . . . . . . : Nein
Ethernetadapter Fritz:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : AVM FRITZ!web PPP over ISDN
Physikalische Adresse . . . . . . : 00-07-77-64-09-32
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.120.254
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.120.1
DNS-Server. . . . . . . . . . . . : 192.168.120.252
192.168.120.253
PPP-Adapter fortissl:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physikalische Adresse . . . . . . : 00-53-45-00-00-00
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 10.0.0.1
Subnetzmaske. . . . . . . . . . . : 255.255.255.255
Standardgateway . . . . . . . . . : 10.0.0.1
DNS-Server. . . . . . . . . . . . : 192.168.1.10
192.168.1.10
Primärer WINS-Server. . . . . . . : 192.168.1.1
Sekundärer WINS-Server. . . . . . : 192.168.1.1
My home-network has: 192.168.1.0. I also did input the WINS and DNS Server to the SSL config, I have in my local network. I am aware that IP Adress must be the same to be in the local network and be able to ping. At the beginning, I did arrange a local IP range 192.168.1.[215-217] for the IP adress, but in the policy, I cna only enter a whole subnet.
Regards,
Steve
PS: This is the current firmware installed (the latest I guess): v4.0,build0496,111108 (MR3 Patch 3)