Re: Resolving hostnames in remote VPN network
From: Bill Grant (not.available_at_online)
Date: 02/24/04
- Previous message: Bill Grant: "Re: VPN Settup"
- In reply to: Aaron Seet: "Resolving hostnames in remote VPN network"
- Next in thread: Aaron Seet: "Re: Resolving hostnames in remote VPN network"
- Reply: Aaron Seet: "Re: Resolving hostnames in remote VPN network"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 24 Feb 2004 11:18:55 +1000
That isn't strictly true. Your client will resolve names using the DNS
server across the link if the client is correctly configured. For this, the
client's connection properties need to have the correct DNS domain
suffix(es) as well as the DNS server IP.
LAN broadcasts do not usually cross WAN links or routers.
"Aaron Seet" <poster@news.microsoft.com> wrote in message
news:eIiWrYb#DHA.888@tk2msftngp13.phx.gbl...
> Either way when one logs in to the office network via VPN:
>
> 1. Logon local machine account first, then connect to VPN.
> 2. Logon domain account direct by dialling-up VPN.
>
> The DNS/WINS settings of your machine at home (or elsewhere outside) will
> tie in with your primary network adapter, and not your VPN PPP adapter
(even
> when there are settings assigned). Given such you can't resolve and locate
> hosts within your office network. Everything will be resolved by your
local
> or ISP DNS/WINS servers.
>
> How does one overcome this problem? Also, how can one allow NBT broadcast
to
> get beyond the RRAS server?
>
>
> Aaron
>
>
>
- Previous message: Bill Grant: "Re: VPN Settup"
- In reply to: Aaron Seet: "Resolving hostnames in remote VPN network"
- Next in thread: Aaron Seet: "Re: Resolving hostnames in remote VPN network"
- Reply: Aaron Seet: "Re: Resolving hostnames in remote VPN network"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|