I've just inherited a network that contains Windows 2000 and Windows NT machines. (NT remains the primary server platform.) I need to add new computers and delete old ones. What's the best way to accomplish this task?
All you need is the tried-and-true DOS batch file that lets you add workstations and servers that aren't domain controllers. You simply use the Net Computer command-line utility, which uses the following syntax:
net computer \\computername
You can use the /add or /delete switch. In the following example, the utility adds four new machine accounts to the domain:
net computer \\bob1 /add
net computer \\bob2 /add
net computer \\bob3 /add
net computer \\bob4 /add
net computer \\nt5 /add
To add machine accounts to the Server Manager database, run this utility on the PDC. An administrator can easily synchronize these accounts to a BDC. The /delete switch removes machine accounts from the domain.
Considering the recent frequency of intruders destroying systems, I need to add security to my Windows NT systems to help prevent open ports. Should I implement C2 security for as many ports as possible?
The basic NT architecture presents an inherent vulnerability. NT services use netbt.sys (i.e., NetBIOS over TCP/IP—NetBT), which opens TCP port 139 and UDP ports 137 and 138. As a result, a user-mode program can listen to these ports. This problem exists on all systems running NT 4.0 Service Pack 6a (SP6a) or earlier.
Fortunately, a post-SP6a hotfix or
C2 update, in conjunction with a Registry change, handles the problem. To obtain Netbt-fix, go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/
fixes/usa/nt40/hotfixes-postsp6a/
c2-fix/. Then, go to the HKEY_LOCAL_ MACHINE\SYSTEM\CurrentControlSet\ Services\NetBT\Parameters Registry key and modify (or create) the value EnablePortLocking of type REG_
DWORD. The default value of 0 allows file share access, whereas a value of 1 disallows file share access.
After you apply Netbt-fix and set the value of EnablePortLocking to 1, the system denies user-mode programs access to the aforementioned TCP and UDP ports and enables C2 compliance. C2 security dictates that the system doesn't let any unprivileged user-mode program listen to the TCP and UDP ports. This rule holds regardless of the encryption placed on the NT service traffic that uses these ports. (By default, Windows 2000 doesn't allow file share access to the ports.)
My company has notebook PCs from several manufacturers. All the notebooks run Windows NT 4.0. Some of these machines use the TrackPoint device, and others use the touchpad device. However, I notice problems when I use a mouse on these notebooks. Occasionally, the mouse pointer goes insane: Screens open randomly, the notebook starts beeping, and finally, the pointer simply disappears. Do you know what is happening?
I've seen this behavior in notebooks that use the IBM Ps2 TrackPoint driver and TrackPoint configuration software. Changing the mouse driver or uninstalling the software won't help. To solve your problem, open the TrackPoint application and set the scrolling type to None.
Previous
Register
