2010年01月06日

这主要是由于盗版的xp系统造成的(如克隆版)。大家可以注意到出现这个问题时,单击桌面的“我的文档”图标是不能正确链接的。解决步骤:
1.右击“我的文档”图标,点击“属性”,对目标文件夹位置“还原默认值”;
2.打开注册表,将“HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders”下的键值Personal改为“My Documents”文件夹的实际路径,如:C:\Documents and Settings\Administrator\My Documents 将键值Favorites改为收藏夹的实际路径,如:C:\Documents and Settings\Administrator\Favorites 即可
 
 
 

2008年05月27日

http://www.apple.com.cn/support/ipod/five_rs/

iPod Five Rs Assistant

iPod 有问题吗?请按照下面的顺序进行操作。逐一完成每项操作直至问题得到解决。

 

 

2006年06月28日

word保存时提示“文档被保存,但是语音识别的数据丢失,因为没有足够的空间存储这些数据。确保没有录音时关闭麦克风,并检查磁盘上的可用存储空间”
怎么回事,哪来的语音数据??我又没录音
 
解决方法:点击Word当中的工具->选项->保存->将嵌入语言数据选框的对话去掉

2006年06月16日

启动远程桌面连接的方法

微软操作系统发展至今只有以下三个操作系统可以使用远程桌面功能,他们是WINDOWS 2000SERVER,WINDOWS XP和WINDOWS 2003。

1)WINDOWS 2000SERVER

WINDOWS2000系统中PROFESSIONAL版本是不能开启远程桌面功能让别人访问的,但SERVER版可以开启,不过需要我们安装相应的WINDOWS组件。方法如下:

第一步:通过任务栏的“开始->设置->控制面板”,选择里头的“添加/删除程序”。

第二步:在左边选择“添加/删除WINDOWS组件”。

第三步:稍后会出现添加删除WINDOWS组件窗口,我们从中选择“终端服务”,然后点“下一步”进行安装。(如图1)这里要注意一点的是在安装过程中需要我们插入WINDOWS 2000SERVER系统光盘到光驱中。

第四步:安装完毕后需要重新启动计算机,重启后就完成了在WINDOWS 2000SERVER下的远程桌面连接功能的安装工作。


图1



(2)WINDOWS XP

正如上文提到的,WINDOWS2000引入远程桌面连接功能后受到了广大用户的好评,大家普遍认为开启该功能的方法太复杂,而且在使用时不能保证每个人都拥有WINDOWS2000SERVER光盘。因此在XP和2003系统中微软将远程桌面开启的操作进行了简化。

第一步:在桌面“我的电脑”上点鼠标右键,选择“属性”。

第二步:在弹出的系统属性窗口中选择“远程”标签。

第三步:在远程标签中找到“远程桌面”,在“容许用户连接到这台计算机”前打上对勾后确定即可完成XP下远程桌面连接功能的启用。(如图2)


图2



(3)WINDOWS 2003

WINDOWS2003开启方法和XP类似,同样对操作步骤进行了简化。方法如下:

第一步:在桌面“我的电脑”上点鼠标右键,选择“属性”。

第二步:在弹出的系统属性窗口中选择“远程”标签。

第三步:在远程标签中找到“远程桌面”,在“容许用户连接到这台计算机”前打上对勾后确定即可完成2003下远程桌面连接功能的启用。(如图3)


图3

4、使用远程桌面连接的方法

使用远程桌面连接的方法很简单,因为一旦连接到服务器上就和操作本地计算机一样了。所以唯一要讲解的就是连接操作。如何连接到开启了远程桌面功能的计算机呢?我们需要远程桌面连接登录器。

(1)WINDOWS XP和2003操作系统:

这两个系统将远程桌面连接程序内置到附件中,我们不用安装任何程序就可以使用远程桌面连接。

第一步:通过任务栏的“开始->程序->附件->通讯->远程桌面连接”来启动登录程序。(如图4)

第二步:在图4界面中的“计算机”处输入开启了远程桌面功能的计算机IP地址。

第三步:点击“连接”按钮后我们就可以成功登录到该计算机上了,连接上去后如图5所示,和操作自己计算机一样方便一样快捷。

图4

