Hi Owen
Just to confirm...
You can connect from external (Internet) to your SSLVPN (authentication setup correctly)?
You get an ip address from your SSLVPN pool and in your SSL monitor you can see your connection?
You have either defined SMB access through the Web Portal....or have enabled tunnel mode for your SSLVPN?
You have defined two policies...one for authentication..the other for your ssl.root->internal
If all of the above has been configured correctly then what do you have defined as the services that are allowed from your ssl.root->internal (or wherever your server is?)
What you could try doing is enabling the sniffer on your firewall (debug utility) to capture how the firewall is interpreting your connection attempt:
diag debug flow filter saddr x.x.x.x (where saddr is the ip address you have been allocated for your ssl connection)
diag debug flow filter daddr x.x.x.x (where daddr is the ip address of your server)
diag debug flow show console enable (will enable debugging to the console)
diag debug flow trace start 99 (will capture the first 99 packets)
diag debug flow show function-name enable
diag debug enable (enables debugging)
This will hopefully show up where your problem lies, either through a routing problem or a missing policy.
Fortigate 1000A
v4.0,build194,100121 (MR1 Patch 4)
Fortianalyzer 800B
v4.0,build0130 (MR1 Patch 3)