2 site's - vpn link - Slow local browsing

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

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

> 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" <(E-Mail Removed)> schreef in bericht
news:%(E-Mail Removed)...
> 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

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" <(E-Mail Removed)> schreef in bericht
> news:%(E-Mail Removed)...
>> 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

Perry,
I don’t think it's a master browser or wins problem.
Could be that it is getting the ACLs from your server over the VPN.
Do you have a site link between them?

"Bill Grant" wrote:

> 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" <(E-Mail Removed)> schreef in bericht
> > news:%(E-Mail Removed)...
> >> 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
>
>
>

Hi There,

I dont know exaclty if I have a site link .I thougth windows did that
automaticly.
If i look in AD sites en services I see " default first sitename" under
that i see the 2 servers .
If i look in " inter-site-transport" then under "IP" I see
"defaultfirstsitelink"
If i look in "subnet's" There is nothing there.

I'm not a sitelink expert so any idea's are more then welcome.

Thx
perry


thx
perry
"Wendel Hamilton" <(E-Mail Removed)> schreef in
bericht news:5FC676BF-C6E1-442A-96FC-(E-Mail Removed)...
> Perry,
> I don't think it's a master browser or wins problem.
> Could be that it is getting the ACLs from your server over the VPN.
> Do you have a site link between them?
>
> "Bill Grant" wrote:
>
> > 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" <(E-Mail Removed)> schreef in bericht
> > > news:%(E-Mail Removed)...
> > >> 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
> >
> >
> >

Perry,
You need to at least tell it you have 2 sites and the associated IP address
range.
Here is some Light reading Ha Ha
http://www.microsoft.com/technet/pro...25cf30e0e.mspx

"Perry Perdijk" wrote:

> Hi There,
>
> I dont know exaclty if I have a site link .I thougth windows did that
> automaticly.
> If i look in AD sites en services I see " default first sitename" under
> that i see the 2 servers .
> If i look in " inter-site-transport" then under "IP" I see
> "defaultfirstsitelink"
> If i look in "subnet's" There is nothing there.
>
> I'm not a sitelink expert so any idea's are more then welcome.
>
> Thx
> perry
>
>
> thx
> perry
> "Wendel Hamilton" <(E-Mail Removed)> schreef in
> bericht news:5FC676BF-C6E1-442A-96FC-(E-Mail Removed)...
> > Perry,
> > I don't think it's a master browser or wins problem.
> > Could be that it is getting the ACLs from your server over the VPN.
> > Do you have a site link between them?
> >
> > "Bill Grant" wrote:
> >
> > > 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" <(E-Mail Removed)> schreef in bericht
> > > > news:%(E-Mail Removed)...
> > > >> 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
> > >
> > >
> > >
>
>
>

Hi Wendel,

Two sites assigned to two different subnets would certainly be an
improvement! But I don't think it would solve the slow browsing. If a share
in the "other" site opens faster than a local one, I agree with Ian that it
is probably a master browser problem. I looks like there is not a
network-wide browse list. The other alternative would be to use Dfs.

And there is still the worry of DCs as routers.

Wendel Hamilton wrote:
> Perry,
> You need to at least tell it you have 2 sites and the associated IP
> address range.
> Here is some Light reading Ha Ha.
> http://www.microsoft.com/technet/pro...25cf30e0e.mspx
>
> "Perry Perdijk" wrote:
>
>> Hi There,
>>
>> I dont know exaclty if I have a site link .I thougth windows did that
>> automaticly.
>> If i look in AD sites en services I see " default first sitename"
>> under that i see the 2 servers .
>> If i look in " inter-site-transport" then under "IP" I see
>> "defaultfirstsitelink"
>> If i look in "subnet's" There is nothing there.
>>
>> I'm not a sitelink expert so any idea's are more then welcome.
>>
>> Thx
>> perry
>>
>>
>> thx
>> perry
>> "Wendel Hamilton" <(E-Mail Removed)> schreef
>> in bericht news:5FC676BF-C6E1-442A-96FC-(E-Mail Removed)...
>>> Perry,
>>> I don't think it's a master browser or wins problem.
>>> Could be that it is getting the ACLs from your server over the VPN.
>>> Do you have a site link between them?
>>>
>>> "Bill Grant" wrote:
>>>
>>>> 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" <(E-Mail Removed)> schreef in bericht
>>>>> news:%(E-Mail Removed)...
>>>>>> 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

Normally I would agree but he can’t connect to shares using the IP address of
the server and thus the master browser should be bypassed.
My reasoning that the remote server opens shares quickly as it is looking up
the ACLs on its local network where the remote server is probably connecting
through the VPN to get the ACLs from the other server.
It was only a suggestion.
He should defiantly set up WINS correctly or configure all his computers to
use DNS and remove NetBIOS over TCPIP. Any way I hope one of us can resolve
his issue.

