Event ID 1000 & 1002 on explorer.exe and netapi32.dll

[Pritch5000]

Scenario: NT4 domain with Netware NDS and NDS for NT. New Windows 2003 member servers. DNS and WINS being used hosted by a Windows 2000 member server.

The problem is that when I add an NT4 domain global group to my NTFS security on the new Windows 2003 servers, I get event IDs event IDs 1000 and 1002. Explorer stops and restarts and the share and Explorer window closes. The issue occurs whether I let DNS or WINS do the resolution. The issue occurs even if I click 'Advanced' - 'Find' and select the group from the list. BUT it doesnt occur if I add a user from the domain - only groups (with or without spaces iin the name).

Text from events:

Event ID 1000 reads: "Faulting application explorer.exe, version 6.0.3790.0, faulting module netapi32.dll, version 5.2.3790.0, fault addess 0x000297b0"

Event ID 1002 reads: "The shell stopped unexpectedly and Explorer.exe was restarted"

I get a similar issue with MMC.exe when I add the NT4 domain global group to a local group on Windows 2003 in Computer Management, again the window closes.

I have spoken with the IT department (I am a contractor) and they said they know they get this and workaround it by for example adding the local \Everyone group to the resource. However they dont get this issue on a Windows 2000 Server.

What do I need to 'allow' on my Windows 2003 servers?

Any help appreciated. Thanks

 

[Pritch5000]

Also when the Windows 2003 server logs on it logs event ID 1001 followed by event ID 1004. This also throws up an error to the screen asking me to send the report to Microsoft. On clicking OK it goes round and round in a loop.

That occurs if I let their DHCP server set up the IP, DNS and WINS settings.

If I manually set the IP address to use WINS and not DNS then I only get one event ID 1004 - no eternal loop. Which is interesting.

The DNS and WINS is being hosted by a Windows 2000 server in the NT4 domain and they had to set up an FQDN eg: ntxxxdomain.local whereas their NT domain name is eg: NTXXX

Any thoughts greatly appreciated.

 

[Pritch5000]

I have rebuilt one of the new servers to see when I first get the error on startup (i.e. my second post above).

I purposely avoided their Windows 2000 DNS&WINS server by setting up IP manually and never letting it pick up a DHCP address. I gave it an LMHOSTS file with the 16th char set so that I could add it to the NT domain.

It added ok (as before). And as soon as I tried to add an NT domain based global group into my Windows 2003 local group, MMC.EXE faulted and event 1004 was logged. I did get that error before as well as the one I described in my first post.

On reboot, I am getting event 1004 logged as before. If I try and add a global group into the NTFS permission on the server then Explorer.exe faults.

I have a workaround which is that NT4 domain users can be added individually which is a pain but bereft of any hope I have to do it.

Thanks anyway (ideas still more than welcome though)

 

[Pritch5000]

I have found that I can add the NT4 domain global groups to Microsoft SQL Server login security.

Well that one less place to add a shed load of users individually.

Any ideas would still be appreciated.