Can not Remote into VMs using machine names


Recommended Posts

I have created Windows VPN on a Win2k8 server, Outside our local network, i am able to connect to the VPN. Issue i am having is, once i connect to VPN i want to be able to remote into other Virtual Machines on the corp. network using machine names i.e abc:port, it shows an error saying remote desktop connection failed.

I am able to remote into virtual machines using public IP, as well as machine local IP (all virtual machines are configured using static IPs), also i am able to ping all the Virtual machines on the network. So it seems like system is not able to process requests based on machine names. which works fine when accessed locally.

Can anyone tell me what do i need to do regarding this?

Well how are you going to resolve a host name? abc, do you have a wins server? if not then since its not a fqdn (dns like abc.domain.tld) you would have to broadcast for it. You can not broadcast across segments.

So no hostname across a vpn rarely work unless your bridging?

So a few options, use DNS - if your talking w2k8 server - do you have a Domain(AD) then you would have to have DNS - use that to resolve your computers name. If you setup a search suffix for your domain.tld then sure you can use just hostname portion and the dns query will auto add the domain.tld part.

Setup Wins if you want and don't have AD with DNS. Or just setup a host file on your computer that has a listing off all your machines IP and names and then you can use the names to connect like

192.168.1.100 abc

192.168.1.101 dfg

192.168.1.203 xyz

etc.

so for example I run dns on my local network at home, local.lan - and I have my computes in dns - so when I vpn in I hand off this dns

ethernet adapter ovpn:

	   Connection-specific DNS Suffix  . : local.lan
	   Description . . . . . . . . . . . : TAP-Win32 Adapter V9
	   Physical Address. . . . . . . . . : 00-FF-79-1A-85-63
	   Dhcp Enabled. . . . . . . . . . . : Yes
	   Autoconfiguration Enabled . . . . : Yes
	   IP Address. . . . . . . . . . . . : 10.0.200.6
	   Subnet Mask . . . . . . . . . . . : 255.255.255.252
	   Default Gateway . . . . . . . . . :
	   DHCP Server . . . . . . . . . . . : 10.0.200.5
	   DNS Servers . . . . . . . . . . . : 192.168.1.253
	   Lease Obtained. . . . . . . . . . : Tuesday, November 06, 2012 3:11:53 PM
	   Lease Expires . . . . . . . . . . : Wednesday, November 06, 2013 3:11:53 PM

So I can resolve hosts in my network via their fqdn, and my search suffix of local.lan

D:\>ping i5-w7

Pinging i5-w7.local.lan [192.168.1.100] with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time=121ms TTL=127

Reply from 192.168.1.100: bytes=32 time=121ms TTL=127

Reply from 192.168.1.100: bytes=32 time=131ms TTL=127

Reply from 192.168.1.100: bytes=32 time=119ms TTL=127

Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 119ms, Maximum = 131ms, Average = 123ms

The HOSTS file is here: C:\Windows\System32\drivers\etc\HOSTS

The file is a text file, just edit the text file and you should see something like this....

127.0.0.1 localhost

So, just add in the IP address and the name that you want to access it.

If I use localhost in my browser it goes directly to 127.0.0.1, this is how it works.

For example...

127.0.0.1 localhost

192.168.1.100 abcport

I would not suggest you setup AD just so you can use dns - you could always just fire up dns on your w2k8 box you don't have to setup AD for just simple dns.

Easier is just host file - above is the location. You will prob have problem editing it, you need to elevate your text editor to admin to be able to edit the file.

But if you were running AD, more than likely your machines would already be registering themselves in your DNS - so there would be nothing to do but use that dns server and domain suffix in your query from your remote box that vpn'd in.

"Enabling DNS in AD has taken take care of it."

This statement confuses me - you can not have AD without DNS. So there is no enabling it in AD, if you setup AD dns it is part of the setup and would be enabled from the git go.

Do you mean you enabled the DNS role and don't have AD running?

This topic is now closed to further replies.
  • Posts

    • https://shop.royalmail.com/special-stamp-issues/monty-python
    • Microsoft disables a key graphics feature in Edge by Paul Hill Microsoft has released its new security baseline for its Edge browser version 139, it includes the addition of one setting and the removal of one other. For those that are unaware, these security baselines allow admins to set an organization’s Edge browser settings to the default that Microsoft recommends at any one time. You can download the new package from the Security Compliance Toolkit. With this update, the company is enforcing the default to disable the EnableUnsafeSwiftShader policy. This will help to mitigate potential risks as malicious web content could exploit vulnerabilities in the renderer. SwiftShader is a software-based renderer that serves as a fallback for WebGL in environments without GPU acceleration, such as virtual machines. With Microsoft’s disabling of it, it seems as though this compatibility tool is now seen as a liability. The disabled SwiftShader was the most relevant in virtual machines which are widely used in enterprises, so this change poses the risk of causing a bit of disruption. While the move is a good one for security, those who it affects may want to deviate away from Microsoft’s security baselines. The security baseline announcement also mentions a new Edge for Business security connectors feature which is designed to integrate the browser with security software for DLP and authentication. Microsoft said that these connectors can close critical gaps in enterprise security. You can learn more on the feature’s landing page. Microsoft doesn’t seem to have made the change to SwiftShader due to existing vulnerabilities, instead the move seems to be a proactive security improvement. If you rely on it with your virtual machines, feel free to deviate away from Microsoft’s security baseline, but understand you’re no longer following the company’s security advice.
    • Edge 139 is out with big performance boost, password improvements, and more by Taras Buria Microsoft has released Edge 139 to all users in the Stable Channel. The latest version (139.0.3405.86) introduces some notable changes to the browser, performance improvements, and bug fixes. It also removes some of the existing features, as Microsoft strives to streamline the browser and its features. Microsoft Edge 139 brings a reworked Settings section, which is now built with WebUI2. This enables significant improvements in performance and responsiveness, which Microsoft recently detailed in a blog post. Additionally, Microsoft optimized Settings for a more cohesive user experience by simplifying the number of pages and reorganizing various options. Though it also disables an important graphics feature with this update. Wallet in Settings is discontinued. It now redirects users to the new "Passwords, Payment, and Personal Information" experience in settings. Speaking of passwords, the built-in password manager now has real-time notifications for compromised passwords. If one of your passwords is found in a known data breach, Edge will prompt you to take immediate action and create a new password. Other changes in Edge 139 include the following: Open external links in another profile when recommended by external applications. When Microsoft Edge is set as the default browser to open external links from applications, Microsoft Edge must determine which profile to open the links. Introducing a new policy that can enable/disable Microsoft 365 Copilot Chat in Edge for Business from showing in the toolbar. Edge for Business now has a dedicated policy, Microsoft365CopilotChatIconEnabled, to enable and disable Copilot in Edge from showing in the Edge toolbar. New Autofill Personal Information Settings Configuration. A web form field collection consent toggle will be available in Autofill settings (edge://settings/autofill/personalInfo). This allows users to consent to Microsoft Edge collecting web form field labels (e.g., "First Name," "Email") to improve Autofill suggestion accuracy. Web AI APIs for prompt and writing assistance. Microsoft Edge now implements the Writing Assistance APIs and the Prompt API (for Edge extensions) with a local language model, Phi-4-mini, that is built into the browser. These easy-to-use JavaScript APIs are made available via Edge flags (set to Enabled, by default only for the Summarizer and Prompt API for extensions) so that sites and extensions can apply AI capabilities on the web. Enhancements to Performance and Secure network. Browser essentials is now separated into two distinct experiences (Performance and Secure Network) - both available from the Settings and more menu (“…” on the menu bar). Reset Microsoft Edge enterprise sync. For users having problems syncing browsing data across other signed-in devices, they can reset sync data from the Microsoft servers via Edge Settings edge://settings/profiles/sync/reset. Update to Microsoft AutoUpdate policy. The MAUEnabled policy allowed admins to continue using Microsoft AutoUpdate on macOS. Finally, Edge 139 contains eight security fixes for vulnerabilities originating from Chromium. Microsoft also published a security guideline with details about a key graphics feature, which is now disabled. You can update to Microsoft Edge 139 by heading to edge://settings/help. By the way, if you uninstalled the browser and do not know how to get it back, check out this guide.
  • Recent Achievements

    • Week One Done
      harveycoleman123 earned a badge
      Week One Done
    • First Post
      EzraNougat earned a badge
      First Post
    • One Month Later
      westDvina earned a badge
      One Month Later
    • Community Regular
      Bern@rd went up a rank
      Community Regular
    • Week One Done
      Joey Solo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      667
    2. 2
      +FloatingFatMan
      196
    3. 3
      ATLien_0
      154
    4. 4
      Xenon
      132
    5. 5
      wakjak
      102
  • Tell a friend

    Love Neowin? Tell a friend!