(2)其他WINDOWS操作系统:

2000及以前的WINDOWS中系统没有将登录工具放到附件中,我们有两个方法获得登录器并实现远程桌面的连接功能。

方法一:使用XP光盘登录器——MSRDPCLI

在XP系统光盘盘符下\SUPPORT\TOOLS目录有一个叫做MSRDPCLI.exe的程序,该程序实际上是一个远程桌面连接登录器,在WIN98/2000机器上运行XP光盘目录下的msrdpcli.exe。将自动安装远程桌面连接程序。安装过程非常简单,一路“下一步”即可。完毕以后通过“开始->程序->附件->通讯->远程桌面连接”就可以登录网络上开启远程桌面功能的计算机了。

方法二:第三方登录器

实际上网络中有很多站点都提供了远程桌面登录器的下载,我们在98系统或2000系统上下载该登录器就可以完成登录远程桌面的功能。

2005年08月03日

http://www.petri.co.il/configure_outlook_2003_to_use_rpc_over_http.htm

RPC over HTTP/S is a cool method for connecting your Outlook 2003 client to the corporate Exchange Server 2003 from the Internet or WAN, without the need to establish a VPN session to the corporate LAN and/or needing to open many ports on your corporate firewall. The only ports you’ll need to open on your firewall are TCP 80 and, if using SSL, TCP 443.

The process of setting up the RPC over HTTP/S connection is outlined in the Setting up RPC over HTTP/S on a Single Server article.

After configuring RPC over HTTP/S you’ll need to configure your Outlook 2003 client to use the RPC over HTTP/S connection method instead of the regular TCP/IP method.

