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

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!