Re: 2 site's - vpn link - Slow local browsing
- From: "Bill Grant" <not.available@online>
- Date: Tue, 4 Oct 2005 09:00:57 +1000
Yes, you need WINS. Browsing uses Netbios names and LAN broadcasts. The
only effective way to get in working in a WAN or a routed network is with
WINS. Without WINS there is no way that the Domain Master Browser can find
the master browser in the other segment to build a network-wide browse list.
You can use one WINS server for the combined network. If you set up a
WINS server at each site, make sure that they replicate.
Perry Perdijk wrote:
>> Does name resolution occur the same way at both sites? do both sites
>> have wins and dns servers with the same info or are you broadcasting
>> requests across the subnets for name resolution?
>
> Do i need wins on the servers?
> I have dnsservers running on both domaincontrollers. On the prim.
> domaincontroller and secondary dns on the sec.domaincontroller.
> Dns seem to be working fine on both site's.
>
>> Are you using the domain controllers as VPN Servers? How many network
>> cards do they have installed? What IP addresses for the Domain
>> Controllers appear in Wins / DNS
>
> I do run the domaincontrollers as vpnservers. They both have 2 nic's
> installed, on internal (192.168.x.x) and 1 external (10.0.0.137).
> Both servers got isa2000 installed.
> Both dnsservers are listening on only the internal ipadres.
>
> Thx for your help so far...
>
> Main question about your comment, do i need to install winsservers
> for this type of configuration?
>
> Thx
> perry
>
> "Ian" <gruntyonline@xxxxxxxxxxx> schreef in bericht
> news:%23Vc2WlByFHA.664@xxxxxxxxxxxxxxxxxxxxxxx
>> Perry Perdijk wrote:
>>> Hi There,
>>>
>>> I got 1 domain , 2 servers , the servers are configured with
>>> isaserver 2000. The servers are connected over a vpn link.. The
>>> prim.domain controller(192.168.0.0) is on 1 site of the link.
>>> Secondary controller(192.168.1.1) on the other site.
>>>
>>> The problem is on the internal network on the remote location.
>>> when the clients connect to a share wich is on the local server(
>>> the network of the remote site) it is very slow.
>>> At first I thought i had to do with the browser service , but also
>>> when I connect to the server with " 192.168.1.1\share" sometimes
>>> it takes about 30 seconds for the share to open. But when i
>>> connect from the remote site to a share located on the mainserver
>>> with " servername\share " the share does open very quicly .. And
>>> that one goes over the vpn link. Dns on both sites of the link is
>>> working properly.
>>>
>>> Anyone has an idea what is going wrong ?
>>>
>>> thx
>>> perry
>>>
>>>
>> Does name resolution occur the same way at both sites? do both sites
>> have wins and dns servers with the same info or are you broadcasting
>> requests across the subnets for name resolution?
>>
>> If you are relying on broadcast for 1 site then this could be the
>> issue.
>>
>> or
>>
>> Are you using the domain controllers as VPN Servers? How many network
>> cards do they have installed? What IP addresses for the Domain
>> Controllers appear in Wins / DNS
>>
>>
>> Ian
.
- References:
- Re: 2 site's - vpn link - Slow local browsing
- From: Perry Perdijk
- Re: 2 site's - vpn link - Slow local browsing
- Prev by Date: Re: Workgroup issue
- Next by Date: Block file copy
- Previous by thread: Re: 2 site's - vpn link - Slow local browsing
- Next by thread: Re: 2 site's - vpn link - Slow local browsing
- Index(es):
Relevant Pages
|
Loading