To set up a new Outlook profile that uses RPC over HTTP/S:

  1. Open Control Panel and run the Mail applet.

  2. In the Mail applet click on Show Profiles.


    In the Mail window click on Add.

    In the New Profile window type a descriptive name and click Ok.

    In the E-Mail Accounts window select Add a new e-mail account and click Next.

    In the E-Mail Accounts window, select Microsoft Exchange Server and click Next.

    1. In the E-Mail Accounts window, under the Microsoft Exchange Server box, type the NetBIOS name (see table) of the Exchange server. Next, in the User Name box type the logon name of the test user account, the one you’ll be connecting with. Although pressing the Check Name button will probably work in the LAN environment, it will NOT work on the WAN, so basically there is no point in pressing it. Next click More Settings.

    Note: In this test scenario I recommend NOT to use Cached Mode. We’re working on the LAN, our network connection is steady and fast, and this is only a test account. However, in WAN scenarios where a user needs to connect to his or her mailbox from their portable computer – you should use Cached Mode.

    1. In the Microsoft Exchange Server window, go to the Connection tab. Notice that you should have a section called "Exchange over the Internet" at the bottom of the tab. If this section does not appear, it means that you might not have met the requirements for setting up an RPC over HTTP/S connection. See the "Client Requirements" section on the Configure RPC over HTTP/S on a Single Server page.

    In the Exchange over the Internet section click to select the Connect to my Exchange mailbox using HTTP, and then click on the Exchange Proxy Settings button.

    1. In the Exchange Proxy Settings tab in the Connection Settings box, type the FQDN (Fully Qualified Domain Name) of the Exchange server.

    Note: For LAN testing you can type the internal FQDN of the server. For WAN connections you MUST type the external FQDN of the server. See Testing RPC over HTTP/S Connection for more on this issue. The external FQDN of the server is the fully qualified domain name that is used by the Outlook clients to connect to the server from outside the LAN, and must be resolved to the IP address of the server, or in most cases, resolved to the IP address of your Firewall (or NAT device) that is configured to transfer the requests to the internal IP address of the Exchange 2003 server.

    Note for scenarios where the Exchange 2003 server is NOT the RPC Proxy: In cases where the RPC Proxy is installed on a different server, the FQDN typed in this box should be of the RPC Proxy server, and NOT of the Exchange server!

    If you want, click to select the checkbox near "On fast networks…", and keep the selected checkbox near the "On slow networks…" settings.

    In most scenarios you’ll need to select the Basic Authentication setting in the Proxy Authentication settings drop-down list. If you do, notice that you MUST use an SSL-based connection, and you will have to configure a Digital Certificate for your Default Website. Read Configure SSL on Your Website with IIS for more on this issue.

    Very important note regarding SSL: When using SSL (and I recommend you do), you must issue a Digital Certificate to your Exchange server. A Digital Certificate needs to be obtained from a CA (Certification Authority). Windows 2000/2003 has a built-in CA that can be installed and used, however, when issuing a Digital Certificate from your internal CA you MUST be 100% sure that the client computers that are going to connect to the server are properly configured to trust this CA. Most operating systems are pre-configured to trust known 3rd-party CAs such as Verisign, Thawte and others. However unless these computers are made members of the Active Directory domain where you’ve installed your CA, they will NOT automatically trust your CA, and thus your connection will fail! In such scenarios you must import the ROOT CA Digital Certificate into the client computers in order to make them trust your CA. When using 3rd-party trusted CAs in most cases you won’t be required to import anything to the client computers, however you will be required to pay a few hundred dollars for such a Digital Certificate.

    When done, click Ok.

    1. Back in the Microsoft Exchange Server window click Ok.

    1. Back in the E-Mail Accounts window click Next.

    1. Back in the Mail window, click to select Prompt for a profile to be used (unless you only have one profile, duh…), then click Ok.

    Now, let’s open Outlook and try to connect to the server. See Testing RPC over HTTP/S Connection for more details.


    1. In the E-Mail Accounts window, under the Microsoft Exchange Server box, type the NetBIOS name (see table) of the Exchange server. Next, in the User Name box type the logon name of the test user account, the one you’ll be connecting with. Although pressing the Check Name button will probably work in the LAN environment, it will NOT work on the WAN, so basically there is no point in pressing it. Next click More Settings.

    Note: In this test scenario I recommend NOT to use Cached Mode. We’re working on the LAN, our network connection is steady and fast, and this is only a test account. However, in WAN scenarios where a user needs to connect to his or her mailbox from their portable computer – you should use Cached Mode.

    1. In the Microsoft Exchange Server window, go to the Connection tab. Notice that you should have a section called "Exchange over the Internet" at the bottom of the tab. If this section does not appear, it means that you might not have met the requirements for setting up an RPC over HTTP/S connection. See the "Client Requirements" section on the Configure RPC over HTTP/S on a Single Server page.

    In the Exchange over the Internet section click to select the Connect to my Exchange mailbox using HTTP, and then click on the Exchange Proxy Settings button.

    1. In the Exchange Proxy Settings tab in the Connection Settings box, type the FQDN (Fully Qualified Domain Name) of the Exchange server.

    Note: For LAN testing you can type the internal FQDN of the server. For WAN connections you MUST type the external FQDN of the server. See Testing RPC over HTTP/S Connection for more on this issue. The external FQDN of the server is the fully qualified domain name that is used by the Outlook clients to connect to the server from outside the LAN, and must be resolved to the IP address of the server, or in most cases, resolved to the IP address of your Firewall (or NAT device) that is configured to transfer the requests to the internal IP address of the Exchange 2003 server.

    Note for scenarios where the Exchange 2003 server is NOT the RPC Proxy: In cases where the RPC Proxy is installed on a different server, the FQDN typed in this box should be of the RPC Proxy server, and NOT of the Exchange server!

    If you want, click to select the checkbox near "On fast networks…", and keep the selected checkbox near the "On slow networks…" settings.

    In most scenarios you’ll need to select the Basic Authentication setting in the Proxy Authentication settings drop-down list. If you do, notice that you MUST use an SSL-based connection, and you will have to configure a Digital Certificate for your Default Website. Read Configure SSL on Your Website with IIS for more on this issue.

    Very important note regarding SSL: When using SSL (and I recommend you do), you must issue a Digital Certificate to your Exchange server. A Digital Certificate needs to be obtained from a CA (Certification Authority). Windows 2000/2003 has a built-in CA that can be installed and used, however, when issuing a Digital Certificate from your internal CA you MUST be 100% sure that the client computers that are going to connect to the server are properly configured to trust this CA. Most operating systems are pre-configured to trust known 3rd-party CAs such as Verisign, Thawte and others. However unless these computers are made members of the Active Directory domain where you’ve installed your CA, they will NOT automatically trust your CA, and thus your connection will fail! In such scenarios you must import the ROOT CA Digital Certificate into the client computers in order to make them trust your CA. When using 3rd-party trusted CAs in most cases you won’t be required to import anything to the client computers, however you will be required to pay a few hundred dollars for such a Digital Certificate.

    When done, click Ok.

    1. Back in the Microsoft Exchange Server window click Ok.

    1. Back in the E-Mail Accounts window click Next.

    1. Back in the Mail window, click to select Prompt for a profile to be used (unless you only have one profile, duh…), then click Ok.

    Now, let’s open Outlook and try to connect to the server. See Testing RPC over HTTP/S Connection for more details.


