Archived from groups: microsoft.public.windowsnt.domain (More info?)
Hi,
we replaced a isdn "fixed line" connection beetween
two location with a DSL VPN connection.
We never had problems with the isdn connection.
PDC is located in A, BDC is located in B.
The direction A (PDC) to B (BDC) works fine.
But I have problems with the direction B (BDC)
to A (PDC).
I can reproduce the problem with the command
net view \\PDC from the BDC
If I have short ping times from BDC to PDC
the command works fine but if the ping
times are longer (mostly case) I get the
error: "The remote procedure call failed"
Is there any value I can change to get
more "tolerance" from BDC to PDC
in cases of more traffic on the VPN?
Or do I have another problem?
Thanks for any idea!
Otto
Hi,
we replaced a isdn "fixed line" connection beetween
two location with a DSL VPN connection.
We never had problems with the isdn connection.
PDC is located in A, BDC is located in B.
The direction A (PDC) to B (BDC) works fine.
But I have problems with the direction B (BDC)
to A (PDC).
I can reproduce the problem with the command
net view \\PDC from the BDC
If I have short ping times from BDC to PDC
the command works fine but if the ping
times are longer (mostly case) I get the
error: "The remote procedure call failed"
Is there any value I can change to get
more "tolerance" from BDC to PDC
in cases of more traffic on the VPN?
Or do I have another problem?
Thanks for any idea!
Otto