t-w1064-ix-013 is not accessible via VNC nor SSH (I think the latter is valid for all Win 10 machines). Ping works though. We're dealing with some backlog on Win 10, so we're trying to get working as many such boxes as possible.
checked the host and it looked fine. rebooted and it came back to log in screen. let me know if issues still persist and we can try a reimage.
Assignee: server-ops-dcops → vle
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
I'm still unable to connect to this machine by any means. It was sitting disabled for many days, so I already did a reimage yesterday to make sure it's clean before enabling it back in production. However, I can't access it at all. There was another disabled Win 10 machine (t-w1064-ix-002) besides this one, so I also did a reimage and enabled it in production. Things went smoothly and I was able to vnc to that machine without any issues. So I think this one has other issues. Maybe we missed something when converting these machines from Win 8 to Win 10? (bug 1367102).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
yah, looks like something on the backend. host is fine from my stand point.
Yeah there is something odd here. IPMI can connect, but the KVM console has no signal. Van: Can you log on and see what the machine thinks its name is? And could try to reinstall it from there?
which file has the root password? is it one of the aspect-*-security.txt.gpg files? ive those passwords and none worked for me. i don't have an account on the box myself.
It is in the releng file aspect-low-security.txt.gpg.
not accepting either one of the 2 passwords in that file. ive tried multiple times. perhaps it's picking up the wrong image? ive tried both user root and Administrator without success. is there another account besides root that can log into these machines? if so, can you point me to the gpg file with the pw as well?
any ideas? fwiw, the aspect-low passwords didn't work on the minis either.
Tried connecting to this machine using several methods, yet failed each time :| 1. SSH: not working, received "connection timed out" - so I didn't get to introduce any password Note: ssh IS NOT working at all for the Windows 10 pool, while it does for Windows 7 and Windows 8. 2. VNC: times out, checked other Windows 10 machines and it worked just fine 3. RDP: - root: tried various passwords, none of them worked Note: Windows 7 and Windows 8 machines don't allow connecting via RDP unless the machine is moved to the loaner OU and rebooted. Windows 10 seems to allow this but since the root password is messed up, connection doesn't work (tried this on other Win10 machines as well) - cltbld: not working. Tried connecting to other Win10 machines and it worked fine. (In reply to Van Le [:van] from comment #8) > any ideas? fwiw, the aspect-low passwords didn't work on the minis either. Checked several Win7, Win8 and OS X 10.10.5 machines and I was able to connect using the password stored in "aspect-low-security.txt.gpg" file.
Filed bug 1401893 for fixing these connection issues.
so definitely something funky with this machine even after reimages. we have 2 iX winXP we recently retired, do you want to use those instead while we troubleshoot this one? or is your win10 pool healthy enough to wait this out?
(In reply to Van Le [:van] from comment #11) > so definitely something funky with this machine even after reimages. we have > 2 iX winXP we recently retired, do you want to use those instead while we > troubleshoot this one? or is your win10 pool healthy enough to wait this out? Sorry for the late reply. Our Win 10 pool is capable of handling the current load, so we could wait for troubleshooting this one.
This bug was mentioned over here https://bugzilla.mozilla.org/show_bug.cgi?id=1403471#c7 that this machine may have a similar issue. Rel Ops could you look at them both together?
You need to log in before you can comment on or make changes to this bug.