Oh no it can't be another Active Directory Help thread :)

[quikslvr311]

OK guys I am new around here. I need some help with active directory. We have recently implemented it and are having some strange problems. Well lets just say we have recently upgraded our NT PDC to win2k server and setup AD. We also replaced a fileserver that was currently running on NT4 as well to win2k Advanced server.

Ok lets get to the problems:
At any given time, users will not be able to login to the network (when they boot up their win2k pro machines, their machines hang upon logging on. I mean up to 20-30 mins) This is on the initial blue screen when you are getting into windows, before the actual logon screen. After about 20 mins they get to the logon screen. They sign in, and wait about 20 more mins, and then they are logged on. DNS is setup correctly for AD.

At any given time, users will not be able to access the newly created fileserver (which as mentioned above is on win2k advanced server. Its a compaq ML750 w/8 900Mhz 2MB cache xeon processors) Users get that the remote machine is unavailable when trying to browse to it.

Now this is also wierd because when all this happens, a reboot of the fileserver cures everything for a given amount of time.

I also forgot to mention that the newly built fileserver is not a DC in AD. I find it wierd that rebooting the fileserver fixes problems (temporarily) I have rebooted it 5 times in the last 2 days. This can obviously not go on much longer or I may be out of a job

Any help would be GREATLY appreciated!!

 

[sevendcruz]

A few questions:

Did you configure wins?

Is DHCP implimented?

 

[quikslvr311]

WINS is configured as well as DHCP. This was an upgrade from an NT4 PDC....

 

[tlcscousin]

Is the NIC on the file server set to allow the system to shut it off to save power when it is not in use?

Device manager properties of the NIC power management.

 

[SupaTech1]

You need to start looking in the event logs of the DC file server and the client machines (should be helpful) please let us nkow if there are any unusual event ID's showing up

 

[quikslvr311]

Checked out the NIC. Power management isn't set up on the NIC.

As far as event ID's I recently replaced the Dual channeled Compaq NIC. Before I replaced it I was getting event ID 2022 refering to not having enough open connections... I applied the so called "microsoft" fix and this did not work out. So I replaced the NIC to a 3com 3c905c-txm NIC and now I do not get that error in the event log, but the machine still completely hangs up with no errors being generated in the event logs..... I am currently in the process of blowing away the system partition and reinstalling Win2k Advanced Server and keeping the data saved on the D and E partitions........ If this doesn't work I may just have to revert back to the old fileserver which is running on NT4 Not sure what else to do. The only major differences between the 2 servers is hardware.

The old fileserver was a compaq DL380 with dual 1000 MHZ pentium processors, the new fileserver is a Compaq ML750 with 8 900 MHZ xeon processors with 2MB cache each.......

 

[SupaTech1]

Have you check the event log on the workstations?

 

[quikslvr311]

I have already tried this. This weekend, I blew away the system partition and reinstalled win2k advanced server from scratch. Same problems. I can't have this happen anymore. I don't have a clue what the problem is. Still getting even id 2022 after applying the MS fix. I think I am going to have to go back to my WinNT box that was stable.......