Exchange Server 2003 Deployment Guide
http://www.microsoft.com/downloads/details.aspx?familyid=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en

Installing New Exchange 2003 Servers

This topic provides information about deploying new installations of Microsoft® Exchange Server 2003 in your organization. Specifically, this topic will:

Provide you with the requirements necessary to install Exchange 2003.

Provide you with information about running Exchange Server 2003 Deployment Tools.

Provide you with information about front-end and back-end architecture, including how to configure a front-end server.

Show you how to run ForestPrep.

Show you how to run DomainPrep.

Show you how to install Exchange 2003 on new servers, including how to run Exchange 2003 Setup in attended and unattended modes.

 more detail see the link http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/a3318f57-3536-4e65-9309-9300cda23c73.mspx
How to Install Microsoft Exchange on a Server in a Root Domain
http://support.microsoft.com/?kbid=236145

原文地址:http://www.unix.org.ua/orelly/networking/tcpip/ch03_02.htm

The host table is a simple text file that associates IP addresses with hostnames. On most UNIX systems, the table is in the file /etc/hosts. Each table entry in /etc/hosts contains an IP address separated by whitespace from a list of hostnames associated with that address. Comments begin with #.

The host table on peanut might contain the following entries:

#
# Table of IP addresses and hostnames
#
172.16.12.2     peanut.nuts.com peanut
127.0.0.1       localhost
172.16.12.1     almond.nuts.com almond loghost
172.16.12.4     walnut.nuts.com walnut
172.16.12.3     pecan.nuts.com pecan
172.16.1.2      filbert.nuts.com filbert
172.16.6.4      salt.plant.nuts.com salt.plant salt

The first entry in the sample table is for peanut itself. The IP address 172.16.12.2 is associated with the hostname peanut.nuts.com and the alternate hostname (or alias) peanut. The hostname and all of its aliases resolve to the same IP address, in this case 172.16.12.2.

Aliases provide for name changes, alternate spellings, and shorter hostnames. They also allow for "generic hostnames." Look at the entry for 172.16.12.1. One of the aliases associated with that address is loghost. loghost is a special hostname used by the syslog daemon, syslogd. Programs like syslogd are designed to direct their output to the host that has a certain generic name. You can direct the output to any host you choose by assigning it the appropriate generic name as an alias. Other commonly used generic host names are lprhost, mailhost, and dumphost.

The second entry in the sample file assigns the address 127.0.0.1 to the hostname localhost. As we have discussed, the class A network address 127 is reserved for the loopback network. The host address 127.0.0.1 is a special address used to designate the loopback address of the local host - hence the hostname localhost. This special addressing convention allows the host to address itself the same way it addresses a remote host. The loopback address simplifies software by allowing common code to be used for communicating with local or remote processes. This addressing convention also reduces network traffic because the localhost address is associated with a loopback device that loops data back to the host before it is written out to the network.

Although the host table system has been superseded by DNS, it is still widely used for the following reasons:

  • Most systems have a small host table containing name and address information about the important hosts on the local network. This small table is used when DNS is not running, such as during the initial system startup. Even if you use DNS, you should create a small /etc/hosts file containing entries for your host, for localhost, and for the gateways and servers on your local net.

  • Sites that use NIS use the host table as input to the NIS host database. You can use NIS in conjunction with DNS; but even when they are used together, most NIS sites create host tables that have an entry for every host on the local network. Chapter 9, Configuring Network Servers , explains how to use NIS with DNS.

  • Very small sites that are not connected to the Internet sometimes use the host table. If there are few local hosts and the information about these hosts rarely changes, and there is no need to communicate via TCP/IP with remote sites, then there is little advantage to using DNS.

