As Phillip said, the first thing to check is whether the Watchguard is
blocking any traffic across the link.
Whether you put a DC in the site or not is a different question. There
are advantages in having a DC in a site with AD. But if it worked OK on a
leased line, it should work OK with a VPN link. Has anything else changed?
Have you moved from a bridged connection to a routed one?
"Phillip Windell" <@.> wrote in message
news:%(E-Mail Removed)...
> Watchgaurd is kinda proprietary in the way they do things (we use one
> here).
> You might be better off contacting them.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> "Ed Walker" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hey guys, I need help with this as I am stumped.
>>
>> I have two locations that were previously connected via Frame Relay, we
> have
>> since moved to a IPSec site to site VPN solution using watchguard soho 6
> and
>> a firebox x2500 on the other side.
>>
>> we have the tunnel up and running, but have several problems:
>>
>> users cannot log into the network (the domain controllers are on the far
>> side <x2500>
>> users on the remote end are able to ping some of our resources on the far
>> side, they can ping and get a response frmo one of our two domain
>> controllers/dns server, but not hte other, nor can they connect to our
> main
>> server on the far side.
>>
>> I can remote desktop into the server on the remote end, and login but the
>> local users there cant login.
>>
>> any ideas?
>>
>> i am thinking they need a domain controller on the remote end and that
> this
>> may be a dns issue among other things?
>>
>> the setup sends only traffic destined for our private network over the
>> tunnel and internet traffic goes directly fmro their router andnot over
> the
>> tunnel
>>
>> thanks
>>
>>
>
>
Similar Threads
Linear Mode
