VPN need WINS?

Easy question: does ms-vpn need wins to work completely? I can get to
servers via IP address but not via Names. Would wins fix this? I currently
have DHCP and DNS on the server but not WINS. Thanks.

In news:OnqY%(E-Mail Removed),
dtm <(E-Mail Removed)-nospam> stated, which I commented on below:
> Easy question: does ms-vpn need wins to work completely? I can get to
> servers via IP address but not via Names. Would wins fix this? I
> currently have DHCP and DNS on the server but not WINS. Thanks.

Yep. WINS offers the ability to connect using NetBIOS names (single name)
across subnets. Just install WINS and have all machines set to use it in
their properties either manually or automatically thru DHCP. If you want to
use DHCP, add these DHCP Options:

044 - WINS Server IP
046 - 0x8

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Assimilation Imminent. Resistance is Futile
Infinite Diversities in Infinite Combinations

"Very funny Scotty. Now, beam down my clothes."

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy.

DNS would do it for you, as long as the client has the correct DNS
address and the correct DNS suffix. A wrong (or no) suffix specified on the
client is the usual cause of problems like that. WINS will work as long as
the servers you want to find are WINS clients (so that they actually
register with WINS).

Make sure that the RRAS server has the correct WINS and DNS addresses.
The remote client gets its WINS and DNS addresses from the RRAS server as
part of the PPP negotiation to set up the connection.

Ace Fekay [MVP] wrote:
> In news:OnqY%(E-Mail Removed),
> dtm <(E-Mail Removed)-nospam> stated, which I commented on
> below:
>> Easy question: does ms-vpn need wins to work completely? I can get to
>> servers via IP address but not via Names. Would wins fix this? I
>> currently have DHCP and DNS on the server but not WINS. Thanks.
>
> Yep. WINS offers the ability to connect using NetBIOS names (single
> name) across subnets. Just install WINS and have all machines set to
> use it in their properties either manually or automatically thru
> DHCP. If you want to use DHCP, add these DHCP Options:
>
> 044 - WINS Server IP
> 046 - 0x8

In news:(E-Mail Removed),
Bill Grant <not.available@online> stated, which I commented on below:
> DNS would do it for you, as long as the client has the correct DNS
> address and the correct DNS suffix. A wrong (or no) suffix specified
> on the client is the usual cause of problems like that. WINS will
> work as long as the servers you want to find are WINS clients (so
> that they actually register with WINS).
>
> Make sure that the RRAS server has the correct WINS and DNS
> addresses. The remote client gets its WINS and DNS addresses from the
> RRAS server as part of the PPP negotiation to set up the connection.

Good point, Bill. I guess DNS would be fine and the search suffix will be
used to resolve single name requests, but using WINS will also give the
users the ability to use Network Neighborhood for browsing, along with
printer browsing, if printers are not published in AD.

Ace

Indeed. I would use WINS myself. Some people seem very reluctant to use
it though (especially those who haven't used NT in the past).

Ace Fekay [MVP] wrote:
> In news:(E-Mail Removed),
> Bill Grant <not.available@online> stated, which I commented on below:
>> DNS would do it for you, as long as the client has the correct DNS
>> address and the correct DNS suffix. A wrong (or no) suffix specified
>> on the client is the usual cause of problems like that. WINS will
>> work as long as the servers you want to find are WINS clients (so
>> that they actually register with WINS).
>>
>> Make sure that the RRAS server has the correct WINS and DNS
>> addresses. The remote client gets its WINS and DNS addresses from the
>> RRAS server as part of the PPP negotiation to set up the connection.
>
> Good point, Bill. I guess DNS would be fine and the search suffix
> will be used to resolve single name requests, but using WINS will
> also give the users the ability to use Network Neighborhood for
> browsing, along with printer browsing, if printers are not published
> in AD.
> Ace

In news:%23$(E-Mail Removed),
Bill Grant <not.available@online> stated, which I commented on below:
> Indeed. I would use WINS myself. Some people seem very reluctant
> to use it though (especially those who haven't used NT in the past).

I agree with you, that's true. I think part of it might also be the lack of
understanding what it does. But for anyone else reading this, it's a pretty
simple tool to allow NetBIOS name resolution across subnets which also wakes
up network browsing across subnets as well.

I hope it helps others out there.

Ace