Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
CAD
Contributor

Allow a program that works through the FortiGate

Hello,

 

i have program called (white smoke) working fine before setup fortigate firewall in my network. after installed fortigate my program stop working 

i want one tell me how to allow this program working through forigate.

 

 

thanks

27 REPLIES 27
Nils
Contributor II

cad wrote:

that means all users will be able to access internet.

 

thanks

You can also create a new policy that looks almost like the current one but instead of specify a user, you can specify the source-address where your program is located (the ip-address of the machine running your program).

Put this policy before the current one.

CAD
Contributor

Thanks  for reply,

Sorry for late reply because i am out of my office , i will try to create this policy and will feedback

 

 

thanks

 

CAD
Contributor

Hello, I created policy as told me, but the same thing the program not working. Please see policy in attached file for verification. thanks

CAD
Contributor

Sorry i forgot to upload the policy , please check now

thanks

ede_pfau

And the 'Whitesmoke-Group' contains public IP addresses? Can you ping these from the FGT/Console window? As that will not need a policy, and you will see if the routing is OK.

 

I keep wondering what 'VLAN ID:0' is...no VLAN customarily means VLAN ID 1.

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
CAD

yes! whitesmoke-group content Public IP address. and Vlan ID:0 is Vlan Number we have (3 vlans)

and No response from the whitesmoke's  server ,please check the ping reseult below:

 

FG200D# FG200D# exec ping 63.236.35.30 PING 63.236.35.30 (63.236.35.30): 56 data bytes --- 63.236.35.30 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss FG200D# exec ping 63.236.35.10 PING 63.236.35.10 (63.236.35.10): 56 data bytes --- 63.236.35.10 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss FG200D#

 

thanks.

ede_pfau

So you have proof that the policy is not the culprit (or that the servers don't answer to ping).

What one could do now is set up a packet trace debug (diag debug flow) to see where and why the HTTPS traffic dies. I recommend getting local help from a Fortinet partner as this is getting way to extensive for a forum post (at least IMHO).

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
CAD

Okay , and thanks for your effort

 

 

Regards,

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors