Re: Resolving hostnames in remote VPN network
From: Bill Grant (not.available_at_online)
Date: 02/26/04
- Previous message: Bill Grant: "Re: RAS'd in but not fully connected"
- In reply to: Aaron Seet: "Re: Resolving hostnames in remote VPN network"
- Next in thread: Bill Grant: "Re: Resolving hostnames in remote VPN network"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 12:09:05 +1000
Rather than a broadcast going through, it probably sent a name request to
your WINS server and got a reply. Requests to WINS servers are directed
requests, not broadcasts. They are not upset by routers or WAN links.
If your clients are configured as WINS clients, they should only try to
broadcast if the WINS request fails.
"Aaron Seet" <poster@news.microsoft.com> wrote in message
news:O0ntcw2#DHA.2524@TK2MSFTNGP10.phx.gbl...
> Missed out a word. It should've been
>
> "it appears the NBT broadcast did get through the VPN connection."
>
>
> "Aaron Seet" <poster@news.microsoft.com> wrote in message
> news:OY$Fbl0%23DHA.220@TK2MSFTNGP09.phx.gbl...
>
> it appears the NBT broadcast did get the VPN connection.
>
>
- Previous message: Bill Grant: "Re: RAS'd in but not fully connected"
- In reply to: Aaron Seet: "Re: Resolving hostnames in remote VPN network"
- Next in thread: Bill Grant: "Re: Resolving hostnames in remote VPN network"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|