I believe that setting GroupPolicyMinTransferRate to 0 (zero) in the following keys on the affected workstations fixes this:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
When a client connects...
Best not to - in fact I'm pretty sure you can't do it this way anyway. If you use a new NT box and upgrade it then you're guaranteed a clean install (assuming you test it offline beforehand that is!). This is only a temporary server anyway, once you've got it upgraded to W2K and running AD you...
I *think* the Notify Pause After Modify maximum value is 9999 minutes, i.e. about a week, but I wouldn't put any money on it. This seems to be how it was in Exchange 5.5's DS, which is what AD is based on, but I suspect you're well into unchartered territory here!
I wouldn't really want this happening on my DCs, hence RAID arrays / redundant PSUs / 4 hour hardware callout contracts and all the rest of it. But if I knew that my server was going offline for an extended period, I would dcpromo it out of the picture and put another one in instead, even if it...
Q214678 describes changing the replication interval within a site, but I doubt MS were thinking of intra-site replication intervals of days/weeks when they implemented this, so "interesting" things might well happen.
If your second site is wired up you could have the second server...
You'd need to leave the roles on the first server, and then seize them if you ever put in the second server as a replacement. But I'm not sure that I would set up the second server and then just unplug it and lock it away somewhere. The first server will continue to try to replicate with server...
I suspect the increased traffic is down to the Nachi worm (or variants) - certainly we've seen a marked increase in ICMP traffic over the last month or so.
You might want to try sid2user :
http://www.ntbugtraq.com/default.asp?pid=55&did=6
Sounds like they're deleted accounts though, where the deletions haven't correctly replicated out.
Check to see what context the scheduler service is running under - normally this would be under the System context but if this has been changed, then whatever account it now runs under needs appropriate privileges (i.e. needs to be a member of Backup Operators or Administrators).
When you run...
NALNTService is the Novell Application Launcher for NT, which is client software for ZenWorks, which (usually) runs on a Novell NetWare server. ZenWorks is used to push out security policy and/or applications to client workstations, it's Novell's equivalent of Group Policy. In any case it...
That's the way I read it (MS are talking about upgrading an NT member server to a W2K member server).
Creating a new domain - you could do it that way. I can see why it would look a safer option, but I still think that I prefer using the temporary server scenario above. If the upgrade of the...
Hi mairving,
You're correct in what you say about needing to upgrade the PDC first.
I've upgraded a couple of NT domains to Win2K recently, and I reckon that the safest option is to do what you originally suggested - i.e. build an NT BDC on a temporary machine (service packed and patched)...
reg.exe on the Resource Kit might help you out there. I haven't got it to hand at the moment, but I seem to recall it has more functionality than regini.exe.
hold on, hold on!
You've checked for the possibility of a virus, right, your anti-virus software is up to date?
The changes in Q318755 won't apply until you reboot - BUT I would run
net share
first, to see what shares you have available. If you see (at least) c$ and ipc$ as well as your...
Could be a virus. In any event, looks like you've lost your IPC$ share. Have a look at this:
http://www.annoyances.org/exec/forum/win2000/r1038386353
There is also an article in the MS KnowledgeBase (Q318755) about recreating the administrative shares if they have been removed...
You can do this with winat.exe from the NT Server Resource Kit (a GUI for at.exe) - fire it up, open up the two servers and copy and paste the commands over.
Saves you a lot of typing there, I'm thinking :-)
The Resource Kit for NT and Win2K provides a logoff screensaver (winexit.scr), which you can configure to log the interactive user off after a certain period of inactivity.
It doesn't work too well under NT though:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q156677
Macromedia Authorware Binary? Sound likely?
http://www.macromedia.com/support/authorware/ts/documents/animated_gifs.htm
http://www.macromedia.com/support/authorware/ts/documents/aw_faq.htm
In any case they're not NT system files, but I should be still be careful about deleting them straight...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.