Tightvnc черный экран при подключении windows 10

check
Best Answer

1. If you don’t have a monitor hooked up to the target machine, do so and try again (why)
2. Try to remote to the target with another windows machine (variable isolation)
3. If you can control the machine from a windows machine, the Mac is the issue. Tag me if the monitor thing doesn’t work, and after you tested Windows ↔ Windows
and I’ll help you more.

2 found this helpful
thumb_up
thumb_down

View Best Answer in replies below

8 Replies

1. If you don’t have a monitor hooked up to the target machine, do so and try again (why)
2. Try to remote to the target with another windows machine (variable isolation)
3. If you can control the machine from a windows machine, the Mac is the issue. Tag me if the monitor thing doesn’t work, and after you tested Windows ↔ Windows
and I’ll help you more.

2 found this helpful
thumb_up
thumb_down
Look for the video driver download at the VNC site.

2 found this helpful
thumb_up
thumb_down
Thanks, Christopher_001 You’ve raised a very good point — the laptop is docked, so technically there is no monitor! I’m just inside an RDP session on it, but I want to be able to still see the screen on another machine (via VNC) so I’m not tied to my desk all the time.

No way to make this work with VNC then I guess…?

1 found this helpful
thumb_up
thumb_down
1. If you don’t have a monitor hooked up to the target machine, do so and try again (why)

This is the issue — thank you!

1 found this helpful
thumb_up
thumb_down
Maybe TeamViewer or something else would work? I need to be able to control an RDP session remotely via something _not_ RDP (if that makes sense).

1 found this helpful
thumb_up
thumb_down
CrimsonKidA wrote:

Christopher_001 wrote:

1. If you don’t have a monitor hooked up to the target machine, do so and try again (why)

This is the issue — thank you!

CrimsonKidA wrote:

Maybe TeamViewer or something else would work? I need to be able to control an RDP session remotely via something _not_ RDP (if that makes sense).

2 found this helpful
thumb_up
thumb_down
….take a look at Ultra VNC Opens a new window and see how you like it.

Yes, uVNC does indeed have a virtual display driver — thanks again!

Was this post helpful?
thumb_up
thumb_down
There is an app named Remote Ripple Opens a new window, they have a version for Mac, also remote desktop.

Was this post helpful?
thumb_up
thumb_down

Источник

В ходе эксперементов обнаружилось следующее: если попытаться подключиться через VNC-Viewer 5.2.0 то получаем черный экран и следующую запись в логах:
[gm] [VNC] Client VNC version 8 (RFB 003.008).
[gm] [VNC] Password ok.
[gm] [VNC] 12 encodings.
[gm] [VNC] bits-per-pixel 8, depth 8, big-endian false, true-colour false.
[gm] [VNC] red-max 0x0000, green-max 0x0000, blue-max 0x0000.
[gm] [VNC] red-shift 0, green-shift 0, blue-shift 0.
[gm] [VNC] 12 encodings.

А если подключаемся через VNC-Viewer 4.1.3 то получаем нормальный доступ и тогда запись в логах следующая:
gm] [VNC] Client VNC version 8 (RFB 003.008).
[gm] [VNC] Password ok.
[gm] [VNC] bits-per-pixel 8, depth 8, big-endian false, true-colour true.
[gm] [VNC] red-max 0x0003, green-max 0x0003, blue-max 0x0003.
[gm] [VNC] red-shift 4, green-shift 2, blue-shift 0.
[gm] [VNC] 7 encodings.
[gm] [VNC] bits-per-pixel 16, depth 16, big-endian false, true-colour true.
[gm] [VNC] red-max 0x001f, green-max 0x003f, blue-max 0x001f.
[gm] [VNC] red-shift 11, green-shift 5, blue-shift 0.
[gm] [VNC] 16-bit server, 16-bit client.
[gm] [VNC] 7 encodings.

Судя по всему где-то в настройках VNC-Viewera 5-ой версии что-то не так. Но что?

Источник

