1. Configure Internet access for DNS in Windows Server 2003
Summary
This step-by-step guide explains how to configure Domain Name System (DNS) in Windows Server 2003 Products
Internet access. DNS is the core name resolution tool used on the Internet. DNS is responsible for host name and
Analysis between Internet addresses
1. How to run Windows Server 2003 from a standalone server
Start The independent server running Windows Server 2003 becomes the network’s DNS server. The first step is to assign a static Internet protocol (IP) address to the server. DNS servers should not use dynamically assigned IP addresses, because dynamic changes to the address will cause the client to lose contact with the DNS server.
Step 1: Configure TCP/IPCopyright
Click Start, point to Control Panel, point to Network Connections, and then click Local Connections.
Click Properties.
Click Internet Protocol (TCP/IP). , and then click Properties.
Click the General tab.
Click Use the IP address below, and then type the IP address, subnet mask, and default gateway address in the corresponding box.
Click Advanced and then click the DNS tab.
Click to attach the primary and connect to specific DNS suffix.
Click to select the parent suffix check box with the append primary DNS suffix.
Click to select the Register the address of this connection in DNS check box.
Note that the DNS server running Windows Server 2003 must specify its DNS server as itself.
If the server needs to resolve the name from its Internet Service Provider (ISP), you must configure a forwarder. The forwarder will be discussed later in this article. Click OK three times.
Note: If you receive a warning from the DNS cache resolver service, click OK to close the warning. The cache resolver is trying to contact the DNS server, but you have not completed the configuration of the server.
Step 2: Install the Microsoft DNS server
Click Start, point to Control Panel, and then click Add or Remove Programs.
Click to add or delete Windows components.
In the Components list, click Network Services (but do not select or clear the check box), and then click Details.
Click to select the Domain Name System (DNS) check box, and then click OK.
Click Next.
After getting the prompt, insert the Windows Server 2003 CD-ROM into the computer's CD-ROM or DVD-ROM drive.
When the installation is complete, click Finish on the Finish Windows Component Wizard page.
Click Close to close the Add or Remove Programs window.
Step 3: Configure the DNS server
To configure DNS using the DNS snap-in in the Microsoft Management Console (MMC), follow the following steps xx:
Click Start, point to Programs, point to Administrative Tools, and then click DNS.
Right-click the forward search area and click New Area.
When the "New Area Wizard" starts, click Next.
You will then be prompted to select the region type. Area types include:
Main Zone: Create a copy of the zone that can be updated directly on this server. This area information is stored in a .dns text file.
Auxiliary Zone: The standard auxiliary zone copies all information from its primary DNS server. The primary DNS server can be an Active Directory zone, main zone or auxiliary zone configured for zone replication. Note that you cannot modify the zone data on the secondary DNS server. All data is copied from the main DNS server.
Stub area: The Stub area only contains resource records required by the authoritative DNS server that identifies the region. These resource records include name server (NS), starting authority (SOA) and possible glue host (A) records. There is also an option in Active Directory to store areas. This option is only available when the DNS server is a domain controller. The new forward search area must be a primary area or an Active Directory integrated area so that it can accept dynamic updates.
Click Main, and then click Next.
The new area contains the locator record of the Active Directory-based domain. The region name must be the same as the domain name based on Active Directory, or it is the logical DNS container for that name. For example, if the name of a domain based on Active Directory is "", then the valid region name can only be "".
Accept the default name of the new region file. Click Next.
Note: Experienced DNS administrators may want to create a reverse search area, so they are advised to study this branch of the wizard. The DNS server can resolve two basic requests: forward search request and reverse search request. Forward search is more common. Forward search resolves the host name to an IP address with "A" or host resource record. opposite
Resolve the IP address to a host name with a PTR or pointer resource record to the search. If you have configured reverse
DNS zone, you can automatically create associated reverse records when creating original forward records.
2. How to remove the root DNS zone
The DNS server running Windows Server 2003 follows specific steps during its name resolution. The DNS server first querys its cache, then checks its zone records, then sends the request to the forwarder, and finally uses the root server to try to resolve.
By default, the Microsoft DNS server connects to the Internet to further process DNS requests with the root prompt. When using the Dcpromo tool to promote the server to a domain controller, the domain controller requires DNS. If DNS is installed during the promotion process, a root zone will be created. This root zone indicates to your DNS server it is a root Internet server. Therefore, your DNS server does not use a forwarder or root prompt during name resolution. Click Start, point to Administrative Tools, and then click DNS.
Expand ServerName, where ServerName is the name of the server, click Properties, and then expand the Forward Search area.
Right-click the "." area and click Delete.
3. How to configure the forwarder
Windows Server 2003 can make full use of the DNS forwarder. This function forwards DNS requests to external servers. If the DNS server cannot find the resource record in its zone, the request can be sent to another DNS server for further attempts to resolve. A common situation is to configure a forwarder to your ISP’s DNS server.
Click Start, point to Administrative Tools, and then click DNS.
Right-click ServerName, where ServerName is the name of the server, and then click the Forwarder tab.
Click on a DNS domain in the DNS domain list. Or click New, type the name of the DNS domain you want to forward the query in the DNS domain box, and then click OK.
In the forwarder IP address box of the selected domain, type the IP address of the first DNS server you want to forward to, and then click Add.
Repeat step 4 to add the DNS server you want to forward to.
Click OK.
4. How to configure the root prompt
Windows can use root prompts. The root prompt resource record can be stored in Active Directory or text file (%SystemRoot%\System32\DNS\). Windows uses standard Internic root servers. In addition, when a server running Windows Server 2003 querys the root server, it will update itself with the latest root server list.
Click Start, point to Administrative Tools, and then click DNS.
Right-click ServerName, where ServerName is the name of the server, and then click Properties.
Click the root prompts tab. The root server of the DNS server is listed in the name server list.
5. How to configure DNS behind a firewall
Agent and Network Address Translation (NAT) devices can restrict access to ports. DNS uses UDP port A and TCP port 53. The DNS service management console also uses RCP. RCP uses port 135. These problems can occur when you configure DNS and firewalls.
2. Configure remote domains for Internet Information Services SMTP mail relay server in Windows Server 2003
Summary
This article introduces how to relay emails for "Internet Information Service" (IIS) "Simple Mail Transfer Protocol" (SMTP)
The server configures the remote domain.
IIS in Windows Server 2003 includes a fully functional SMTP virtual server that you can use
Servers deliver mail on your internal network. The SMTP virtual server can also be used to receive emails from the Internet. Although the SMTP service does not provide an easy-to-access email retrieval mechanism, its role is very important for accepting mail from the Internet and relaying mail to the SMTP/POP3 server. For the domain to which the computer belongs, as well as other domains, you can configure the SMTP virtual server to accept emails.
Using a standalone server running SMTP services is a good security measure because it acts as an enterprise mail server.
The isolation layer between inbound connections from the Internet. A standalone computer based on Windows Server 2003 will isolate the server from the Active Directory security boundary of the internal network. You can configure a standalone SMTP virtual server to use the company mail server as a smart host. You can then configure a standalone SMTP virtual server to relay mails sent to the remote domain only. In this way, all other emails will be rejected and will not be relayed.
1. How to configure an independent IIS SMTP server to relay to the remote domain
Start the "Internet Information Service Manager" or open the "Internet Information Services (IIS)" snap-in. Expand the server name, where the server name is the name of the server, and then expand "Default SMTP Virtual Server".
Right-click the domain, point to New, and then click Domain.
Click Remote and click Next.
Type the name of the new remote domain in the Name box.
You can specify a single domain, or use an asterisk (*) as a wildcard (the asterisk must start with the name and you want to
Use periods to separate the asterisk from the rest of the name) to specify multiple fields. For example, if you need a remote domain to receive another domain.
com Mails for all subdomains, you can use the name *.other domain.com. Click Finish.
In the right pane, right-click the new remote domain you just created and click Properties.
Click the General tab.
Under Select the appropriate settings for the remote domain, click the Allow inbound mail relay to this domain check box and select it to enable the SMTP server to act as a mail relay.
Under Routing Domain, click Forward All Mail to Smart Host, and then type the IP address or fully qualified domain name (FQDN) of the company's mail server for the internal network. If you use an IP address, you must enclose the IP address in brackets "[]". For example,[].
Click OK.
Stop and start the SMTP virtual server. To do this, right-click "Default SMTP Virtual Server" and start alone.
2. Troubleshooting
After the remote domain is configured, all emails sent to the remote domain name will be relayed to the smart host you configured. Mails that cannot be delivered will be stored in the Inetpub\Mailroot\Badmail folder
Summary
This step-by-step guide explains how to configure local domains for SMTP services in Windows Server 2003. This article explains
How to change the name of the default domain, configure the alias domain, and specify the Drop folder.
SMTP service domain is used to organize the messages to be delivered. SMTP virtual server has at least one domain: the default local domain.
The local domain is a domain name system (DNS) domain provided by the local SMTP server. Inclusion of arrival at the SMTP server
Messages of local domain names are either sent locally to the Drop folder or are returned to the sender with an untransmitted (NDR) report.
1. How to rename the default domain
The default domain is used to stamp messages from addresses that do not contain the domain. SMTP virtual server must have a default domain. This default domain cannot be deleted.
By default, the name specified in the Computer Name tab of the Control Panel system tool is used as the default domain name.
. You can also specify a unique name as the default domain name of the SMTP service.
2. To rename the default domain, follow the following steps xx:
Start the Microsoft Internet Information Services (IIS) Manager or open the IIS snap-in.
Expand Server_name, where Server_name is the name of the server, and then expand the required SMTP virtual server
Server (for example, the default SMTP virtual server).
Click on the domain.
In the right pane, right-click the default field and click Rename.
Type the name you want to use and press ENTER.
Exit the IIS Manager or close the IIS snap-in.
3. How to configure alias domain
Alias domain is an alias for the default domain. The alias domain can be set using the same settings as the default domain. SMTP service received
Messages for the alias domain are placed in the Drop folder specified for the default domain.
To configure the alias domain, follow the following steps xx:
Start the IIS Manager or open the IIS snap-in.
Expand Server_name, where Server_name is the name of the server, and then expand the required SMTP virtual server
Server (for example, the default SMTP virtual server).
Right-click the domain, point to New, and then click Domain.
"New SMTP Domain Wizard" starts.
Click the alias and click Next.
Type the name of the alias domain in the Name box and click Finish.
Exit the IIS Manager or close the IIS snap-in.
4. How to specify the Drop folder
For the default domain, you must specify a folder where all incoming messages are placed. SMTP service puts messages from the alias domain
In the Drop folder used by the default domain.
By default, the Drop folder is located in the Inetpub\Mailroot folder. You can specify any folder as a Drop folder as long as the folder is a local folder on the computer where the SMTP service is installed and not specified as a Pickup folder.
To change the location of the Drop folder, follow the following steps xx:
Start the IIS Manager or open the IIS snap-in.
Expand Server_name, where Server_name is the name of the server, and then expand the required SMTP virtual server
Server (for example, the default SMTP virtual server).
Click on the domain.
In the right pane, right-click the default field and click Properties.
Click Browse, locate and click the folder you want to use as the Drop folder, and then click OK.
Click OK.
SummaryCopyright
This article introduces how to configure packet filter support for PPTP VPN clients.
Windows Server 2003 "Routing and Remote Access" service supports Virtual Private Networks (VPN). VPN clients can use Point-to-Point Tunneling Protocol (PPTP), Layer 2 Tunneling Protocol (L2TP) and IP Security (IPSec) to create a secure tunnel to a VPN server based on Windows Server 2003. In this way, the client becomes a remote node on the private network.
Multi-host "routing and remote access" service with external interfaces that directly connect to the Internet. VPN servers can use packet filtering to protect internal networks from external attacks. The best way to configure packet filters in a secure environment is to use the least privilege Principle: discard all packets except those explicitly allowed.
How to configure PPTP filter to allow communication of PPTP VPN client PPTP is a commonly used VPN protocol because it is safe and easy to set up. You can easily deploy PPTP in both pure Microsoft environments and hybrid environments. You can configure the Windows Server 2003-based “Routing and Remote Access” service VPN server to discard non-PPTP packets by using the packet filter.
How to configure PPTP Input filter to allow inbound communication from PPTP VPN client Click Start, point to Programs, point to Administrative Tools, and then click Routing and Remote Access.
In the left pane of the Routing and Remote Access console, expand Server, and then expand IP Routing.
Click General, right-click the external interface, and then click Properties.
Click the General tab, click Inbound Filter, and then click New.
Click the "Target Network" check box, select it, and then in the "IP Address" box, type the IP address of the external interface. In the Subnet Mask box, type 255.255.255.255.
In the Protocol box, click TCP. In the Destination Port box, type 1723, and then click OK.
Click "Discard all packages, except those that meet the following conditions".
Click New.
Click the "Target Network" check box and select it. In the "IP Address" box, type the IP address of the external interface.
In the Subnet Mask box, type 255.255.255.255.255.
In the Agreement box, click Other. In the Protocol Number box, type 47, and then click OK twice.
How to configure PPTP Output Filter to allow outbound communication to the PPTP VPN client Click Start, point to Programs, point to Administrative Tools, and then click Routing and Remote Access.
In the left pane of the Routing and Remote Access console, expand your server, and then expand IP Routing.
Click General, right-click the external interface, and then click Properties.
Click the General tab, click Outbound Filter, and then click New.
Click the "Source Network" check box and select it. In the "IP Address" box, type the IP address of the external interface. In the Subnet Mask box, type 255.255.255.255. In the Protocol box, click TCP. In the Source Port box, type 1723, and then click OK.
Click the option "Discard all packages, except those that meet the following conditions".
Click the "Source Network" check box and select it. In the "IP Address" box, type the IP address of the external interface.
In the Agreement box, click Other. In the Protocol Number box, type 47, and then click OK twice.
Note: After these changes are completed, only PPTP communication can enter and exit the external interface of the VPN server. These filters support communicating with PPTP VPN clients that make inbound calls to the Routing and Remote Access Service VPN server.
5. Configure network security for SNMP services in Windows Server 2003
Summary
This step-by-step guide introduces how to serve as the "Simple Network Management Protocol" (SNMP) server in Windows Server 2003
Configure network security.
The SNMP service acts as a proxy, which collects information that can be reported to the SNMP management station or console. You can use the SNMP service to collect data and manage it based on Windows Server across the entire company's network.
2003, Microsoft Windows XP and Microsoft Windows 2000 computers.
Generally, the method to protect communication between SNMP agents and SNMP management stations is to specify these agents and management stations.
A shared community name. When the SNMP management station sends a query to the SNMP service, the community name of the requesting party is compared with the community name of the agent. If it matches, it means that the SNMP management station has passed the authentication. If it does not match, it means that the SNMP agent considers the request a "failed access" attempt and may send an SNMP trap message.
SNMP messages are sent in plain text. These plaintext messages are easily intercepted and decoded by network analysis programs such as "Microsoft Network Monitor". Unauthorized persons can capture community names for important information about network resources.
"IP Security Protocol" (IPSec) can be used to protect SNMP communications. You can create an IPSec policy that protects communications on TCP and UDP ports 161 and 162 to protect SNMP transactions.
Create a filter list
To create an IPSec policy that protects SNMP messages, you must first create a filter list. The method is:
Click Start, point to Administrative Tools, and then click Local Security Policy.
Expand Security Settings, right-click "IP Security Policy on Local Computer", and then click "Manage IP Filter"
List of the user and filtersxxdo”。
Click the "Manage IP Filter List" tab, and then click Add.
In the IP Filter List dialog box, type the SNMP message (161/162) (in the Name box), and then type TCP and UDP ports 161 filter (in the Description box).
Click the Use the Add Wizard check box, clear it, and then click Add.
In the Source Address box (located on the Address tab of the IP Filter Properties dialog box displayed), click Any IP Address. In the Destination Address box, click My IP Address. Click the "Mirror. Match packets with exactly the opposite source and destination addresses" check box to select it.
Click the Agreement tab. In the Select Protocol Type box, click UDP. In the Set IP Protocol Port box, click From this port, and then type 161 in the box. Click "To this port" and type 161 in the box.
Click OK.
In the IP Filter List dialog box, click Add.
In the Source Address box (located on the Address tab of the IP Filter Properties dialog box displayed), click Any IP Address. In the Destination Address box, click My IP Address. Click the "Mirror. Match packets with exactly the opposite source and destination addresses" check box to select it.
Click the Agreement tab. In the Select Protocol Type box, click TCP. In the Set IP Protocol box, click From this port, and then type 161 in the box. Click To this port, and then type 161 in the box. Click OK.
In the IP Filter List dialog box, click Add.
In the Source Address box (located on the Address tab of the IP Filter Properties dialog box displayed), click Any IP Address. In the Destination Address box, click My IP Address. Click the "Mirror. Match packets with exactly the opposite source and destination addresses" check box to select it.
Click the Agreement tab. In the Select Protocol Type box, click UDP. In the Set IP Protocol box, click From this port, and then type 162 in the box. Click "To this port" and type 162 in the box.
Click OK.
In the IP Filter List dialog box, click Add.
In the Source Address box (located on the Address tab of the IP Filter Properties dialog box displayed), click Any IP Address. In the Destination Address box, click My IP Address. Click the "Mirror. Match packets with exactly the opposite source and destination addresses" check box to select it.
Click the Agreement tab. In the Select Protocol Type box, click TCP. In the Set IP Protocol box, click From this port, and then type 162 in the box. Click To this port, and then type 162 in the box.
Click OK.
Click OK in the IP Filter List dialog box, and then click OK in the "Manage IP Filter List and Filter xx" dialog box.
Create an IPSec policy
To create an IPSec policy to enforce IPSec on SNMP communication, please follow the following steps xx:
Right-click "IP Security Policy on Local Computer" in the left pane, and then click Create IP Security Policy. The "IP Security Policy Wizard" starts.
Click Next.
Type Secure SNMP in the Name box on the "IP Security Policy Name" page. In the Description box, type Force IPSec for SNMP Communications, and then click Next.
Click the Activate Default Response Rules check box, clear it, and then click Next.
On the "Completing IP Security Policy Wizard" page, confirm that the Edit Properties check box has been selected and click Finish.
In the Security SNMP Properties dialog box, click the Use "Add Wizard" check box, clear it, and then click Add.
Click the IP Filter List tab, and then click SNMP Message (161/162).
Click the Filter xx as the tab, and then click Security Required.
Click the Authentication Methods tab. The default authentication method is Kerberos. If you need another method of authentication, click Add. In the New Authentication Method Properties dialog box, select the authentication method you want to use from the list below, and click OK:
Active Directory Default Value (Kerberos V5 Protocol)
Use this string (pre-shared key)
In the New Rule Properties dialog box, click Apply, and then click OK.
In the SNMP Properties dialog box, confirm that the SNMP Message (161/162) check box has been selected, and then click OK.
In the right pane of the Local Security Settings console, right-click the Security SNMP Rules, and then click Specify.
Complete this process on all Windows-based computers running SNMP services. SNMP management station must also
Configure this IPSec policy.
Summary
This article describes how to configure the Domain Name System (DNS) server so that its hosting can be accessed from the outside (i.e. from
Internet access) Web site.
How to get IP address
To host an externally accessible Web site, you must obtain it from your Internet Service Provider (ISP)
Take a public IP address. And specify this IP address to the outside of the firewall or router connected to the DNS server.
Interface
How to register a domain name
Register for your organization through the Internet domain name registry (such a management organization is called a registry)
A parent or secondary DNS domain name. For a list of globally recognized registries, please visit the following
Internet Corporation for Assigned Names and Numbers (ICANN) Website:
Internet Corporation for Assigned Names and Numbers
The registration process for each registration agency may vary, but you can still register a domain name as follows:
Search to confirm that the name you want to register is available.
Provide contact information and payment information for this account (including email address).
Type the fully qualified domain name (FQDN) of the master-slave DNS server.
Note: These are public IP addresses provided by ISP.
Pay annual fees or prepare for annual fees.
How to configure the web server
Install and configure Microsoft Internet Information Services (IIS) (if not installed yet).
How to create a DNS item for a web server
Please create an alias or CNAME record for the DNS server with IIS configured. This ensures that the external host can
Use the "www" hostname to connect to your web server. The creation method is:
Open the DNS snap-in. The method is: click Start, point to Administrative Tools, and then click DNS.
Under DNS, expand "Host Name" (where the host name is the host name of the DNS server).
Expand the forward search area.
Under Forward Search Area, right-click the desired area (for example, domain name.com.), and click New Alias
(CNAME)。
In the Alias box, type www.
In the "Full Qualified Name of the Target Host" box, type the fully qualified master of the DNS server that IIS is installed
Machine name. For example, type dns.domain.com and click OK.
Overview
You must activate the license server before it can issue a license to the Terminal Services client. When the license server is activated, Microsoft provides this server with a digital certificate that verifies the server's ownership and identity. By using this certificate, the license server can conduct business with Microsoft and receive client licenses for your terminal server. When the Terminal Services client first tries to log in to the terminal server, the terminal server contacts the license server and requests a license for that client.
To activate a license server using Terminal Server Authorization, you can use any of the following methods:
Automatic activation
Web Browser
Telephone
Note: The steps introduced in this article assume that the server has "Terminal Server Authorization". To perform these procedures, you must also be a member of the local "Administrators" group.
Automatically activate the license server
Click Start, point to Administrative Tools, and then click Terminal Server Authorization.
In the console tree, expand All Servers.
Right-click the license server you want to activate, and then click Activate Server. The Terminal Server License Server Activation Wizard will start.
Click Next.
On the Connect Methods page, click Automatic Connect (Suggestions) in the Activate Methods box, and then click Next.
On the Company Information page, type your name, company, and country information, and then click Next.
Specify any additional information you need, such as email and company address, and click Next.
Note: The information on this page is optional. This activates your license server.
On the "Complete Terminal Server Activation Wizard" page, execute one of the following xx works:
To install the client license key package for the license server, click Next. Follow the instructions in the Terminal Server Client License to install the client license.
If you want to install the client license key package later, click the "Start the Terminal Server Client Authorization Wizard now" check box, clear it, and then click Finish.
Close the terminal server authorization window.
Activate the license server by using a web browser
Click Start, point to Administrative Tools, and then click Terminal Server Authorization.
In the console tree, expand All Servers.
Right-click the license server you want to activate and click Activate Server. The "Terminal Server License Server Activation Wizard" will start.
Click Next.
On the Connect Method page, click Web Browser in the Activate Method box, and then click Next.
On the License Server Activation page, click the hyperlink connected to the Terminal Server Activation and Authorization Web site.
Under Select Options, click Activate License Server and click Next.
Type your product ID (displayed on the License Server Activation page of the Terminal Server License Server Activation Wizard), name, company, and country or region information in the appropriate box, and then click Next. You will receive your license server ID.
On the License Server Activation page, type the license server ID you received in step 8, and then click Next. This activates your license server.
On the "Complete Terminal Server Activation Wizard" page, execute one of the following xx works:
To install the client license key package for the license server, click Next. Install the client license as described in the Terminal Server Client Authorization Wizard.
To install the client license key package later, click the "Start the Terminal Server Client Authorization Wizard now" check box, clear it, and then click Finish.
Close the terminal server authorization window.
Activate the license server via phone
Click Start, point to Administrative Tools, and then click Terminal Server Authorization.
In the console tree, expand All Servers.
Right-click the license server you want to activate and click Activate Server. The Terminal Server License Server Activation Wizard will start.
Click Next.
On the Connect Method page, click Phone in the Activate Method box, and then click Next.
On the Country Selection page, click your country and then click Next to display the corresponding phone number to call.
Call Microsoft using the phone number displayed on the License Server Activation page, and then provide the Microsoft Customer Support representative with the Product ID displayed on your screen. You will also need to provide your name, organization name, and the type of authorization plan to use. The customer service representative will then process your request to activate the license server and create a unique ID for your license server.
Type the license server ID provided by the customer service representative and click Next. This activates your license server.
On the "Complete Terminal Server Activation Wizard" page, execute one of the following xx works:
To install the client license key package for the license server, click Next. Follow the instructions in the Terminal Server Client License to install the client license.
To install the client license key package later, click the "Start the Terminal Server Client Authorization Wizard now" check box, clear it, and then click Finish.
Close the terminal server authorization window.
Troubleshooting
After the license server is activated, it will become the registrar for the "Terminal Services" client license. "Waiting for completion of the " server, the duration is up to 120 days.
You can change the Authorization Wizard attribute, for example, the connection method and company information set using the Terminal Server Authorization during activation. To achieve this, follow the steps below:
Click Start, point to Administrative Tools, and then click Terminal Server Authorization.
In the console tree, expand All Servers.
Right-click the license server you want to modify and click Properties. The Terminal Server License Server Activation Wizard will start.
Specify the required information and settings in the Installation Method, Required Information, and Optional Information tab, and click OK.
Close the terminal server authorization window.
How to Change Refresh Frequency for Your Monitor Click Start, point to Control Panel, and then click Show. You can also right-click the desktop and click Properties.
Click the Settings tab, and then click Advanced.
Click the Monitor tab.
In the Refresh Frequency box, click the screen refresh frequency you want to use.
Click OK, and then click OK.
Note: While your monitor may support higher settings, the default refresh frequency settings are determined by the hardware. For more information on the settings supported by your monitor, check out the manufacturer documentation that comes with your monitor.
If you use a higher refresh frequency, you can reduce the frequency of the screen flickering. However, if the refresh frequency you specify is too high for the monitor, the screen may become unusable and your hardware may be damaged.
Changing the refresh frequency will affect all users logged into the computer.
How to change the refresh frequency of the monitor when the display is blurry (not clear). If the computer displays blurry, or you cannot view the contents of the screen, it may be because the display settings such as the refresh frequency of the monitor are not configured correctly. To diagnose and resolve this issue, start the computer by using the Enable VGA Mode boot option and change the refresh frequency to use the correct settings. When starting the computer in VGA mode, the video driver currently installed on the computer is loaded using the lowest screen resolution, color depth and refresh frequency settings.
To start the computer in VGA mode, use one of the following methods:
Restart the computer using the "Enable VGA Mode" startup option.
When you see the message "Please select the xx to start as the system", press the F8 key.
In the "Windows Advanced Options" menu, use the arrow keys to select Enable VGA mode, and then press the ENTER key.
If you want to use a dual-boot or multi-boot computer, select Microsoft Windows Server 2003 and press ENTER.
Log in to your computer and follow the steps described in the "How to Change Refresh Frequency for Your Monitor" section earlier in this article to do xx.
Using the /Basevideo switch in a file You can also force the computer to start in VGA mode by configuring the file. To achieve this, edit to include the /basevideo switch. This setting corresponds to enabling the VGA mode startup item.
After starting the computer and logging in, change the refresh frequency of the monitor according to the steps xx described in the "How to Change the Refresh Frequency for Your Monitor" section in the previous article.
Summary
This article describes how to change the IP address assigned to a network adapter. If your network has a "Dynamic Host Configuration Protocol" (DHCP) server, the IP address will be automatically assigned, otherwise you can specify an IP address.
How to change the IP address assigned to the network adapter to log in to the computer using the administrator account.
Click Start, point to Control Panel, point to Network Connections, and then click the local connection you want to modify.
In the Connection Status dialog box, click Properties.
Right-click the required local connection and click Properties. The Local Network Connection Properties dialog box appears on the screen.
In the "This connection uses the following items" box, click Internet Protocol (TCP/IP), and then click Properties. The "Internet Protocol (TCP/IP) Properties" dialog box will appear on the screen.
Continue with the steps in one of the two sections below (selected according to your environment).
How to automatically obtain IP address
Follow the steps below to configure the computer to obtain an IP address from the DHCP server. Note that you must have a DHCP server.
Click "Automatically obtain IP address".
If you do not want to specify the IP address of the Domain Name System (DNS) server, please click "Automatically obtain DNS server address".
Click OK. In the Local Connection Properties dialog box, click Close.
In the Local Connection Status dialog box, click Close.
Click Start, and then click Run.
In the Open box, type cmd, and then click OK.
At the command prompt, type ipconfig/release, and press ENTER.
Type ipconfig /renew, and press ENTER. The DHCP server will assign an IP address to the network adapter, and you will see a message like the following:
Windows .NET IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix .:
IP Address.. . . . . . . . . . . :192.168.0.201
Subnet Mask .. . . . . . . . . . :255.255.255.0
Default Gateway . . . . . . . . . :192.168.0.1
Type exit, then press ENTER to exit the command prompt.
How to specify an IP address
To assign an IP address to the network adapter, follow the following steps xx:
If you want to assign an IP address to the network adapter, click "Use the IP address below".
In the IP Address box, type the IP address you want to assign to this network adapter. This IP address must be unique in the available address range of your network. Please contact the network administrator to obtain a list of valid IP addresses for your network.
In the Subnet Mask box, type the subnet mask for your network.
In the Default Gateway box, type the IP address of the computer or device in the network that connects your network to another network or the Internet.
In the Preferred DNS Server box, type the IP address of the computer that resolves the hostname to an IP address.
In the "Alternative DNS Server" box, type the IP address of the DNS computer you want to use when the preferred DNS server is unavailable.
Click OK. In the Local Connection Properties dialog box, click Close.
In the Local Connection Status dialog box, click Close.
Troubleshooting
There is a conflict in IP address: If you try to assign an occupied IP address, you will see the following error message:
The static IP address that was just configured is already in use on the reconfigure a different IP address.
Your computer cannot connect to other computers on the network: If the network adapter is assigned an incorrect subnet mask address, the computer will actually be in another network, so you cannot connect to other computers on the network.
Your computer cannot connect to other computers using the hostname: if the incorrect DNS server IP address is assigned, or if the DNS server is not used, the hostname of other computers cannot connect to these computers. This way you will not be able to browse the Internet. You can connect to them using the IP address of other computers.
To work around this problem on the local network, you can use the Host
10. Add LPT port in Windows Server 2003Summary
This article explains how to add additional LPT ports to a Microsoft Windows Server 2003-based computer.
By default, there are 3 LPT available ports in Windows Server 2003, which are LPT1, LPT2, and LPT3. Additional LPT ports can be added until LPT9. After adding an additional LPT port, the port is displayed as an available printer port in the "Add Printer Wizard"
How to add additional LPT ports
Click Start, and then click Run. Warning: Improper use of the Registry Editor can cause serious problems, which may require reinstalling xx as the system. Microsoft does not guarantee that it can resolve problems arising from improper use of the "Registration Editor". Using Registry Editor is at your own risk.
Type regedit in the Open box and click OK.
Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Ports The current LPT port is displayed in the right pane.
On the Edit menu, point to New, and then click String Value.
Type a new value name. To do this, type LPT#, where # is the serial number of the LPT port you want to add, and press ENTER. For example, type LPT4.
On the File menu, click Exit to exit Registry Editor.
Click Start, and then click Run.
Type cmd in the Open box and click OK.
Stop and restart the spool service. To do this, type the following command at the command prompt and press
ENTER key:
net stop spooler
net start spooler
Type exit to exit the command prompt.Copyright