10-05-2012
It should not be that big a deal. You can see all users using niscat passwd and all groups using niscat group, as I recall, and form them into ldap user and group adds. You can process the niscat into command lines in a script using awk or sed or the glabal find and replace of any text editor or word processor. I would be surprised if there were not tools to automate this process, but it should not be a big deal. Probably wise to do groups before the users that depend on them. Then you can remove the nic from the system configuration and the ldap should perform the same function. Make a test ldap-only user and group to ensure ldap is working, and leave a test nis-only user and group to test that nis is turned off. Welcome to UNIX, a stream of text world within a gui world.
8 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi
Does anybody know the steps and requirements of the installation process of Windows Active Directory using Unix/Linux Bind DNS.
I will appreciate if somebody gives the answer. (1 Reply)
Discussion started by: Darwin Rodrigue
1 Replies
2. UNIX for Dummies Questions & Answers
Hello - I have a very vague question, which will probably result in vague answers because I don't have a lot of detailed information and I don't know a whole lot about active directory.
Our Windows/NT admin has been rolling out Active Directory over the past several weeks and as time goes on,... (1 Reply)
Discussion started by: rm -r *
1 Replies
3. UNIX for Dummies Questions & Answers
i would like to ask about unix with active directory..actually my situation is at ny place there already have dns server in unix based,i want to implement an active directory to the network..from what i read about active directory we have to used bind dns...some say that bind could not handle in... (1 Reply)
Discussion started by: nour
1 Replies
4. HP-UX
Hey,
I've asked questions about this project here before and gotten lots of help so I figured I'd give it another try.
I've recently set up my HP-UX environment to authenticate to a Windows Active Directory server (Windows Server 2003 R2).
I setup an account on Active Directory which works... (2 Replies)
Discussion started by: Rike255
2 Replies
5. Red Hat
Hi Friends,
I need your help to get some solution of one of my problem.
Ours is a mixed domain. Most of the servers are windows and very little linux servers. We are using the MS AD for authentication. My problem is, I want to authenticate linux servers against AD. I donot want to use any... (1 Reply)
Discussion started by: arumon
1 Replies
6. UNIX for Advanced & Expert Users
Is there anyone who is utilizing Active Directory (2008R2) for AIX user account management? If yes or if AD is possible with AIX systems, can you please share what to be done to get there?
Please advise. (1 Reply)
Discussion started by: Daniel Gate
1 Replies
7. Solaris
I'd like to share some experiences and what I found for NIS migration from Solaris 8 NIS to Linux platform.
I'm not an expert for both platforms, it's just when I tested both systems and found something really tricky. That might takes a lot of time for you to find the root cause. So, I think I can... (11 Replies)
Discussion started by: bestard
11 Replies
8. UNIX for Beginners Questions & Answers
Hi,
How can we check users added through LDAP or AD. Users added through a group of AD or LDAP group. (2 Replies)
Discussion started by: Nishit
2 Replies
LEARN ABOUT XFREE86
findsmb
FINDSMB(1) User Commands FINDSMB(1)
NAME
findsmb - list info about machines that respond to SMB name queries on a subnet
SYNOPSIS
findsmb [subnet broadcast address]
DESCRIPTION
This perl script is part of the samba(7) suite.
findsmb is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests.
It uses nmblookup(1) and smbclient(1) to obtain this information.
OPTIONS
-r
Controls whether findsmb takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine. This
option is disabled by default because it is specific to Windows 95 and Windows 95 machines only. If set, nmblookup(1) will be called
with -B option.
subnet broadcast address
Without this option, findsmb will probe the subnet of the machine where findsmb(1) is run. This value is passed to nmblookup(1) as part
of the -B option.
EXAMPLES
The output of findsmb lists the following information for all machines that respond to the initial nmblookup for any name: IP address,
NetBIOS name, Workgroup name, operating system, and SMB server version.
There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup. There will be an '*' in
front of the workgroup name for machines that are the domain master browser for that workgroup. Machines that are running Windows for
Workgroups, Windows 95 or Windows 98 will not show any information about the operating system or server version.
The command with -r option must be run on a system without nmbd(8) running. If nmbd is running on the system, you will only get the IP
address and the DNS name of the machine. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root
and with -r option on a machine without nmbd running.
For example, running findsmb without -r option set would yield output similar to the following
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.35.10 MINESET-TEST1 [DMVENGR]
192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6]
192.168.35.56 HERBNT2 [HERB-NT]
192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10]
192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX]
192.168.35.78 HERBDHCP1 +[HERB]
192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
VERSION
This man page is correct for version 3 of the Samba suite.
SEE ALSO
nmbd(8), smbclient(1), and nmblookup(1)
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open
Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to
DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
Samba 3.5 06/18/2010 FINDSMB(1)