Previous Page | Next Page

  1. Introduction
  2. Windows 2000 Professional
  3. Windows 2000 Server
  4. Windows 2000 Advanced Server
  5. Windows 2000 Datacenter Server
  6. Application Support
  7. System Operation
  8. Disks and Volumes
  9. Filesystems
  10. Configuration Files
  11. Security
  12. Network Support
  13. Access Management
  14. Processes
  15. AD Structure
  16. AD Objects
  17. AD Object Naming
  18. AD Schema
  19. AD Sites
  20. Domains
  21. AD Functions
  22. AD Replication
  23. DNS
  24. AD Security
  25. AD Installation
  26. AD Configuration
  27. AD Performance
  28. Installation
  29. Installation Options
  30. Unattended Installation
  31. Software Distribution
  32. Remote Installation Service
  33. Language
  34. Accessibility
  35. File Attributes
  36. Shares
  37. Distributed File System
  38. Control Panel
  39. Active Directory Tools
  40. Computer Management Console Tools
  41. MMC Tools
  42. Network Tools
  43. Network Monitor
  44. System Performance Monitoring
  45. Tools
  46. Managing Services
  47. Connections
  48. TCP/IP
  49. DHCP
  50. Printing
  51. Routing
  52. IPSec
  53. ICS
  54. Fault Tolerance
  55. Backup
  56. System Failure
  57. Services
  58. Remote Access
  59. WINS
  60. IIS
  61. Certificate Server
  62. Terminal Services
  63. Web Services
  64. Authentication
  65. Accounts
  66. Permissions
  67. Groups
  68. User Rights and Auditing
  69. Auditing
  70. User Profiles
  71. Policies
  72. Group Policies
  73. Miscellaneous
  74. Terms
  75. Credits

Windows 2000 TCP/IP

The menu selection "Start", "Settings", "Network and Dial-up Connections" is used to configure TCP/IP. Two ways for a computer to get its IP address:

  • Using DCHP from a DHCP server.
  • Manual configuration.

NetBIOS Name Resolution - See the Network Certification Reference and the WINS Section in the Windows NT Server Reference

  • WINS
  • lmhosts - In \SystemRoot\system32\drivers\etc in Windows 2000 and NT. In Windows NT it is stored in C:\Windows. The #DON keyword indicated the machine is a domain controller. A sample line:

    10.1.0.144 dcmyorg #DOM:mydomain

    A computer that is not a domain controller will not have the information after the #DOM. Notice that the name of the domain is included.

WINS Installation:

  1. Open the Control Panel.
  2. Run the "ADD/Remove Programs" applet.
  3. Click "Add/Remove Windows Components"
  4. Highlight "Networking Services" and click "Details".
  5. Select the "Windows Internet Name Service (WINS)" checkbox.
  6. Click OK and continue.

To make a Windows 2000 computer be a WINS Proxy, edit the registry at HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/NetBT. Add the parameter "EnableProxy with a value type of REG_SZ with a value of 1.

WINS replication is configured using the WINS administrative tool. Select the WINS server to configure, then click "Action", "New Replication Partner". Select "Action" and "Properties" to configure when replication will occur. Types of partners:

  • Push - Notifies its partner when its database changes.
  • Pull - Requests database changes from the WINS server.
  • Push/Pull

If one server is push, the other must be pull, and vice versa. The WINS administrative tool is used to monitor the WINS server. Can view the last replication data and time, NetBIOS queries received, and the actual database contents. The System Monitor may also be used to monitor the WINS server.

Use the "Network and Dial-up Connections" tool selected from "Start", and "Settings" to configure client computers to use WINS servers for NetBIOS name resolution.

DHCP Relay Agent

Used to forward DHCP requests through routers to the DHCP server. Usually the router is configured as the DHCP relay agent, but any computer on the segment to be serviced may be configured as the agent. The "Routing and Remote Access" administrative tool is used to install and configure the DHCP relay agent.

Ports

Windows 2000 server computers are configured as a router or RAS server five each of L2TP and PPTP ports are configured. A demand-dial interface is required for demand dial routing and requires a modem or VPN connection. The "Routing and Remote Access" tool must be used to create demand-dial interfaces and it is also used to configure ports. If the server is configured as a VPN server, 128 PPTP ports and 128 L2TP ports are configured. Up to 30,000 of each type of port can be supported.