server won't listen

[ivow]

I have a domain controller in one domain who refuses to talk to any other
computers. It connects to the other domain controller with no problems, but
no one else can hit it. It holds the FSMO roles for the domain. I'm running SP2.

I even tried transfering the FSMO roles using MMC and that didn't work. I am
not ready to lose the server, so I'm not going to use ntdsutil.exe yet.

I'm thinking of doing what this article from MS KB asks for, but I just want
to know if I'm going in the right direction:

http://support.microsoft.com/default.aspx?scid=kb;en-us;288167

If anyone has any ideas that would be great:


The event log for it looks good, no errors, however the other DC has the
following events:


Event Type: Warning
Event Source: DNS
Event ID: 5504
Description:
The DNS server encountered an invalid domain name in a packet from
192.168.0.13. The packet is rejected.


Event Type: Error
Event Source: DNS
Event ID: 7063
Description:
The DNS server is configured to forward to a non-recursive DNS server at
192.5.6.30.

DNS servers in forwarders list MUST be configured to process recursive
queries.
Either
1) fix the forwarder (192.5.6.30) to allow recursion
- connect to it with DNS Manager
- bring up server properties
- open "Advanced" tab
- uncheck "Disable Recursion"
- click OK
OR
2) remove this forwarder from this servers forwarders list
- DNS Manager
- bring up server properties
- open "Forwarders" tab
- remove (192.5.6.30) from list of forwarders
- click OK

Event Type: Warning
Event Source: MRxSmb
Event ID: 3034
Description:
The redirector was unable to initialize security context or query context
attributes.
Data:
0000: 00 00 08 00 02 00 56 00 ......V.
0008: 00 00 00 00 da 0b 00 80 ....Ú..?
0010: 00 00 00 00 22 03 09 80 ...."..?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 68 04 00 00 22 03 09 80 h..."..?




"If it's stupid but works, it isn't stupid."

 

[sproosy]

ivow

either reinstall DNS or follow that article. Sounds like it should work. Keep it real!

 

[InfrArch]

Perform a DNS monitoring for errors. Check DNS configuration.
Definitely , install SP3!

try to follow MS article.

Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.

 

[ivow]

Awesome.
I ran what the article I suggested, and bingo, everything is back to normal.

Now at least I have time to plan the deployment of SP3.

Thanks a lot,

Ivo "If it's stupid but works, it isn't stupid."