i have two vdom , one vdom is policy based and connect to server and client another vdom is profile based and connect WAN .
when configure ldap server in WAN vdom i problem and don't work .
i check and have access between vdom WAN and DC(in VDOM Server)
Not sure what you meant by policy based and profile based VDOMs. But I'm assuming it's about how to apply UTM/UTP.
And, I'm also assuming it's a routing issue between two VDOMs and if you are in the WAN VDOM you can't even ping the LDAP server. How are you routing between two VDOMs to connect WAN and servers? Static routes over a vdom-link or npu-vlink?
Toshi
Created on 03-03-2023 12:08 PM Edited on 03-03-2023 12:22 PM
i used vdom-link and use statick route i have ping
Do you have static routes, one from WAN vdom to server vdom for the server subnet, and a default route from server vdom toward WAN vdom?
yes
Of course you also have sets of policies to allow traffic from/to vdom-link to/from the server interface at least in the server vdom, right?
Then, the ldap server should be reachable from the WAN vdom. Can you ping the server IP from the WAN vdom in CLI? Or can't? If can't, what do you see in traceroute "exe traceroute [server_ip]" from the WAN vdom?
yes
Created on 03-03-2023 01:30 PM Edited on 03-03-2023 01:37 PM
You seem to be a person of few words. I asked multiple questions then your answer was only one 'yes'. Which one is yes then? Have a proper set of policies or the server is pingable from WAN vdom? Or 'yes' and 'yes', you meant? If not what's in the traceroute?
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1740 | |
1108 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.