Cannot access PC remotely when Monitor is powered off
| Newsgroups | gmane.network.tight-vnc.general |
|---|---|
| Message-ID | <CABBKwRsdefPSsFixb23BUdL3L9r_=1V_v0n-+m_+ae6GT9oWYA@mail.gmail.com> |
--===============6097823044638378229== Content-Type: multipart/alternative; boundary="000000000000c48e5c06328a0ef0" --000000000000c48e5c06328a0ef0 Content-Type: text/plain; charset="UTF-8" Swapped out a tower PC with GTX video card running Windows 10 for a mini running Win 11 Pro and an AMD Radon video card. Previously I had no issues powering off the PC (located in a different room) and connecting via tightvnc to the tower. Now, with the Mini, I basically get a black screen and if an image ever comes up, after login, I have no ability to do anything. I have another mini that runs Win 11 Pro, but uses Intel video and it's headless, no problem with that. Even pulled the hdmi cable from the problem mini to see if having no connection might help - did not. But as soon as I put the cable back in and powered on the monitor, full access is restored. I can live with this behavior if there is no other circumvention within Windows and/or TightVNC. I've been pointed to using a virtual display utility and may give that a try (a physical dongle won't work with my setup). Just want to make sure I haven't done something dumb. -- [email protected] --000000000000c48e5c06328a0ef0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Swapped out=C2=A0a tower=C2=A0PC with GTX video card = running Windows 10=C2=A0 for a mini running Win 11 Pro and an AMD Radon=C2= =A0video card.=C2=A0 Previously I had no issues powering off the PC (locate= d in a different room) and connecting via tightvnc to the tower.=C2=A0 Now,= with the Mini, I basically get a black screen and if an image ever comes u= p, after login, I have no ability to do anything.=C2=A0</div><div><br></div= ><div>I have another mini that runs Win 11 Pro, but uses Intel video and it= 's headless, no problem with that.</div><div><br></div><div>Even pulled= the hdmi cable from the problem mini to see if having no connection might = help - did not.=C2=A0 But as soon as I put the=C2=A0cable back in and power= ed on the monitor, full access is restored.</div><div><br></div><div>I can = live with this behavior if there is no other circumvention=C2=A0within Wind= ows and/or TightVNC.=C2=A0 I've=C2=A0 been pointed to using a virtual= =C2=A0display utility and may give that a try (a physical dongle won't = work with my setup).</div><div><br></div><div>Just=C2=A0want to make sure I= haven't done something dumb.</div><div><br></div><span class=3D"gmail_= signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature" = data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><a href=3D"mailto:steve= @steveattias.com" target=3D"_blank">[email protected]</a></div></div></= div> --000000000000c48e5c06328a0ef0-- --===============6097823044638378229== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============6097823044638378229== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________ TightVNC mailing list, [email protected] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list --===============6097823044638378229==--