Comments
-
OK
-
Can you be more specific, what kind of error do you get, have you tried restarting the Firebox?
-
Hi James, I explained myself badly, vmware cloud director is written in the watchgaurd guide and asks to choose "vmware cloud director" but it does not appear in the authpoint (cloud) drop list.
-
Update: these days I have activated the watchguard portal, I have activated the RDP for mine, the strange thing and by connecting the problem of "DNS_PROBE_FINISHED_NXDOMAIN" does not occur, I am going crazy about it ...
-
Hi Ryan, I did not understand, but in any case it is I who sent the ticket and the DNS_PROBE_FINISHED_NXDOMAIN forum, I assure you that by disabling the windws dndcache service the problem will disappear.
-
I have been struggling with this problem for a month now, I found a workaround by deactivating the DNDcache service on the PC (windows 10), a solution already communicated to technical support, I also downgraded the firmware and in fact the problem no longer occurs. for me the problem lies in the DNSWatch service.
-
the problem is random, you have DNSWatch active, abche me on Dimension I don't find anything in the logs
-
the cluster is ok, my problem is browsing the sub domains
-
if you have the possibility to go back to the previous one .... I also have 2 M370 in active / passimo cluster where the upgrade I have great difficulty in navigating the sub domains, open a ticket but for now nothing to do, wait for upgrade ...
-
version 12.7.2 is terrible ... a lot of problems
-
when I opened the ticket to technical support they told me to update to 12.7.2 because my problem was probably related to this BUG, it seems strange to me that no one else has this problem, even in the other office we have this problem arandom on many domains , for now the only thing to do is wait, I did everything, I even…
-
as a matter of fact, if I bypass the firewall and connect directly to my router the problem does not exist. did you see the fix I wrote earlier on version 12.7.2?
-
Hi Bruce, yes sure, already done, I also ipconfgi / flushdns to empty everything mam then double check what is inside the cache, it is empty but the problem persists.
-
Hello, if i disable the dnscache service on the pc (windows 10) the problem seems to disappear, i don't really understand. if you noticed in the changelog of 12.7.2 a fix is mentioned that seems related to my problem: "An issue that caused DNSWatch to refuse requests is resolved. [FBX-22069]"
-
Hi Bruce, with DNSWatch no DNS forwarding enabled, this morning I disabled the "dnscache service" on my PC (windows 10) and re-enabled DNSWatch, I'm doing some tests ....
-
Hello, yes they are all tests that I have already done, even from different PCs, as already described after the update to 12.7.2 and the deactivation of DNSWatch everything works ok, as I reactivate DNSWatch the problem comes back to the surface for what concerns only and exclusively the "watchguard" domain. during the day…
-
Hi James, I can confirm that after the last update 12.7.2 the problem was still in place, after disabling DNSWartch the problem seems to have disappeared, for what I think the problem lies in DNSWatch. this for what concerns the initial post, the problem on my M370 for Watchguard domains "DNS_PROBE_FINISHED_NXDOMAIN"
-
you're welcome
-
OK
-
our cluster ID is 50
-
flush dns on the PC
-
they use these IDs 190/51/2/100/99/188/16/26/17/15, possible some conflict?
-
in fact we have 2 other devices that use vrrp for synchronization, mikrotik
-
me too M370 12.7.1
-
Ok, this already done, I thought there was more to enable per cluster, thanks
-
no problem for me
-
Hello, can you suggest me how?
-
Hello, firewalls are directly connected, ports 6 and 7, no devices using vrrp
-
Hello RVilhelmsen, in fact our configuration is stadard "from the Any-Trusted or Any-Optional aliases. If you set the FireCluster Management Interface to a Trusted or Optional interface, the Management Interface IP addresses are automatically included in the Any-Trusted alias or the Any -Optional alias " it's not that it…
-
Hi Gregg, very simply, through authpoint (watchgaurd cloud) I set the resource / Group and user and the authentication policy then in the webui of the firebox I set authpoint as the default authentication setting. if you need more info let me know, Cristiano