Scenario: (See attached file for screen shots and log info)
On the Windows side of the house, if we enter into the Management console for Unix, we can see that the service is started, the Master and Slave have been defined, encryption has been set, Use windows for NIS is check marked. (The port number has been changed on purpose; but the reflection was made on the other server correctly.)

So I know I'm getting information from the NIS. but it's not relfected in my passwd file and I cannot log in. I assume that is due to the password not being sync'd. And I cannot change the password for a user on the Redhat side.
[root@amf-asic1 ~]# yppasswd timmy
Changing NIS account information for timmy on amf-dc1.
Please enter root password:
Changing NIS password for timmy on amf-dc1.
Please enter new password:
Please retype new password:
Error while changing the NIS password.
The NIS password has not been changed on amf-dc1.

WINDBIND is.. technically.. a right answer; but there is a reason that I need NIS. The server will be placed into a a live/existing network, and the stupid(PREVIOUS) IT department before me made the current setup quite combersome. Everything is networked together via UID/GIDs. I need to keep a handfull of the UIDs and GIDs; Windows Server 2003, R2 will allow you to perform a NIS like function and intergrate a Unix NIS with Active directory. We are trying to do manny things at once and felt this it would be the "simplest" (GOD WERE We WRONG) way. There is very little documentation from Microsoft and even fewer white papers on the internet.

In the end, we have installed WINBIND and are currently working on a long drawn out method to fix everything as quickly as possible. More or less it boiled down to, "just make it right and follow the industry standard."

Featured Post

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…

After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…