Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am having a php based webapp on azure windows server 2012 vm. Everything was fine till now. Since a day, whenever I try to connect through RDP, a full black screen get displayed, and after sometime the RDP window gets closed automatically. On Azure portal, the VM looks fine. I tried redeploying, restarting, still no success, and the vm is still working (the webapp is accessible and working) and the IP is static. What should I do to resolve this?
This is known to be an issue over screen resolutions or slow internet connections / client connectivity problems.
I'd suggest first to try to see if this is a problem with resolution on your client. Try the following:
Click on the black RDP windows (to select it) and press CTRL-ALT-END to bring up the Windows Security screen and select LOG OFF, then log back in (If you're using a RDP client like e.g. remote desktop manager, click the Send Ctrl-alt-delete so the keys are actually sent to the session).
Start a new rdp client on your desktop but before you click connect, click the show options link, click the display tab and set the DISPLAY CONFIGURATION to a low resolution like 640×480
When connection you can also try to disable Bitmap caching (click the experience tab and disable bitmap caching before connecting).
This is a known problem, check Microsoft knowledge base
If this doesn't work, I would investigate further too see if there's any network issues / firewall issues dropping your RDP packages.
I had this exact same issue. I started Task Manager (CTRL+ALT+END as explained in one of the other answers) and then started explorer.exe from File>Run new task to get the desktop.
Apparently explorer.exe had not started automatically when I first logged on, hence the blank screen.
I fixed this by remoting using a computer that had remote allowed. My current computer had Windows Home Edition, but I had a VM on virtual box with Windows Pro. So I remoted using that VM.
I had this problem and i tried all the suggestions. Nothing worked...
I ended up restarting the VM in Azure which fixed the problem.
This solution is not recommended thou. Its was a last resort.
To restart the VM in Azure, login and select the VM you want to access. Click the Restart button at the top of the list.
... then pray
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 hours ago.
Improve this question
My company is a Lenovo shop and we stood up a WDS server some time ago that boots computers into MDT to deploy images. We've done all sorts of models, from T480s to T490s, T14s, P51, P52, P53, without a single issue. I never did much with drivers in the boot image because it always just seemed to work. Until, that is, we got some new T14 generation 2 and P15 generation 2 models. No matter what I do, they will not successfully boot into MDT.
What happens is we PXE boot these new model machines, they contact the PDX server, load the boot image, I see the background image we set in MDT, and then we immediately get this image, or sometimes, it displays the prompt to start the deployment wizard, and THEN after clicking the start button it displays this error.
On the P15 gen2:
A connection to the deployment share (path) could not be made. The following networking device did not have a driver installed: PCI\VEN_8086&DEV_15F3&SUBSYS_22D817AA&REV_03.
On the T14 gen2:
A connection to the deployment share (path) could not be made. The following networking device did not have a driver installed: PCI\VEN_8086&DEV_15F3&SUBSYS_22D817AA&REV_20.
Once and only once, a T14gen2 went all the way through the deployment task sequence, booted into Windows 10, and THEN displayed the error.
Some googling led me to this page, where I found that the T14gen2 and P15gen2 have specific WinPE 10 driver packs: https://support.lenovo.com/us/en/solutions/ht074984-microsoft-system-center-configuration-manager-sccm-and-microsoft-deployment-toolkit-mdt-package-index
Ok, great. Problem solved. So I downloaded and extracted each package, created a folder in my Out-of-Box driver packs, imported the drivers into there, made a selection profile for that folder, and configured WinPE to grab drivers from there in the Deployment Share properties, then imported that boot image into WinPE.
Then I PXE booted each model and got the same behavior. I'm a little stuck, and wondering if anyone here has run into this before or has any clues on where to go.
Also, originally, I just left the WinPE drivers on 'All,' imported all of the P15g2 and T14g2 drivers into Out-of-Box drivers, and just let the boot image grab what it needed. That broke everything. Computers would boot from the image and then display a message saying that Windows couldn't boot because iaStorAfs.sys couldn't be found. I had to rebuild the entire MDT environment to recover from that.
So right now, just the WinPE drivers for the T14g2 and the P15g2 are being injected into the image, as well as the drivers for the USB-C gen2 dock (https://download.lenovo.com/km/media/attachment/USBCG2.zip). Every other Lenovo model still boots into MDT no problem, and the two models I loaded drivers for don't.
Any insight appreciated! This has been driving me nuts for a while.
I got the same error with Lenovo Thinkpad T14 Gen2(Type 20W0).
PCI\VEN_8086&DEV_15FC&SUBSYS_22C917AA&REV_20
How to reslove this issue, go to Lenovo website https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-2-type-20w0-20w1/downloads
and enter your serial number to download the network driver,my Thinkpad NIC was Intel i211-v, so I download it and import to MDT out-of-box WinPE driver,after that I boot my laptop via PXE and no error prompt,about 15 mins complete the Win10 deployment, hope this can resolve your problem.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I have one centos 7 (minimum setup) installed on cloud .
I m connect it using using putty on my laptop.
I have installed Firefox on centos server which has fast internet connection.
However whenever i run Firefox its not loading because it doesn't have GUI installed (and i m connecting it using putty).
I want to browse internet on it from windows machine. How can i go about it?
Error Message
# firefox
Error: GDK_BACKEND does not match available displays
Please help
You need to supply Firefox with a virtual graphic screen. You could for example install XMing on Windows, and configure PuTTY to "forward X connection".
Then Firefox will "draw" on the screen, and the screen will be transmitted to your PC. Your mouse and keyboard signals will be transmitted to the remote server.
This setup should go about six times as slow than your current Web connection, since your connection to the Internet, which is the bottleneck, is unchanged, and now you're pushing massive X data on it instead of browsing elements.
A better possibility would be to install Squid proxy on the remote server, then configure your PuTTY to open a "tunnel" from remote port 127.0.0.1:3128 to local port 3128, and finally instructing your Windows Firefox to use 127.0.0.1 on port 3128 as proxy for all protocols.
This way, the browsing information will be downloaded remotely, compressed and forwarded to you.
This should be around twice as slow as your current connection (unless you're connecting with old Web sites without gz/deflate support, and mostly text with no images. In that case you might experience a connection up to five times as fast, albeit with a somewhat increased latency.
(An even better but even more complicated setup involves running a local proxy, connected through SSH tunnel to a remote proxy).
In all cases your navigation might appear as coming from the remote machine, but to ensure there's no information leak, you need to properly configure the proxy.
Use the below command to connect
$ ssh -Y whatever.com
On the Centos server, edit the file /etc/X11/sshd_config, it will be necessary to turn on X11 forwarding with a line like
X11Forwarding yes
In the putty Enable X11 forwarding in the configuration.
You can forward X over SSH, but it is painfully slow. Something like NoMachine will do far better.
However, if you are trying to get faster internet, you may be out of luck as any attempt to improve this will just add overhead.
You may be able to set up a VPN to improve the compression on data you receive from other websites. Take a look at this SO post for some information about what's available and what solutions already exist.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I use windows 8.1 64-bit on my machine and recently, without having installed any new application, I get the following error when connecting to VPN:
Error 720: Unable to establish a connection to the remote computer.
Might need to change the network settings for this connection.
Tenentei already follow several tutorials but in no've succeeded.
Example configuration that tried to accomplish:
http://en.remontka.pro/error-720-windows-8-and-8-1-solved/
Thankyou
Since I can't find a complete or clear answer on this issue, and since it's the second time that I use this post to fix my problems, I post my solution:
why 720? 720 is the error code for connection attempt fail, because your computer and the remote computer could not agree on PPP control protocol, I don't know exactly why it happens, but I think that is all about registry permission for installers and multiple miniport driver install made by vpn installers that are not properly programmed for win 8.1.
Solution:
check write permissions on registers
a. download a Process Monitor
http://technet.microsoft.com/en-us//sysinternals/bb896645.aspx and run it
b. Use registry as target and set the filters to check witch registers aren't writable for netsh: "Process Name is 'netsh.exe'" and "result is 'ACCESS DENIED'", then get a command prompt with admin permissions and type netsh int ipv4 reset reset.log
c. for each registry key logged by the process monitor as not accessible, go to registers using regedit anche change these permissions to "complete access"
d. run the following command netsh int ipv6 reset reset.log and repeat step c)
unistall all not-working miniports
a. go to device managers (windows+x -> device manager)
b. for each not-working miniport (the ones with yellow mark): update driver -> show non-compatible driver -> select another driver (eg. generic broadband adapter)
c. unistall these not working devices
d. reboot your computer
e. Repeat steps a) - d) until you will not see any yellow mark on miniports
delete your vpn connection and create a new one.
that worked for me (2 times, one after my first vpn connection on win 8.1, then when I reinstalled a cisco client and tried to use windows vpn again)
references:
http://en.remontka.pro/error-720-windows-8-and-8-1-solved/
https://forums.lenovo.com/t5/Windows-8-and-8-1/SOLVED-WAN-Miniport-2-yellow-exclamation-mark-in-Device-Manager/td-p/1051981
This solved my 720 problem. The idea is to change the driver of the faulty WAN to another network adaptar driver, and then we are able to uninstall the WAN device and then reboot the system.
https://forums.lenovo.com/t5/Windows-8-and-8-1/SOLVED-WAN-Miniport-2-yellow-exclamation-mark-in-Device-Manager/td-p/1051981
First I would like to thank Rose who was willing to help us, but your answer could solve the problem on a computer, but in others there was what was done could not always connect gets error 720.
After much searching and contact the Microsoft support we can solve.
In Device Manager, on the View menu, select to show hidden devices.
Made it look for a remote Miniport IP or network monitor that is with warning of problems with the driver icon. In its properties in the details tab check the Key property of the driver.
Look for this key in Regedit on Local Machine, make a backup of that key and delete it. Restart your windows.
Reopen your device manager and select the miniport that had deleted the record. Activate the option to update the driver and look for the option driver on the computer manually and then use the option to locate the driver from the list available on the computer on the next screen uncheck show compatible hardware. Then you must select the Microsoft Vendor and the driver WAN Miniport the type that is changing, IP or IPV6 L2TP Network Monitor.
After upgrading restart the computer.
I know it's a bit laborious but that was the only way that worked on all computers.
Based on the Microsoft support KBs, this can occur if TCP/IP is damaged or is not bound to your dial-up adapter.You can try reinstalling or resetting TCP/IP as follows:
Reset TCP/IP to Original Configuration- Using the NetShell utility,
type this command (in CommandLine): netsh int ip reset [file_name.txt],
[file_name.txt] is the name of the file where the actions taken by
NetShell are record, for example netsh hint ip reset fixtcpip.txt.
Remove and re-install NIC – Open Controller and select System. Click
Hardware tab and select devices. Double-click on Network Adapter and
right-click on the NIC, select Uninstall. Restart the computer and
the Windows should auto detect the NIC and re-install it.
Upgrade the NIC driver – You may download the latest NIC driver and
upgrade the driver.
Hope it could help.
I had the same problem. Most posted solutions would not work.
I ran sfc /scannow and it reported that some errors could not be fixed.
To address that problem I ran the command
Dism /Online /Cleanup-Image /RestoreHealth
Ironically, I later found the WAN errors had gone away, the 720 VPN error went away and my VPN worked.
Hard to believe that the WAN errors were corrected by this rather esoteric command, but it's worth a try.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am wanting to install OpenShift Origin on my PC running Windows 7.
I am completely new to Linux environments and terminology but wanted to 'look around' the OpenShift product with the hope that I can become familiar with its offerings and features.
So I have started here:
https://www.openshift.com/products/origin
Where the instructions are:
"The easiest way to run OpenShift Origin locally is to download an image suitable for running on a VM. The image will work on KVM , VirtualBox or VMWare . You can also spin up a VirtualBox instance using Vagrant or build your own machine using Puppet".
I have downloaded openshift-origin.latest.tgz and I am assuming the next step is to download and install a 'VM' (something I also have never used)?
I have heard the name VMWare before but when I visit the site there seem to be 15+ different products and I'm not sure which one is required for the above task.
So, is it possible for someone to provide a <ul> of steps required to install and run OpenShift Origin on Windows 7?
A google search for how to install openshift origin on windows 7? does not seem to return any immediately obvious results (the first result links to an article that starts with [obsolete]).
There is a video called 'open shift origin setup' here:
http://youtu.be/rzW3N_C5sIE
But it starts with a file called 'openshift_origin.iso' and not the 'openshift-origin.latest.tgz' that I have downloaded and then it gets into some terminal coding that is completely foreign to me.
Any pointers appreciated.
Edit:
In addition to accepted answer below, as virtual machines may be a bit ominous to newbies here are some screenshots which show the installation of VirtualBox, it was really pretty easy.
For Windows 7, I downloaded VirtualBox 4.2.16 for Windows hosts x86/amd64 from:
https://www.virtualbox.org/wiki/Downloads
and then ran the installer:
Then you will see a few of these type of screens, just click 'Install'.
Unfortunately then when running OpenShift, as per instructions in accepted answer, I got this message:
And I haven't been able to find a workaround to this yet.
But this error shouldn't occur for those who have hardware acceleration enabled.
VirtualBox
VirtualBox is freely available.
Open VirtualBox from the Start Menu - this opens the VirtualBox Manager.
Open the menu File > Import Appliance or press CTRL+I.
Click Open Appliance...
Browse to the folder you downloaded OpenShift Origin to.
Select the .ovf file.
Press Next.
Press Import.
It'll import the file for a while (roughly 2 minutes on my computer) and show up as a Virtual Machine afterwards. You can just click Start and it'll boot up.
VMWare
VMWare Player is free for personal non-commercial use while most other VMWare products are not.
I haven't personally tried this route, but it seems easy enough to just open the .vmx file directly.
Your choices of software to run the ISO (VM image with Fedora) on Windows is VirtualBox or VMWware Workstation. Here's an interesting article that compares the 2:
http://www.infoworld.com/d/virtualization/review-vmware-workstation-9-vs-virtualbox-42-203277
2 unrelated things here...
First, if you do not have a hardware virtualization enabled 64 bit processor (listed as VT-X on Intel chips, and AMD-V on AMD processors), then you cannot host an OpenShift Origin VM, which itself spawns VMs, and thus not only needs the virtualization enabled processor, but needs its VirtualBox VM enabled for virtualization (a checkbox under System/Acceleration in the settings for the VM).
Second, OpenShift Origin relies on multicast DNS, which is not supported on Windows 7, so it won't work.
If you can install Fedora 20 Alpha (I expect Fedora 19 will work, but I haven;t tried it) onto metal, then install VirtualBox and the nss-mdns RPM, that should work.
Been there, done that, got the headache.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am running a VNC server on Linux and a TightVNC viewer (ver.1.3.10 from 2/10/2009) on Windows with 2 monitors attached to it. I would like to have a full-screen session on both monitors at the same time, but whenever I do that, my full-screen always uses only one monitor.
Is it possible to extend the full-screen onto both local monitors? Perhaps there is a more modern version of a viewer that could make it work?
(In regular, not full-screen mode, it is easy - just run the VNC server with double desktop size and stretch the window on the local machine across both monitors. It's the full-screen mode that I cannot make work.)
Real VNC Viewer (5.0.3) - Free :
Options->Expert->UseAllMonitors = True
RealVNC 5.0.x now offers a VNCViewer that will do dual displays on Windows without having to buy a license. (Licensing now covers the SERVER portion of their tools).
The free version of TightVnc viewer (I have TightVnc Viewer 1.5.4 8/3/2011) build does not support this. What you need is RealVNC but VNC Enterprise Edition 4.2 or the Personal Edition. Unfortunately this is not free and you have to pay for a license.
From the RealVNC website [releasenote] http://www.realvnc.com/products/enterprise/4.2/release-notes.html
VNC Viewer: Full-screen mode can span monitors on a multi-monitor system.
tightVNC 2.5.X and even pre 2.5 supports multi monitor.
When you connect, you get a huge virtual monitor.
However, this is also has disadvantages.
UltaVNC (Tho when I tried it, was buggy in this area) allows you to connect to one huge virtual monitor or just to 1 screen at a time. (With a button to cycle through them) TightVNC also plan to support such a feature.. (When , no idea)
This feature is important as if you have large multi monitors and connecting over a reasonably slow link.. The screen updates are just to slow..
Cutting down to one monitor to focus on is desirable.
I like tightVNC, but UltraVNC seems to have a few more features right now..
I have found tightVNC more solid. And that is why I have stuck with it.
I would try both. They both work well, but I imagine one would suite slightly more then the other.