Ik heb nogal wat problemen met een windows 2000 server die ik beheer. Op de server draait een Sybase SQL server, Exchange Server en dient tevens als domein controller van zo'n 80 PC's.
De server disconnect vaak van het netwerk waardoor de verbinding met de SQL server weg is en de client pc's vastlopen!
De server disconnect vaak van het netwerk waardoor de verbinding met de SQL server weg is en de client pc's vastlopen!
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
| Event Type: Error Event Source: DNS Event Category: None Event ID: 6702 Date: 7-11-2001 Time: 12:44:37 User: N/A Computer: S-LIJNCO Description: DNS Server has updated its own host (A) records. In order to insure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code. If this DNS server does not have any DS-integrated peers, then this error should be ignored. If this DNS server's ActiveDirectory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it. To insure proper replication: 1) Find this server's ActiveDirectory replication partners that run the DNS server. 2) Open DnsManager and connect in turn to each of the replication partners. 3) On each server, check the host (A record) registration for THIS server. 4) Delete any A records that do NOT correspond to IP addresses of this server. 5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the ActiveDirectory DNS server you are updating.) 6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data. Data: 0000: 7c 26 00 00 |&.. |
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
| Event Type: Warning Event Source: DNS Event Category: None Event ID: 7062 Date: 7-11-2001 Time: 12:44:36 User: N/A Computer: S-LIJNCO Description: The DNS server encountered a packet addressed to itself -- IP address 195.38.242.161. The DNS server should never be sending a packet to itself. This situation 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. Example of self-delegation: -> This DNS server dns1.foo.com is the primary for the zone foo.com. -> The foo.com zone contains a delegation of bar.foo.com to dns1.foo.com, (bar.foo.com NS dns1.foo.com) -> BUT the bar.foo.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. Data: 0000: 50 25 00 00 P%.. |
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 7-11-2001
Time: 12:17:00
User: N/A
Computer: S-LIJNCO
Description:
The master browser has received a server announcement from the computer PWOUDE that believes that it is the master browser for the domain on transport NetBT_Tcpip_{0E64F799-4418-44EE-8B. The master browser is stopping or an election is being forced.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........ |
Advanced sheep-counting strategies
:strip_exif()/u/24090/hekje.gif?f=community)
