Windows remote desktop through NAT [closed] - windows

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 8 years ago.
Improve this question
I just setup remote desktop to my Windows server 2012 R2. Thi works great from LAN. How can I setup remote desktop from outside of the LAN. I have tried NAT like this:
192.168.1.200 = windows server's IP
192.168.1.200:80 -->> my_public_IP:10200
when I want connect to it like this, it doesn't work. Maybe other local port..?

Windows vista onwards provides secure RDP connectivity over IPv6 without port forwarding configuration on NAT. This feature is called WICN & it gives a unique name to your computer using which you can directly RDP to the machine. Please check the below link to enable & use it:
http://technet.microsoft.com/en-us/library/bb727045.aspx

Related

how to give virtual machine local IP? [closed]

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 4 years ago.
Improve this question
I want to ping to my main pc so I want to make my virtual machine address local my mean pc address is 192.168.1.1 ,but my virtual machine address is 127.1.0.1
I use windows 10 and the system of the virtual machine is linux ubuntu .
When you open your virtual machine click on Devices from the menu above then network then network settings then you need to change "attached to" to Bridged Adapter then OK .

PXE booting from AWS EC2 instance? [closed]

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 5 years ago.
Improve this question
I am working to create a cloud managed provisioning system to be used with a number of computers located on home networks. As part of this, I would really like to setup a PXE server on AWS that can be booted on demand if a computer goes down.
Does PXE booting only work from the local network, or is there some way to specify the location of the server (from the local home router)? I would like to avoid use of a VPN as network bandwidth is a concern for normal operation of the machines.
You can use iPXE to accomplish this by hard coding a URL to boot from. You'd likely have to chainload to do this which is well documented at the site.

Azure - Windows VM not accessible [closed]

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 6 years ago.
Improve this question
I have a Windows VM in my Azure account. It was working fine until I changed its size to increase resources / disk size. After the update VM stopped working. I am unable to access VM with RDP or FTP etc.
I have tried restarting VM but still same. Any clue how to fix this?
After several tried, I used Reset Remote Access option. This seems to have made the VM accessible again. But unfortunately it has changed VM Ip address too.

windows server 2012 r2 not able to connect network after change ip [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 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 am wondering what is wrong with my windows server 2012 r2 standard, use this server to serve as file server only to replace my current windows server 2003 standard edition.
During installation, setup with ip address 192.168.103.200 and everything ok, after some adjustment and configuration, we decide to take the server to production and change the ip address to the old ip address and power off the old server, which the ip address is 192.168.2.2, but after change the ip address, the server is not able to connect to other computers and vice versa. Try to change the ip address to 192.168.2.3 and everything is working.
Anyone know what could the cause for this issue?
I think the source this problem there is network level. Try to ping itself. Make on server ping to 192.168.2.2. If no then this is problem with driver's NIC. But if yes... Then check your network switch or router. There are maybe any settings for MAC address and this IP address(any filter rules your firewall). I'm almost sure this problem is in port access settings in your network equipment.

Synergy 1.5.0 Windows 8 & 7 [closed]

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 8 years ago.
Improve this question
I'm trying to connect two computers with Synergy v1.5.0: Windows 8 (as the server) and Windows 7 (as the client). When I start the server there's no problem, but on the client's screen Synergy says:
"WARNING: failed to connect to server: Timed out".
I configured it on the server's side by having one screen next to the other on the Configuration Panel.
I made sure is the same port on both computers: 24800.
I have taken the IP from the command line (cmd then ipconfig) and set it on each PC.
I have tried to turned off the firewall but didn't work out.
Don't know what else to do. Any ideas?
Posted on behalf of the OP.
I have solved this by installing Synergy 1.3.1 that can be found on Sourceforge: (http://sourceforge.net/projects/synergy2/) and following this tutorial (https://www.youtube.com/watch?v=OixCfusCiuA).

Resources