ssh help needed

think that I'm missing something obvious here.

After a server reboot a few weeks ago, ssh using cygwin failed to recognize
any users other than the adminstrator. I have tried the following:

- resetting the user passwords from the AD using the command "mkpasswd -d |
grep username > /etc/passwd" followed by "ssh-host-config -y"
- restting all the user passwords with "mkpasswd -l -d > /etc/passwd"
followed by "ssh-host-config -y"
- I've tried restoring all the cygwin files from backup tapes
- uninstalling and reinstalling cygwin
- forcing the CYGWIN sshd service to logon with sshd_server instead of
"system"

At this point in time I can log on as administrator but not as anyone else.
I've been all over the cygwin.com site and googled what seems like every
possible combination of search words for this problem.

How do I set up cygwin to recognize existing users in Active Directory and
their corresponding passwords? Additionally, how do I prevent this from
happening again on my 2003 server?

Thank you in advance.

Ask the people who make your OpenSSH software.
OpenSSH isnt an Microsoft Issue.
You will get bugs from time to time using 3rd party non/ M$ software.

Open ssh is just a port from unix/linux systems to run in windows.
How about trying to just remove the password file and remake them again.


"SBSnewbie" <(E-Mail Removed)> wrote in message
news91710AA-70F4-4EE4-A248-(E-Mail Removed)...
> think that I'm missing something obvious here.
>
> After a server reboot a few weeks ago, ssh using cygwin failed to
> recognize
> any users other than the adminstrator. I have tried the following:
>
> - resetting the user passwords from the AD using the command "mkpasswd -d
> |
> grep username > /etc/passwd" followed by "ssh-host-config -y"
> - restting all the user passwords with "mkpasswd -l -d > /etc/passwd"
> followed by "ssh-host-config -y"
> - I've tried restoring all the cygwin files from backup tapes
> - uninstalling and reinstalling cygwin
> - forcing the CYGWIN sshd service to logon with sshd_server instead of
> "system"
>
> At this point in time I can log on as administrator but not as anyone
> else.
> I've been all over the cygwin.com site and googled what seems like every
> possible combination of search words for this problem.
>
> How do I set up cygwin to recognize existing users in Active Directory and
> their corresponding passwords? Additionally, how do I prevent this from
> happening again on my 2003 server?
>
> Thank you in advance.

Thanks. I did that and am still having problems that point to a permissions
issue. Was just wondering if anyone else had similar problems.

"Backup" wrote:

> Ask the people who make your OpenSSH software.
> OpenSSH isnt an Microsoft Issue.
> You will get bugs from time to time using 3rd party non/ M$ software.
>
> Open ssh is just a port from unix/linux systems to run in windows.
> How about trying to just remove the password file and remake them again.
>
>
> "SBSnewbie" <(E-Mail Removed)> wrote in message
> news91710AA-70F4-4EE4-A248-(E-Mail Removed)...
> > think that I'm missing something obvious here.
> >
> > After a server reboot a few weeks ago, ssh using cygwin failed to
> > recognize
> > any users other than the adminstrator. I have tried the following:
> >
> > - resetting the user passwords from the AD using the command "mkpasswd -d
> > |
> > grep username > /etc/passwd" followed by "ssh-host-config -y"
> > - restting all the user passwords with "mkpasswd -l -d > /etc/passwd"
> > followed by "ssh-host-config -y"
> > - I've tried restoring all the cygwin files from backup tapes
> > - uninstalling and reinstalling cygwin
> > - forcing the CYGWIN sshd service to logon with sshd_server instead of
> > "system"
> >
> > At this point in time I can log on as administrator but not as anyone
> > else.
> > I've been all over the cygwin.com site and googled what seems like every
> > possible combination of search words for this problem.
> >
> > How do I set up cygwin to recognize existing users in Active Directory and
> > their corresponding passwords? Additionally, how do I prevent this from
> > happening again on my 2003 server?
> >
> > Thank you in advance.
>
>
>

Finally got it all running again after tracking it down to a domain file
replication issue and with the help of a small tool from the Server 2003
Resource Kit.

Here’s a synopsis as an FYI. Copied linkd.exe into NWHSERVER system32
folder and then ran from "c:\winnt\sysvol\sysvol\linkd domain.local
c:\winnt\sysvol\domain" Received a cannot create link at domain.local error.
Had to remove the information currently in domain.local as it was manually
copied over at some previous date and would not allow linkd to copy in info
until domain.local was cleared. Copied old files to backup folder on
desktop. Reran linkd command and then copied any policies not already listed
to C:\WINNT\SYSVOL\domain\policies.

Tested with new GPO creation and it immediately popluated both
C:\WINNT\SYSVOL\domain\policies and
C:\WINNT\SYSVOL\sysvol\domain.local\policies on NWHSERVER as expected.
Woohoo!

Reset the sshd_server password and am now back in business.


"SBSnewbie" wrote:

> think that I'm missing something obvious here.
>
> After a server reboot a few weeks ago, ssh using cygwin failed to recognize
> any users other than the adminstrator. I have tried the following:
>
> - resetting the user passwords from the AD using the command "mkpasswd -d |
> grep username > /etc/passwd" followed by "ssh-host-config -y"
> - restting all the user passwords with "mkpasswd -l -d > /etc/passwd"
> followed by "ssh-host-config -y"
> - I've tried restoring all the cygwin files from backup tapes
> - uninstalling and reinstalling cygwin
> - forcing the CYGWIN sshd service to logon with sshd_server instead of
> "system"
>
> At this point in time I can log on as administrator but not as anyone else.
> I've been all over the cygwin.com site and googled what seems like every
> possible combination of search words for this problem.
>
> How do I set up cygwin to recognize existing users in Active Directory and
> their corresponding passwords? Additionally, how do I prevent this from
> happening again on my 2003 server?
>
> Thank you in advance.