The old host table system is inadequate for the global Internet for two reasons: inability to scale and lack of an automated update process. Prior to adopting DNS, the Network Information Center (NIC) maintained a large table of Internet hosts called the NIC host table. Hosts included in the table were called registered hosts, and the NIC placed hostnames and addresses into this file for all sites on the Internet.

Even when the host table was the primary means for translating hostnames to IP addresses, most sites registered only a limited number of key systems. But even with limited registration, the table grew so large that it became an inefficient way to convert host names to IP addresses. There is no way that a simple table could provide adequate service for the enormous number of hosts in today’s Internet.

Another problem with the host table system is that it lacks a technique for automatically distributing information about newly registered hosts. Newly registered hosts can be referenced by name as soon as a site receives the new version of the host table. However, there is no way to guarantee that the host table is distributed to a site. The NIC didn’t know who had a current version of the table, and who did not. This lack of guaranteed uniform distribution is a major weakness of the host table system.

Some versions of UNIX provide the command htable to automatically build /etc/hosts and /etc/networks from the NIC host table. htable and the NIC host table are no longer used to build the /etc/hosts file. However, the command is still useful for building /etc/networks. The /etc/networks file is still used to map network addresses to network names because many network names are not included in the DNS database. To create the /etc/networks file, download the file ftp://rs.internic.net/netinfo/networks.txt into a local work directory. Run htable networks.txt. Discard the hosts file and the gateways file produced by htable, and move the networks file to the /etc directory.

This is the last we’ll speak of the NIC host table: it has been superseded by DNS. All hosts connected to the Internet should use DNS.

原文地址:http://www.grape-info.com/doc/win2000srv/network/dhcp/
http://www.grape-info.com/doc/index.html也是一个有很多技术资料的网站
主要是以下这几个方面:

Contents

  1. Windows 2000 Server
  2. Redhat Linux Practice Note
  3. Symantec’s Norton Antivirus Corporate Edition (Ver 7.5) Administrator’s Guide
  4. CISCO Router Configuration
  5. CISCO Switch Catalyst 2900 XL Manual
  6. Eclipse Manual
  7. HTML/CSS/ASP Manual
    DHCP Server

Dynamic Host Configuration Protocol (DHCP) is a TCP/IP standard designed to reduce the complexity of administering address configurations by using a server computer to centrally manage IP addresses and other related configuration details used on your network. Windows 2000 Server provides the DHCP service, which enables the server computer to perform as a DHCP server and configure DHCP-enabled client computers on your network as described in the current DHCP draft standard, RFC 2131.


Sample Network

Server Name hoge-server
Network Address 192.168.0.0
Subnet Mask 255.255.255.0
Server IP Address 192.168.0.1
Default Gateway 192.168.0.1
DNS Server 192.168.0.1
DHCP Server 192.168.0.1
WINS Server 192.168.0.1

Install DHCP Server

  1. Open [Windows Components Wizard], select [Network Services] and click [Details...]

  2. Select [Dynamic Host Configuration Protocol (DHCP)] and click [OK]

Configure DHCP Server

  1. Open [DHCP] window from [Start], [Programs], [Administrative Tools] and [DHCP]. To add new scope, click [Action] and [New Scope]

  2. Click [Next]

  3. Type Scope Name and click [Next]

  4. Type IP Address Range and click [Next]

  5. Click [Next]

  6. Click [Next]

  7. Click [Next]

  8. Type Default Gateway IP Address and click [Next]

  9. Type [Parent domain] name and DNS server IP Address and click [Next]

  10. Type WINS server IP Address and click [Next]

  11. Click [Next]

  12. Click [Finish]

  13. After finishing installing Active Directory, authorize the DHCP Server

  14. Close DHCP window

Two DHCP Servers

We need to consider that if there is only one DHCP server and it’s down, clients can not get IP address. It’s better to have two DHCP server as below,


