<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2722.900" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>LMHosts?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Give it a try, usually works wonders for me. Aside
from that, I'm not sure what to suggest, If you're on 2K/XP machines you can
attempt to browse the shares by IP address, rule out any of the naming
gremlins.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>eg. <A
href="file://\\192.168.12.2\data">\\192.168.12.2\data</A></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>HTH</FONT></DIV>
<DIV><FONT face=Arial size=2>Chad</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=russak@bps.org.uk href="mailto:russak@bps.org.uk">Russell Sakne</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=vpn@lists.shmoo.com
href="mailto:vpn@lists.shmoo.com">vpn@lists.shmoo.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, April 10, 2003 12:23
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [VPN] Cannot find domain
controller</DIV>
<DIV><BR></DIV><BR><FONT face=sans-serif size=2>Hi all, I hope you can
help.</FONT> <BR><BR><FONT face=sans-serif size=2>Having followed the advice
of the very helpful people on this list, we had our remote site with its
PIX-to-PIX VPN working fine, using WINS to find network resources here at home
base. Then "something happened" and the remote machines can no longer find any
domain controllers for our domain. They can connect to other servers
(including our Terminal Serivces machine and our web proxy), but the primary
machines they *need* to connect to are a PDC and a BDC and they can't see them
at all. Weirdly, a "find" on the other BDC *does* get a result, which suggests
they should be able to approach that machine for authentication.</FONT>
<BR><BR><FONT face=sans-serif size=2>I've checked their DNS settings haven't
changed, and "ping" tests resolve the correct IP addresses (though we've never
been able to get an ICMP packet through either PIX in any circumstances...).
</FONT><BR><BR><FONT face=sans-serif size=2>We wondered if the machine
accounts downthere had somehow managed to expire, so have deleted them from
the Domain and then both attempted to created them at a workstation
rename-rejoin and manually to allow the workstation to reconect as that name,
to no avail.</FONT> <BR><BR><FONT face=sans-serif size=2>Can anyone offer any
clues or informed speculation as to what might have gone wrong? We're
wondering about the nature of an NT4 "Where's a DC" call. Is there some
setting on the VPN that would refuse passage to such a multicast-thing which
we may have inadvertently set?</FONT> <BR><BR><FONT face=sans-serif
size=2>Hopefully yours</FONT> <BR><FONT face=sans-serif size=2>RussellS</FONT>
<BR><BR><CODE><FONT
size=3><BR><BR>************************************************************************************<BR>This
email and any attachments are meant only for the person or entity<BR>intended.
If you have received it in error please notify the sender
and<BR>delete.<BR>Any information expressed is not necessarily the position of
the
Society.<BR>************************************************************************************<BR></BLOCKQUOTE></FONT></CODE></BODY></HTML>