Summary
Files
Reviews
Support
Mailing Lists
Tickets ▾
- Bugs
- Feature Requests
- Support Requests
- Patches
News
Code

Menu
▾
▴

From: Mark F. <mf…@no…> — 2018-05-31 14:28:20

Yury,

Wow! I've never heard of Intel AMT (vPro).  I did some quick googling.  I'll investigate more as I manage clients' computers remotely using Remote Desktop, VNC and ssh.  Thanks for the new information. 

--Mark

On Thu, 31 May 2018 00:51:13 +0000 Yury Averkiev <ave...@li...> wrote:

> Hi Mark,
> I'm using it on an Intel AMT (vPro) capable hardware, which has a VNC server built-in. And I use SmartCode VNC Manager to access the computer remotely. But you can also use Intel vPro Platform Solution Manager or RealVNC Viewer Plus. 
>
> Regards,
> Yury
>
> > On May 30, 2018, at 21:02, Mark Foley <mf...@no...> wrote:
> > 
> > Yury,
> > 
> > That looks like a great device! I might get one too.
> > 
> > Question, That device just "fakes" a connected monitor. That would take care of Ed's original issue, but I don't see how you could remotely view the BIOS settings as it's not possible to have the VNC Server running when you boot into the BIOS screen. What do you mean, "this HDMI display emulator to allow me to remotely view the BIOS screen." How are you doing that?
> > 
> > --Mark
> > 
> > -----Original Message-----
> > On Wed, 30 May 2018 01:14:11 +0000 Yury Averkiev <ave...@li...> wrote:
> >> 
> >> Recently I've bought this HDMI display emulator to allow me to remotely view the BIOS screen. It only costs $10 and is 4K capable (not that I need 4K to navigate the BIOS.
> >> 
> >> https://www.amazon.com/gp/product/B01EK05WTY/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
> >> 
> >> Regards,
> >> Yury Averkiev
> >> SmartCode VNC Manager (www.s-code.com)
> >> 
> >>> On May 29, 2018, at 21:46, Mark Foley <mf...@no...> wrote:
> >>> 
> >>> The DVI emulator is probably a better idea than the KVM switch. It's designed to do exactly what you want.
> >>> 
> >>> Post your results. I'm curious.
> >>> 
> >>> Re. BIOS settings, I was thinking of the one to ignore any video errors, but there might not be such a setting and that still might not work.
> >>> 
> >>> --Mark
> >>> 
> >>> -----Original Message-----
> >>> From: Ed Meadows Tom Perkins <mos...@ou...>
> >>> To: Mark Foley <mf...@no...>
> >>> Subject: Re: TightVNC Shows black screen after Win 10 updates
> >>> Date: Mon, 28 May 2018 14:02:47 +0000
> >>> 
> >>> Hi Mark,
> >>> 
> >>> Thanks.  I don't have a KVM switch handy and there are no BIOS settings for this.
> >>> 
> >>> Someone else suggested using an EDID emulator, so I'm going to try this:
> >>> 
> >>> https://www.amazon.com/1920x1200-DVI-D-Emulator-Dummy-Headless/dp/B01EISICO0/ref=sr_1_10/140-3476651-2228763?ie=UTF8&qid=1527515656&sr=8-10&keywords=DVI-D+emulator
> >>> 
> >>> There's probably a non-hardware solution/setting somewhere, but for $18, why not?
> >>> 
> >>> Thanks,
> >>> 
> >>> Ed
> >>> 
> >>> On 5/27/2018 7:30 PM, Mark Foley wrote:
> >>> Maybe the new Win 10 update is "smart" enough to detect no monitor as shut down the video memory. The VNC server maps the actual video memory. I tried something like this on purpose to turn off the real monitor video (not the monitor itself) and still see the screen on the VNC client. No go.
> >>> 
> >>> Try attaching a KVM switch or seeing if there is a BIOS setting to ignore the monitor.
> >>> 
> >>> 
> >>> 
> >>> --Mark
> >>> 
> >>> Sent from my Verizon Wireless 4G LTE smartphone
> >>> 
> >>> 
> >>> -------- Original message --------
> >>> From: MossyRock <mos...@ou...><mailto:mos...@ou...>
> >>> Date: 5/27/18 8:01 PM (GMT-05:00)
> >>> To: vnc...@li...<mailto:vnc...@li...>
> >>> Subject: TightVNC Shows black screen after Win 10 updates
> >>> 
> >>> Hello,
> >>> 
> >>> Suddenly, after applying the latest Windows 10 updates to a headless machine
> >>> used for BOINC crunching, I am getting a black screen when I try to remote
> >>> into it from another machine using TightVNC.
> >>> 
> >>> I've tried completely uninstalling and re-installing TightVNC server on it
> >>> so it's at it's most current release.  I've also tried fiddling with a lot
> >>> of its options and with the Win 10 desktop "personalizations" as well
> >>> (including the resolution) and none of it has any effect.
> >>> 
> >>> Here's the strange thing - when I attach a real monitor to it, I can remote
> >>> into it and I can see the desktop just fine. When I remove the real monitor,
> >>> the remote session goes black.
> >>> 
> >>> I don't know what's changed and I don't know what else to do.
> >>> 
> >>> Any ideas?  If you need any specifics about my machine or TightVNC's
> >>> settings, just let me know.
> >>> 
> >>> Thanks.
> >>> 
> >>> 
> >>> 
> >>> --
> >>> Sent from: http://tightvnc.10971.n7.nabble.com/VNC-Tight-List-f3.html
> >>> 
> >>> ------------------------------------------------------------------------------
> >>> Check out the vibrant tech community on one of the world's most
> >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >>> ___________________________________________________________
> >>> TightVNC mailing list, VNC...@li...<mailto:VNC...@li...>
> >>> To change your subscription or to UNSUBSCRIBE, please visit
> >>> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
> >>> 
> >>> 
> >>> --
> >>> Det angår också dig när det brinner i grannens vägg. (gammalt svenskt ordspråk)
> >>> It concerns you, too, when your neighbor's wall is on fire. (old Swedish proverb)
> >>> Meaning: We're all in this together.
> >>> 
> >>> ------------------------------------------------------------------------------
> >>> Check out the vibrant tech community on one of the world's most
> >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >>> ___________________________________________________________
> >>> TightVNC mailing list, VNC...@li...
> >>> To change your subscription or to UNSUBSCRIBE, please visit
> >>> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
> >> 
> >> ------------------------------------------------------------------------------
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >> ___________________________________________________________
> >> TightVNC mailing list, VNC...@li...
> >> To change your subscription or to UNSUBSCRIBE, please visit
> >> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
> >> 
> > 
> > ------------------------------------------------------------------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___________________________________________________________
> > TightVNC mailing list, VNC...@li...
> > To change your subscription or to UNSUBSCRIBE, please visit
> > https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
>
>

