怎样用LINUX作WINS服务器?

zwdzwdzwd

各位大哥大姐,小弟我是一个LINUX新手有个问题想向大家请教一下: 我是我们单位的网管,我想用LINUX作个WINS服务器(单位已经用WIN 2003 SERVER作了个域控制器了,这里不用LINUX再作域控制器了),但是我不知该怎么配,你们能帮帮我吗,谢谢了!

Yuri

那你直接用那台2003做一个wins不就结了麽?
有必要用Linux麽?
很多人以为Linux比windows安全,其实安全看的是管理员的.
Linux&Windows都是一样的.没什么区别.
设置好了哪个都安全.
还有就是有什么必要用Linux做域控制器?
而且客户机都是windows,直接用windows做域控兼容性是最好的.
除非是服务器不够了,比较紧张只能用Linux那就没办法.
不过我想能用上域控的单位也不缺这一台机器了!

zwdzwdzwd

Post by genv
那你直接用那台2003做一个wins不就结了麽?
有必要用Linux麽?
很多人以为Linux比windows安全,其实安全看的是管理员的.
Linux&Windows都是一样的.没什么区别.
设置好了哪个都安全.
还有就是有什么必要用Linux做域控制器?
而且客户机都是windows,直接用windows做域控兼容性是最好的.
除非是服务器不够了,比较紧张只能用Linux那就没办法.
不过我想能用上域控的单位也不缺这一台机器了!

谢谢你

是服务器不够,但单位又不买新的,没办法呀! 而且我已经用这个LINUX服务器作了个SAMBA服务器(上面放了许多WINDOWS下的备份程序),反正都配了samb.conf,只是再多配几项吗.但是要把它配成WINS我不知道还要配哪几项. 我们单位有好几个子网(WIN 98的),现在没配好都不能互相访问了,就是WINS的问题(路由器绝对没问题),我现大怎么办呀
5555555555555555555

meteoren

域控制器和wins服务可以装在同一台电脑上，而且wins服务占用资源很小，没必要单独用一台电脑

zwdzwdzwd

SAMBA服务器上放了大量的文件,访问量也比较大,如果再作域控制器的话多半拖不起了.现有的问题是:我不用这台LINUX作域控制器(已经用WIN 2003作了一个了),只用它作个WINS服务器,还要配那几项?该怎么配?
谢谢!

meteoren

Post by zwdzwdzwd
SAMBA服务器上放了大量的文件,访问量也比较大,如果再作域控制器的话多半拖不起了.现有的问题是:我不用这台LINUX作域控制器(已经用WIN 2003作了一个了),只用它作个WINS服务器,还要配那几项?该怎么配?
谢谢!

你没明白我的意思，我是说在2003上装wins，几分钟搞定，不是要你把linux装成域控制器  

tdance

版主就是想学怎么在linux下做wins.哪位达人可以教一下就好了.

zwdzwdzwd

上面几位大哥说得很好,其实照你们说的可以节省资源,但是我也想学一下怎样在linux下做wins(已经用WIN 2003 SERVER 作了主域控制器的情况下)

77587758

Post by tdance
版主就是想学怎么在linux下做wins.哪位达人可以教一下就好了.

对哦,很容易看出楼主想学Linux下的Wins,不知道现在的人为什么那么不厚道......
其实我也想学..... :cool:

enthalpy

7.3.3 Setting Up Samba as a WINS Server

You can set up Samba as a WINS server by setting two global options in the configuration file, as shown below:

[global]
        wins support = yes
        name resolve order = wins lmhosts hosts bcast

The wins support option turns Samba into a WINS server. Believe it or not, that's all you need to do! Samba handles the rest of the details behind the scenes, leaving you a relaxed administrator. The wins support=yes and the wins server option are mutually exclusive; you cannot simultaneously offer Samba as the WINS server and point to another system as the server.

If Samba is acting as a WINS server, you should probably get familiar with the name resolve order option mentioned earlier. This option tells Samba the order of methods in which it tries to resolve a NetBIOS name. It can take up to four values:

lmhosts

    Uses a LAN Manager LMHOSTS file
hosts

    Uses the standard name resolution methods of the Unix system, /etc/hosts, DNS, NIS, or a combination (as configured for the system)
wins

    Uses the WINS server
bcast

    Uses a broadcast method

The order in which you specify them in the value is the order in which Samba will attempt name resolution when acting as a WINS server. For example, let's look at the value specified previously:

name resolve order = wins lmhosts hosts bcast

This means that Samba will attempt to use its WINS entries first for name resolution, followed by the LAN Manager LMHOSTS file on its system. Next, the hosts value causes it to use Unix name resolution methods. The word hosts may be misleading; it covers not only the /etc/hosts file, but also the use of DNS or NIS (as configured on the Unix host). Finally, if those three do not work, it will use a broadcast to try to locate the correct machine.

Finally, you can instruct a Samba server that is acting as a WINS server to check with the system's DNS server if a requested host cannot be found in its WINS database. With a typical Linux system, for example, you can find the IP address of the DNS server by searching the /etc/resolv.conf file. In it, you might see an entry such as the following:

nameserver 127.0.0.1
nameserver 192.168.200.192

This tells us that a DNS server is located at 192.168.220.192. (The 127.0.0.1 is the localhost address and is never a valid DNS server address.)

Use the global dns proxy option to alert Samba to use the configured DNS server:

[global]
        wins support = yes
        name resolve order = wins lmhosts hosts bcast
        dns proxy = yes


http://www.oreilly.com/catalog/samba/chapter/book/ch07_03.html