Created on 03-23-2011 10:48 AM
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
PCNSE
NSE
StrongSwan
Created on 03-23-2011 11:22 AM
Created on 03-23-2011 11:47 AM
We' ve configured the FortiGate with the address of our DNS server which is 192.168.2.7 and for secondary DNS, we put a public one, OpenDNS or something probably.Maybe your hitting the public-dns server and it surely is not going to find " host" .purplemonkey.local. Other things to thank about, if the local resolution is the problem ( purplemonkey) what happens when you ping an external resouces www.microsoft.com or www.hp.com etc...? Does it resolve ?
PCNSE
NSE
StrongSwan
Created on 03-24-2011 08:29 AM
Created on 03-24-2011 09:35 AM
As I said, when I used the network monitor to see what was happening, the workstation seems to be hitting the right address for name resolution but it' s not using DNS, it' s using netbios and some other things.have you considered disabling netbios for troubleshooting purpose? tcp ipv4 > properties> advance > netbios/tcp or whatever it is for windows adapter setting. If the problem is with local lookups, than I would start in that area and ensure that the client is not using netbios name resolution. But to me, it sounds like a local dns-server issue.
PCNSE
NSE
StrongSwan
Created on 03-24-2011 10:02 AM
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 |
---|---|
1519 | |
1019 | |
749 | |
443 | |
209 |
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.