\ Server1 (DHCP,DNS,WINS) Server2 (DHCP,DNS,WINS)
Server IP Address 192.168.0.1 192.168.0.2
IP Address Range 192.168.0.100 – 192.168.0.200 192.168.0.100 – 192.168.0.200
IP Address Exclution 192.168.0.151 – 192.168.0.200 192.168.0.100 – 192.168.0.150
Scope Options
DNS 192.168.0.1, 192.168.0.2 192.168.0.2, 192.168.0.1
WINS 192.168.0.1, 192.168.0.2 192.168.0.2, 192.168.0.1

Or if you have two scope

Two Servers
Two scopes (DHCP 80/20 Rule)
DHCP Server Range Exclution
DHCP1 192.168.10.10 – 192.168.10.254 192.168.10.200 – 192.168.10.254
192.168.20.10 – 192.168.20.254 192.168.20.10 – 192.168.20.200
DHCP2 192.168.10.10 – 192.168.10.254 192.168.10.10 – 192.168.10.200
192.168.20.10 – 192.168.20.254 192.168.20.200 – 192.168.20.254

Testing at Client

  1. Release and renew the current DHCP configuration uging ipconfig /renease and ipconfig /renew
    C:\> ipconfig /release
    Ethernet adapter Local Area Connection:
            Connection-specific DNS Suffix  . :
            IP Address. . . . . . . . . . . . : 0.0.0.0
            Subnet Mask . . . . . . . . . . . : 0.0.0.0
            Default Gateway . . . . . . . . . :
    C:\> ipconfig /renew
    Ethernet adapter Local Area Connection:
            Connection-specific DNS Suffix  . : grape-info.com
            IP Address. . . . . . . . . . . . : 192.168.0.101
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.0.2
    

    Note: Practically I have noticed that some computer does not get the new configuration. In such a case, restart the computer.

  2. Display full configuration information uging ipconfig /all
    C:\> ipconfig /all
    Ethernet adapter Local Area Connection:
            Connection-specific DNS Suffix  . : grape-info.com
            Description . . . . . . . . . . . : Hoge hoge LAN Card
            Physical Address. . . . . . . . . : 00-02-2D-4F-57-3B
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.0.101
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.0.1
            DHCP Server . . . . . . . . . . . : 192.168.0.1
            DNS Servers . . . . . . . . . . . : 192.168.0.1
                                                192.168.0.2
            Primary WINS Server . . . . . . . : 192.168.0.1
            Secondary WINS Server . . . . . . : 192.168.0.2
            Lease Obtained. . . . . . . . . . : 12 June 2002 12:34:22
            Lease Expires . . . . . . . . . . : 20 June 2002 13:35:22
    

BackSupport

Short for Windows Internet Naming Service, a system that determines the IP address associated with a particular network computer. This is called name resolution. WINS supports network client and server computers running Windows and can provide name resolution for other computers with special arrangements. Determining the IP address for a computer is a complex process when DHCP servers assign IP addresses dynamically. For example, it is possible for DHCP to assign a different IP address to a client each time the machine logs on to the network.

WINS uses a distributed database that is automatically updated with the names of computers currently available and the IP address assigned to each one.

DNS is an alternative system for name resolution suitable for network computers with fixed IP addresses

mirosoft网站上面的介绍:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/babc5a09-0561-44a5-884c-d2dfaa5b1019.mspx
在microsoft的这个网页上面你也可以找到所有关于dns,wins,dhcp的安装,配置,问题解决的文档

WINS

Windows Internet Name Service (WINS) provides a dynamic replicated database service that can register and resolve NetBIOS names to IP addresses used on your network. The Microsoft® Windows Server 2003 family provides WINS, which enables the server computer to act as a NetBIOS name server and register and resolve names for WINS-enabled client computers on your network as described in the NetBIOS over TCP/IP standards.

Before you begin using this computer as a WINS server, see Checklist: Installing a WINS server.

To find features that have been moved in the Windows Server 2003 family, see New ways to do WINS tasks.

For tips about using WINS, see WINS Best Practices.

For help with specific tasks, see WINS How To….

For general background information, see WINS Concepts.

For problem-solving instructions, see WINS Troubleshooting.

Configure WINS for DHCP-enabled clients