"Bill Grant" wrote:

> Hi Wendel,
>
> Two sites assigned to two different subnets would certainly be an
> improvement! But I don't think it would solve the slow browsing. If a share
> in the "other" site opens faster than a local one, I agree with Ian that it
> is probably a master browser problem. I looks like there is not a
> network-wide browse list. The other alternative would be to use Dfs.
>
> And there is still the worry of DCs as routers.
>
> Wendel Hamilton wrote:
> > Perry,
> > You need to at least tell it you have 2 sites and the associated IP
> > address range.
> > Here is some Light reading Ha Ha.
> > http://www.microsoft.com/technet/pro...25cf30e0e.mspx
> >
> > "Perry Perdijk" wrote:
> >
> >> Hi There,
> >>
> >> I dont know exaclty if I have a site link .I thougth windows did that
> >> automaticly.
> >> If i look in AD sites en services I see " default first sitename"
> >> under that i see the 2 servers .
> >> If i look in " inter-site-transport" then under "IP" I see
> >> "defaultfirstsitelink"
> >> If i look in "subnet's" There is nothing there.
> >>
> >> I'm not a sitelink expert so any idea's are more then welcome.
> >>
> >> Thx
> >> perry
> >>
> >>
> >> thx
> >> perry
> >> "Wendel Hamilton" <(E-Mail Removed)> schreef
> >> in bericht news:5FC676BF-C6E1-442A-96FC-(E-Mail Removed)...
> >>> Perry,
> >>> I don't think it's a master browser or wins problem.
> >>> Could be that it is getting the ACLs from your server over the VPN.
> >>> Do you have a site link between them?
> >>>
> >>> "Bill Grant" wrote:
> >>>
> >>>> 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" <(E-Mail Removed)> schreef in bericht
> >>>>> news:%(E-Mail Removed)...
> >>>>>> 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
>
>
>

Wendel Hamilton wrote:
> Normally I would agree but he can’t connect to shares using the IP address of
> the server and thus the master browser should be bypassed.
> My reasoning that the remote server opens shares quickly as it is looking up
> the ACLs on its local network where the remote server is probably connecting
> through the VPN to get the ACLs from the other server.
> It was only a suggestion.
> He should defiantly set up WINS correctly or configure all his computers to
> use DNS and remove NetBIOS over TCPIP. Any way I hope one of us can resolve
> his issue.
>
> "Bill Grant" wrote:
>
>
>> Hi Wendel,
>>
>> Two sites assigned to two different subnets would certainly be an
>>improvement! But I don't think it would solve the slow browsing. If a share
>>in the "other" site opens faster than a local one, I agree with Ian that it
>>is probably a master browser problem. I looks like there is not a
>>network-wide browse list. The other alternative would be to use Dfs.
>>
>> And there is still the worry of DCs as routers.
>>
>>Wendel Hamilton wrote:
>>
>>>Perry,
>>>You need to at least tell it you have 2 sites and the associated IP
>>>address range.
>>>Here is some Light reading Ha Ha.
>>>http://www.microsoft.com/technet/pro...25cf30e0e.mspx
>>>
>>>"Perry Perdijk" wrote:
>>>
>>>
>>>>Hi There,
>>>>
>>>>I dont know exaclty if I have a site link .I thougth windows did that
>>>>automaticly.
>>>>If i look in AD sites en services I see " default first sitename"
>>>>under that i see the 2 servers .
>>>>If i look in " inter-site-transport" then under "IP" I see
>>>>"defaultfirstsitelink"
>>>>If i look in "subnet's" There is nothing there.
>>>>
>>>>I'm not a sitelink expert so any idea's are more then welcome.
>>>>
>>>>Thx
>>>>perry
>>>>
>>>>
>>>>thx
>>>>perry
>>>>"Wendel Hamilton" <(E-Mail Removed)> schreef
>>>>in bericht news:5FC676BF-C6E1-442A-96FC-(E-Mail Removed)...
>>>>
>>>>>Perry,
>>>>>I don't think it's a master browser or wins problem.
>>>>>Could be that it is getting the ACLs from your server over the VPN.
>>>>>Do you have a site link between them?
>>>>>
>>>>>"Bill Grant" wrote:
>>>>>
>>>>>
>>>>>> 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" <(E-Mail Removed)> schreef in bericht
>>>>>>>news:%(E-Mail Removed) ...
>>>>>>>
>>>>>>>>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
>>
>>
>>
Sorry for my absence - I always forget to check my posts outside of the
..general board!!

Think we have all raised valid points

* Sites, Site Links and subnets need to be configured so that
workstations have the ability to figure our which DC they should be using!

* Wins needs to be setup for netbios to be able to work properly (Even
if you are accessing the resource via IP!!)

I'm pretty sure that the OP's problems will disappear when this has been
completed.

I