Ok, I'm working on a Solaris 8 network using NIS...not NIS+, Just NIS. Recently some of the admins have had a problem with SSHing to one of the servers...this problem has recently spread to my account.

Just now I went as far as completely removing and recreating my useraccount, giving the system more then enough time to propogate the information yet the same problem exist.

The server giving some of us problems is the root master server and is the primary handler of all of our NIS authentications. Also, the affected accounts can still SSH to other workstations and the backup RMS. To add another twist, while a few accounts are affected...there is still one admin who has no problem SSHing to the RMS.

Unfortunatly, I can not post up any code or output of commands or files so I'm just trying to get some suggestions on where to look, something like a big neon sign pointing me in the general direction I need to be looking.

Thanks in advance...

Maybe it has to do with filtering using tcpwrappers . Check the /etc/hosts.allow and /etc/hosts.deny files . Also try disabling the firewalls

Sorry for the delayed responce.

Unfortunatly I do not have the option of disabling the firewall at all...also, the /etc/host.allow/deny files do not exist but then again, the host itself isn't being denied.

Firstly, certain users can SSH from that same terminal without issue.

Second, the accounts that do not work do not work from anywhere.

Third, we are not being denied a connection to the server, we're being told that the login is incorrect.

I've even tried resetting my password directly from that server but no change.

Also, if another user logs onto the server and then does a su - username and I enter my password, it accepts it without issue.

Hi ,
Im just prep 4 my SA2..so forgive if this is inaccurate .

Checkpoint 1 : do a ypmatch username passwd on a server where ur able to get in and 1 in whic ur not able to get in n see if the encrypted shadow password is the same .

Checkpoint 2 : You mentioned that u werent able to get in directly on the server ; do 1 thing...can u recreate ur account directly on the NIS Master...dont let it pull from somewhere..just create it right there and wait for the time interval and the ntry and login...mebbe there is some problem pulling it form the slaves n stuff...

Checkpoint 3 : Do all the ppl who arent able 2 get in on the same homedirectory server ; I mean same partition or something??...mebbe bad sectors on dat part of the disk..or sumthing..

All this sounds sorta primitive but u never know man..lemme know...all the best

Arvind