euh dans mon moniteur d'événements, il y a plusieurs rubriques.
Dans la rubrique application :
il y a plein d'informations que je passerai mais il y a aussi des warning.
"The configuration information of the performance library "C:\WINDOWS\system32\perfts.dll" for the "TermService" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."
et un autre
"A provider, PerfProv, has been registered in the WMI namespace, ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"
dans system il y a plusieurs warnings avec le msg "Cannot register the URL prefix 'https://*:443/' for site '1'. The necessary network binding may already be in use. The site has been deactivated. The data field contains the error number.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"
dans dns server il y a une série violente de warnings avec le msg suivant : "The DNS server encountered a packet addressed to itself on IP address 192.168.0.1. The packet is for the DNS name "pagead2.google.com.". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
Example of self-delegation:
-> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
-> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
(bar.example.microsoft.com NS dns1.example.microsoft.com)
-> BUT the bar.example.microsoft.com zone is NOT on this server.
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record.
You can use the DNS server debug logging facility to track down the cause of this problem.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"
j'ai deux connexions sur mon ordi, une internet et une intranet. l'intranet a la config ip 192.168.0.1 avec le subnet mask 255.255.255.0, pas de gateway, le primary dns qui est 192.168.0.1 et pas de secondary dns.
ma connexion internet a l'ip 192.168.2.3, le masque 255.255.255.0, le gateway 192.168.2.1, le primary dns 192.168.0.1 et pas de secondary. faudrait pas que je mette plutot les dns de mons provider sur ma connexion internet? il faut dire aussi que c'est mon pare-feu physique qui est après avec l'ip 192.168.2.1
j'ai corrigé et mis les dns de mon provider dans la config de ma connexion internet mais ca marche tjs pas. j'ai comme l'impression que c'est peut-être parce que le virtual server est passé en ssl et qu'il y avait peutêtre déj une autre application qui utilisait le port 443. on saurait voir ca comment?
ca a l'air d'être ca car l'erreur système citée plus haut vient de la source W3SVC qui a l'air d'apartenir à l'exchange. maintenant comment résoudre ce ptit problème de port ?