Updated: January 21, 2005

* *
* *

To configure WINS for DHCP-enabled clients

Clients running Windows 2000, Windows XP, or the Windows Server 2003 family are configured by default to use a DHCP server to obtain an IP address. No further client-side configuration is needed.

Instead, configure your DHCP server to assign WINS-related options needed to enable DHCP-enabled clients on your network to use WINS. For more information, see Related Topics.

Note

In most cases, WINS clients only need to be provided the following NetBIOS over TCP/IP (NetBT) option types for basic WINS configuration: 44 (WINS servers) and 46 (WINS node type). These options must be configured at the DHCP server providing each client its dynamically leased IP address.


Information about functional differences

Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

DNS:
(Domain Name Service)是寻找Internet域名并将它转化为IP地址的系统。域名是有意义的,容易记忆的Internet 地址。

(1) Short for Domain Name System (or Service or Server), an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they’re easier to remember. The Internet however, is really based on IP addresses. Every time you use a domain name, therefore, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.example.com might translate to 198.105.232.4.

The DNS system is, in fact, its own network. If one DNS server doesn’t know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.

原文地址:http://www.webopedia.com/TERM/D/DNS.html

这个网站有很多关于技术方面专业名词的技术,值得一看。下面是这个网站对自己的定位i:)

Webopedia.com

How can I configure DNS forwarding for Internet connection?

If you want you DNS server to be integrated into a larger DNS environment such as the Internet, you will need to configure forwarding on your server.

To configure DNS forwarding:

  1. Click Start, point to Programs, point to Administrative Tools, and then click DNS to start the DNS Management Console.

  2. Right click the DNS Server object for your server in the left pane of the console, and click Properties.

  1. Click the Forwarders tab.

  2. Check the Enable forwarders check-box.

  3. In the IP address box enter the IP address of the DNS servers you want to forward queries to – typically the DNS server of your ISP. You can also move them up or down. The one that is highest in the list gets the first try, and if it does not respond within a given time limit – the query will be forwarded to the next server in the list.

  1. Click OK.

If you cannot configure forwarding because the forwarding tab is grayed out, read No Forwarding or Root Hints on DNS server?

 

Why are the options to configure Root Hints or Forwarders unavailable?

If no DNS servers were detected during the initial configuration of Windows 2000 DNS, the system will typically designate the new DNS server as a "root server", which is the ultimate authority for all naming resolution activities. As a result, the new DNS server will not be able to forward any name resolution queries that it is unable to resolve to another server or to the root servers on the Internet. Consequently, a Windows 2000 DNS server that has been configured as a root server disables the options to add forwarders automatically.


Also, the Root Hints tab will be empty.

If, at a later date, you decide that this DNS server should be integrated into a larger DNS environment such as the Internet, you will need to remove the "root" forward lookup zone.

To remove the root forward lookup zone:

  1. Click Start, point to Programs, point to Administrative Tools, and then click DNS to start the DNS Management Console.

  2. Click the DNS Server object for your server in the left pane of the console, and click the (+) PLUS sign next to the server object to expand the tree.

  3. Click the (+) PLUS sign next to Forward Lookup Zones to expand it.

  4. Click the zone that is marked with a (.) period, and then press DELETE.

  5. Click OK to confirm that you want to delete the zone.

  6. Close the DNS Management Console and re-open it. Now the options to configure Root Hints or Forwarders are available.
    After deleting the root zone you can now read Configure DNS Forwarding

The DNS system is, in fact, its own network. If one DNS server doesn’t know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.

原文地址:http://www.webopedia.com/TERM/D/DNS.html

这个网站有很多关于技术方面专业名词的技术,值得一看。下面是这个网站对自己的定位i:)

Webopedia.com

How can I configure DNS forwarding for Internet connection?

If you want you DNS server to be integrated into a larger DNS environment such as the Internet, you will need to configure forwarding on your server.

To configure DNS forwarding:

  1. Click Start, point to Programs, point to Administrative Tools, and then click DNS to start the DNS Management Console.

  2. Right click the DNS Server object for your server in the left pane of the console, and click Properties.

  1. Click the Forwarders tab.

  2. Check the Enable forwarders check-box.

  3. In the IP address box enter the IP address of the DNS servers you want to forward queries to – typically the DNS server of your ISP. You can also move them up or down. The one that is highest in the list gets the first try, and if it does not respond within a given time limit – the query will be forwarded to the next server in the list.

  1. Click OK.

