[ previous ] [ next ] [ threads ]
 From:  "Kristian Shaw" <monowall at wealdclose dot co dot uk>
 To:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall] M0n0wall to M0n0wall Ipsec tunnel does not connect
 Date:  Wed, 18 Oct 2006 20:07:26 +0100

Perhaps the other device was automatically forwarding NETBIOS broadcasts 
across the VPN link. If that was the case then I'm not surprised that 
browsing wasn't very reliable.

In my experience a WINS server is still necessary for anything other than a 
small network on one subnet. Whilst DNS takes care of the name resolution 
requirementss of Active Directory, the Network Neighbourhood still needs 
WINS to work quickly and reliably.


----- Original Message ----- 
From: "Cecil Strange" <cecil underscore strange at msn dot com>
To: <m0n0wall at lists dot m0n0 dot ch>
Sent: Wednesday, October 18, 2006 5:09 PM
Subject: RE: [m0n0wall] M0n0wall to M0n0wall Ipsec tunnel does not connect

Thanks for all the help.  Windows browsing works fine now
that WINS is installed.

As a novice who has managed three active directory domains
for five years, I've never had legacy workstations and
therefore never had to install WINS.  My last Ipsec tunnel
was between two Netgear FVS318 appliances.  I could browse
on that tunnel without WINS, but it was slow and not
terribly persistent.  M0n0wall, with a WRAP at one end and a
PC at the other, is much faster.  I guess I'll know about
reliability of the tunnel in a few days.

Thanks again.  I guess I owe the Wiki a page on this.

To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch