I have a small server app, which receives UDP data on port X. When I run this app with a local logged in user account, all is fine and my app receives commands via UDP. But when I'm installing the app as a windows service which runs under same local user account, I'm not longer receiving data, when I try to connect from a different machine. Local connections are fine. I've also opened my UDP port X in the windows firewall settings, but with no luck.
Any help is appreciated.
Only for the sake of completeness:
It has been found that it has something to do with the virtual machine in which the Windows runs. I use a network bridge to connect it to my local network. After adding a host-only network adapter, my windows service received all expected commands. No idea why!?
Related
I'm running a avahi deamon on my linux server to publish a service at my local network.
For testing purpuse I use dns-sd.exe from bonjour for discovering. After connecting to the LAN service discovery is working well. But if I close the connection, connect to a different network (e.g. hostspot of my iphone) und reconnect to LAN service discovery is not working anymore.
I have to restart windows to solve this issue.
I have also noticed this behavior with other (self implemented) clients (with the use of DNSAPI.dll, mono-zeroconf).
It looks like windows is reconfiguring something in the background.
Does somebody has any idea?
which technology they use for the backend in windows for remote access without internet?
here is the link -
https://support.microsoft.com/en-us/windows/how-to-use-remote-desktop-5fe128d5-8fb1-7a23-3b8a-41e636865e8c#connect-using-remote-desktop-connection=windows-7
In fact when you are not connect to internet you can not Access to other devices by remote access tools.in this case you can access to devices which are in your Local network only.
another condition is your device does not connect to internet directly but nearest your local router which has NAT configuration connected to internet and you use this router IP as gateway.so you are connected to internet and can remote access to other devices in your VLAN.
This may be my misunderstanding but you require a network connection to connect to Microsoft remote desktop..
No network connection no remote desktop.
Remote desktop works bt connecting across the network/Internet to TCP PORT 3389.
Now you "could" connect via modem but it would be so SLOOOOOWWWWW as to be basically unusable.
It is discussed here https://superuser.com/questions/992183/connect-2-pcs-together-via-the-pstn-using-dial-up-modems
Good luck
Tom
I'm using a Windows Server 2019 server from Microsoft Azure. I have installed Hyper-V with the management tools and am now trying to setup a Ubuntu 14.04LTS VM inside of Hyper-V. I create a new External Switch however when setting up the Ubuntu instance there it tells me that there is an issue with the DHCP server. When I check my network connections for the newly created switch there is IPV4 connectivity, with packets being sent and received.
Things that I have tried:
-Ensured that inside of the Virtual Switch Manager that in my newly created virtual switch, the external network is selected as my main internet adapter. And that the "Allow management os to share this network adapter".
-Tried selecting "Internal Network"
-Inside of the ubuntu server, tried dchlient -r and dhclient eth0 to try to retrieve a new IP (For internal network this has worked, but without internet access, for external ip it hangs on the command dhclient eth0)
-In Network Connections I have tried bridging the two connections (out of desperation, "bricks" the vps causing me to not be able to rdp, must create a new azure vm)
-I have tried right clicking the main "ethernet" inside the Network Connections and allowing sharing options to other users.
Please help as I'm quite lost as to why the Ubuntu Guest is not connecting to the internet with the new network switch
The virtual switch connection types are very confusingly named, and sharing is somewhat flaky. I've had best results with the Internal Network. Most of the time it just works but there are certain situations when the NAT service breaks and you will have to restart some combination of the host and guest machines, possibly both -- I've not found a way to just restart the virtual switch service without restarting the host OS.
If you need to use the External Network type, be aware that your actual physical router will be in the mix, so you must make sure that it is properly configured, especially if you're doing MAC filtering on your router and the guest is not using the hardware MAC. This usually happens because of the virtualisation process itself, even if it's not something you've configured in the guest.
I am trying to rdp from my local mac to an Azure instance through a (IKEv2) vpn connection. I am never prompted for a password, and it looks like the connection just times out. The error code I get is 0x204.
I have tried using both Microsoft Remote Desktop 8 and 10 for mac.
The connection is active and reports that it is connected.
From the mac, I can connect to another VM (in the same azure account) which is not running behind a vpn.
From Parallels Desktop (with networking set to Shared mode and the vpn connection active on the mac), I can successfully connect using the windows rdp client.
So it seems the Microsoft RDP-client for mac is not using the vpn connection.
Is there a way to make it do so?
Is there another solution, that will allow me to rdp to an Azure VM from my mac (without going through Parallels)?
Note: This is not the same question as this, since that is not about going through an azure vnet gateway.
I needed to add hosts file entries for each azure site I needed to access.
For example for accessing my-vm-name.someregion.cloudapp.azure.com, I needed to add a hosts file entry for it's private IP within the subnet. E.g. 10.2.0.100.
The reason everything worked in Windows under Parallels, is that the relevant entries had already been added to the hosts file previously.
I'm being in a tough spot, having created 2 different virtual machines on Azure, with windows server 2012 R2 OS. I'm trying to host a game server for a game, which requires ports 7777 and 27015 opened.
What I did is simple, I went into the panel, set-up endpoints for 7777, 27015, for UDP and TCP, and added exceptions to firewall as well for incoming/outcoming 7777, 27015 TCP and UDP.
canyouseeme.org still apparently can't find my service and shows me the ports are not opened. It shows my remote connection port is opened though. What am I doing wrong? Is there anything more that I need to know?
Image showing forwarded ports
If you opened the ports on your Firewall and on the Endpoints screen you are probably fine to game. The problem is probably with the utility that you're testing with and not the ports themselves.
I logged onto an Azure VM that I know I can remotely connect to, tested an open port that I know is open with that website, and it said it did not find it. Maybe that site is using Ping, which gets stuck in Azure's load balancer. To test connectivity, try using PSPing. This will let you test connections to specific ports. https://technet.microsoft.com/en-us/sysinternals/bb896649