If you cannot configure forwarding because the forwarding tab is grayed out, read No Forwarding or Root Hints on DNS server?

 

Why are the options to configure Root Hints or Forwarders unavailable?

If no DNS servers were detected during the initial configuration of Windows 2000 DNS, the system will typically designate the new DNS server as a "root server", which is the ultimate authority for all naming resolution activities. As a result, the new DNS server will not be able to forward any name resolution queries that it is unable to resolve to another server or to the root servers on the Internet. Consequently, a Windows 2000 DNS server that has been configured as a root server disables the options to add forwarders automatically.


Also, the Root Hints tab will be empty.

If, at a later date, you decide that this DNS server should be integrated into a larger DNS environment such as the Internet, you will need to remove the "root" forward lookup zone.

To remove the root forward lookup zone:

  1. Click Start, point to Programs, point to Administrative Tools, and then click DNS to start the DNS Management Console.

  2. Click the DNS Server object for your server in the left pane of the console, and click the (+) PLUS sign next to the server object to expand the tree.

  3. Click the (+) PLUS sign next to Forward Lookup Zones to expand it.

  4. Click the zone that is marked with a (.) period, and then press DELETE.

  5. Click OK to confirm that you want to delete the zone.

  6. Close the DNS Management Console and re-open it. Now the options to configure Root Hints or Forwarders are available.
    After deleting the root zone you can now read Configure DNS Forwarding

The DNS system is, in fact, its own network. If one DNS server doesn’t know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.

原文地址:http://www.webopedia.com/TERM/D/DNS.html

这个网站有很多关于技术方面专业名词的技术,值得一看。下面是这个网站对自己的定位i:)

Webopedia.com

How can I configure DNS forwarding for Internet connection?

If you want you DNS server to be integrated into a larger DNS environment such as the Internet, you will need to configure forwarding on your server.

To configure DNS forwarding:

  1. Click Start, point to Programs, point to Administrative Tools, and then click DNS to start the DNS Management Console.

  2. Right click the DNS Server object for your server in the left pane of the console, and click Properties.

  1. Click the Forwarders tab.

  2. Check the Enable forwarders check-box.

  3. In the IP address box enter the IP address of the DNS servers you want to forward queries to – typically the DNS server of your ISP. You can also move them up or down. The one that is highest in the list gets the first try, and if it does not respond within a given time limit – the query will be forwarded to the next server in the list.

  1. Click OK.

If you cannot configure forwarding because the forwarding tab is grayed out, read No Forwarding or Root Hints on DNS server?

 

Why are the options to configure Root Hints or Forwarders unavailable?

If no DNS servers were detected during the initial configuration of Windows 2000 DNS, the system will typically designate the new DNS server as a "root server", which is the ultimate authority for all naming resolution activities. As a result, the new DNS server will not be able to forward any name resolution queries that it is unable to resolve to another server or to the root servers on the Internet. Consequently, a Windows 2000 DNS server that has been configured as a root server disables the options to add forwarders automatically.


Also, the Root Hints tab will be empty.

If, at a later date, you decide that this DNS server should be integrated into a larger DNS environment such as the Internet, you will need to remove the "root" forward lookup zone.

To remove the root forward lookup zone:

  1. Click Start, point to Programs, point to Administrative Tools, and then click DNS to start the DNS Management Console.

  2. Click the DNS Server object for your server in the left pane of the console, and click the (+) PLUS sign next to the server object to expand the tree.

  3. Click the (+) PLUS sign next to Forward Lookup Zones to expand it.

  4. Click the zone that is marked with a (.) period, and then press DELETE.

  5. Click OK to confirm that you want to delete the zone.

  6. Close the DNS Management Console and re-open it. Now the options to configure Root Hints or Forwarders are available.
    After deleting the root zone you can now read Configure DNS Forwarding

HOW TO: Configure DNS Records for Your Web Site in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;315982&sd=tech#XSLTH3148121122120121120120