I keep running into this issue where when I try to save local app files from a Hololens to my computer via the Windows Device Portal, the Portal takes forever to download them and eventually times out. This is frustrating since I have no problem connecting to the Portal otherwise, and the files I'm trying to download are super small. Does anyone know of another way I can access these files?
WDP shows that it's waiting on the IP address for minutes before losing connection
How did you connect your HoloLens to the PC? With Wi-Fi or USB? To check if there are connectivity issues in your network, it is recommended that you try another connection method to access the Device Portal by following this doc:Using the Windows Device Portal. If the behavior still occurs, please open a support ticket through this link: http://aka.ms/hololenssupport so that we can diagnose it deeper for you.
I figured out my problem. I had the Hololens connected via USB yet was using the Device Portal as if I were connect remotely. To solve my issue, I had to use the address http://127.0.0.1:10080/ rather than the Hololens IP.
Related
I want to be able to use a camera on an Azure Virtual Machine using Windows 10.
Camera feed can either come through on local machine or a feed from another machine. Either way I get the below error:
We can't find your camera, NoCamerasAreAttached.
Even though I have enabled both through the connection and enable USB Redirection in Windows 10. incl gpedit.msc
the easiest solution I discovered is that you can go to the settings of Remote desktop connection in the general tab, go to the connection setting and select your RDP file of azure VM:
Second, in the RDP setting go to the local resource and then go to the local device tab in setting and click on the 'more' button:
Enable both checkpoints inside the video catalog that include the webcam option:
goog luck! hope it saves your day!
#syedasadrazadevops
First of all, make sure you have enabled devices redirection in the Remote Desktop connection via MSTSC. And check if you have enabled USB Redirection in both sides of the client and VM via GPEDIT. For more details, Refer to this case.
I accidentally told my network adapter to use a bad ip address in my Internet Protocol Version 4 (TCP/IPv4) properties. A big oops look spread across my face as I pressed the OK button and immediately got disconnected from my remote session. Naturally I can't remote back in and even azure can't reboot the vm. Is there any way I can recover from this?
So things I would do include:
1. Redeploy
2. Try to change VM ip using the portal\powershell
3. Delete the VM and deploy new one using the same os\data disks.
I accidently broke my centos VM in azure by twiddling firewall rules within it. After a reboot, the normal ssh access is not working anymore. Is there any chance to get into that VM, any console login directly to the machine somehow?
After reading the current state (April 2016) at microsoft about this, I've decided to dump the virtual machine and set it up again:
This one-directional access is just a start. Console screenshots and serial output can help identify a problem, but they are not the solution for resolving the problems. We are working on enhancements that will enable secure bi-directional access to the console of the virtual machine. This will enable additionally debugging capabilities, and, more importantly, the ability to resolve a set of common problems through the bi-directional access. Right now, I don’t have a timeline but we know this is critical.
(article)
I tried to install a hardware I've installed in my previous computer under Windows 7, basically an external network card with antenna, but when I try to use it, after installed it I get this bluescreen error:
BUGCODE_NDIS_DRIVER
I don't know if it's possible to fix it, any useful information?
PS: If this isn't the best Stack forum, please guide me to the right one.
There is some technical information on Windows Dev Center - Hardware on this bugcheck. Driver developers can find the cause from the bugcheck code and parameters.
I can duplicate the BUGCODE_NDIS_DRIVER blue screen on my Windows 8.1 developer box fairly easily by opening two different VPN tunnels. Luckily, I don't need both running at the same time, so my solution is "don't do that".
For example, I open SonicWALL Global VPN Client to connect to one network. Then, I open the Cisco VPN client to connect to another. The crash happens almost immediately.
If you have two active network card, deactivate one, that is all.
I connected two laptops using a cross-over cable. My IP Address is 192.168.1.1 and the other IP Address is 192.168.1.16. We both are able to ping each other and the reply is perfect. There is no loss of packets.
The problem is I shared a file and the other system is not able to open my IP Address using the run command. Even I am not able to open my Shared folder by giving in the run (\\192.168.1.1). A dialogue box with the message \\192.168.1.1, The Network Path was not found opens each time we try this.
But I am able to open his shared folder by giving in run command (\\192.168.1.16). I closed all the firewall services in my system. But still my system is not able to respond. Also we are not able to use remote desktop connection.
Can anyone please help me in solving this?
Additional Details: I use Windows XP and the other machine uses Windows 7. We both are in the same work group.
Here are some steps to solve your problem:
Did you set the static IP by yourself or that come automatically?
If yes then please go and set the IP manually
Then share the file and put the permission of that file to Maximum (If you believe your partner)
Then power down the firewall or antivirus for some moments (say 10 minutes)
Now try to connect using the \192.xxx.xxx.xxx method using the Run window
If the 5th step is not working, then try disabling and reenabling the LAN card, then try the 5th step again.
Hope that solved your problem.
Remote Desktop needs to be explicitly enabled. Right click on "My computer", go to properties and look at the remote settings tab.
I advice you to use Radio Access Point to connect both windows 7 and windowsXP. I think this is best choice of troubleshoting jaringan. why?
Because I already do anything to connect both Operating System but can't solve that problem.