Question Locked

Accessing Windows machines across a VPN; some anomalous behaviour

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hey all!

Okay, so I have a few VPNs that I connect to on occasion. There are a few interesting issues that I've come across with one in particular.

1. On one VPN connection, I can access machines that are on the remote network by their IP address but not by their DNS name.If I remote desktop into a machine that is on the remote network, DNS resolves nicely and I can ping my computer. An ipconfig /all reveals that the PPP adapter for the VPN has set me up with the correct DNS server on the remote network. Yet, on a different VPN connection I can access machines by both IP and DNS addresses. The client configuration on my end is the same for both VPNs.

2. I can ping a remote machine and remote desktop to it via the IP address but if I try to connect to it via a UNC path using the same IP, I get a "Windows cannot access \\[IP Address]\ Error code 0x80070035: The network path was not found" error. If I remote desktop into a computer on the remote LAN, I can UNC to my heart's content, including UNCing back across the VPN to my client machine.

Both of these things only occur on one VPN connection. Another VPN connection behaves quite nicely. Seems rather odd to me. It's not confined to DNS, because UNCing to IPs is munged as well. What am I missing?

Thanks,

6 replies

by nonapeptide

Two things are at play here.

The first: The fellow that set up the network originally felt it necessary to change the workgroup name of the Windows machines to the business's acronym, rather than the default WORKGROUP. Thusly, anything using NetBIOS names (SMB/CIFS) would not work correctly until I changed my machine's workgroup.

Second, when I VPN into the network I'm given the SMB router's address as the DNS server, which would normally be okay except that every other machine on the network is set to use the ISP's DNS server. Thusly, a host's DNS names are not registered with the router and I cannot access anything by its DNS name.

Three cheers for nonstandard practices.

by nonapeptide

I had never thought of subscribing to posts to bump them later...

In fact, there's not a lot of features that I use on this rather unique message board implementation. So many of them either don't work or don't seem to server a practical purpose.

by nonapeptide

I should have stated that.

Also, some bizarre behaviour is still behing observed. So maybe "Solved!" should have rather read "(Almost) Solved!"

Ah well.

This discussion is closed to new replies.