Re: [VPN] Cannot find domain controller

["Chad Osmond" <[EMAIL PROTECTED]>]

LMHosts?

 

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.

 

eg. \\192.168.12.2\data

 

HTH

Chad

 

----- Original Message -----

From: Russell Sakne

To: [EMAIL PROTECTED]

Sent: Thursday, April 10, 2003 12:23 PM

Subject: [VPN] Cannot find domain controller

Hi all, I hope you can help.

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.

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...).

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.

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?

Hopefully yours
RussellS



************************************************************************************
This email and any attachments are meant only for the person or entity
intended. If you have received it in error please notify the sender and
delete.
Any information expressed is not necessarily the position of the Society.
************************************************************************************