View entire thread

Источник

Blank or Black Screen When Remote Control Windows System with VNC

VNC (Virtual Network Computing) allows users to connect and remotely control another computer using a graphical desktop sharing system which based on the RFB protocol. If you run VNC Server from RealVNC, TightVNC or UltraUNC in Windows operating system such as Windows Vista and Windows 7, and trying to remote VNC connect to the system, you may face a problem where the VNC screen window of the remote computer appears to be black, dark or simply blank.

The VNC appears to be working fine and able to connect to the remote Windows system properly, as VNC client shows connection connected, prompts for password, accepts and login, and then brings up the remote Windows desktop window. However, the error symptom will occur. Users can only see a blank or black screen instead of proper Windows desktop, both in VNC window or full screen.

This Windows blank screen on VNC connection problem is most likely caused by Windows Aero theme or color scheme. The Windows Aero scheme causes the desktop to not transfer over via the VNC connection, thus users initiating the VNC remote control view only a blank or black desktop.

The solution to this VNC Windows black desktop screen problem is easy – simply disable the Windows Aero theme. To do so, right click on black space on desktop of target remote system (the one you want to remote control with VNC, where server is running), choose Personalize. Then click on Windows Color and Appearance link, follow by Open classic appearance properties for more color options link. In the Color Scheme list of options, select non-Aero theme, such as Windows Vista Basic or Windows Classic, then press OK.

If you must want and can’t live without Aero Glass effect, you can try this alternative workaround to get VNC working with Windows without turning off Aero. Install UltraVNC Server on target Windows system (server side to remote control to), then go to User Properties, and untick the Poll Full Screen option.

About the Author: LK

LK is a technology writer for Tech Journey with background of system and network administrator. He has be documenting his experiences in digital and technology world for over 15 years.Connect with LK through Tech Journey on Facebook, Twitter or Google+.

Page load link

Go to Top

Источник

a black or blank screen….Change the VNC Server CaptureMethod parameter:

On the remote Windows computer, open the VNC Server dialog.
Select Options from the hamburger menu.
On the Expert tab, filter the list for CaptureMethod , and set the value to 1.
Restart VNC Server.

Why is my VNC screen black?

How do I fix a black screen on Remote Desktop?

Solution

Disable bitmap caching for your RDP connections.
Confirm RDP account has full administrative rights on remote system.
Access the remote computer using consistent resolution – Full screen may help.
Confirm both systems’ video drivers are up to date.

Why is my server screen black?

The Issue. Using Remote Desktop the remote screen turns black right after login and you have no control. The issue appears to be caused by Screen Caching and accessing a system with different display resolution or RDP window sizes.

Why does Vnc not show real remote desktop?

vncserver doesn’t connect to the actual desktop; it creates a virtual desktop that is configured separately. If you want to access the actual desktop then you need to use either the VNC X extension or Vino.

Does VNC work without monitor?

Machine with no monitor connected, RDP works fine. TightVNC only works after physically connecting a monitor. Interested if anyone knows a workaround. Without a monitor, TightVNC only shows a black screen.

How do I fix a black screen in Windows 10?

Sometimes, a black screen happens because Windows 10 will lose its connection with the display. Using the Windows key + Ctrl + Shift + B keyboard shortcut can restart the video driver and refresh the connection with the monitor.

Why is the screen black after my Windows VM boots?

This issue is caused by the incorrect version of the VMware SVGA driver installed within the virtual machine, which comes bundled with VMware tools. To resolve this issue: Boot the virtual machine into Safe Mode. (You may also uninstall the driver instead.)

How do I turn off VDI?

To shut down a remote computer when you are using Remote Desktop, press CTRL+ALT+END, and then click Shutdown.

Can I run Windows 10 headless?

Windows 10 IoT Core can be configured for either headed or headless mode.

How to run VNC server?

On the the system you want to run vnc-server,install vnc-server as noted above.

Edit/etc/X11/xorg.conf,as root,and add/create a ‘Module’ Section and add ‘Load “vnc”‘: Section “Module” Load “vnc” EndSection

For standard vnc authentication,edit/etc/X11/xorg.conf,as root,and add to the ‘Screen’ Section: Option “SecurityTypes” “VncAuth” Option “UserPasswdVerifier” “VncAuth” Option “PasswordFile” “/root/.vnc/passwd”

As root,run ‘vncpasswd” to create the password noted above.

Restart X11 (<Ctrl>+<Alt>+<BS> will work if on the console already)

You should be able to connect with a vncviewer client as normal.

To trouble shoot,check for errors in the/var/log/Xorg.0.log or verify that iptables or selinux is not interfering with remote connections. Additional information is at http://www.realvnc.com/products/free/4.1/x0.html

How to enable VNC server on Raspberry Pi?

– On your Raspberry Pi, boot into the graphical desktop. – Select Menu › Preferences › Raspberry Pi Configuration › Interfaces. – Ensure VNC is Enabled.

What is a VNC client?

The VNC client is the program that watches, controls and interacts with the server. The server is generally controlled by the client. The VNC protocol uses the remote frame buffer protocol , which is based on graphic primitives passed from the server to the client and event messages passed from the client to the server.

Источник