C
Chuck
In October 2002 we converted to Active Directory in a
multiple AD environment. We currently have three DC's on
three subnets and the same domain.
Since converting we have had constant problems while
connected to our intranet from DSL connections to a VPN
server and trying to map network shared folders.
Occasionally there are successful mappings but always
after 5-20 minutes of machine frozen time. The successful
mapping will occur or the following error message will be
presented after the machine hang time:
"The mapped network drive could not be created because the
following error has occurred: There are currently no logon
servers available to service the logon request."
The problem seems confined to when the initial
authentication is to a local cashed profile and the share
is on an "aliased" W2K Advanced server. NT Server shares
(unaliased) don't seem to be experiencing the same trouble.
Further exasperating the issue is clients that are closest
to a remote segment of our domain do not seem to
experience this issue as often.
multiple AD environment. We currently have three DC's on
three subnets and the same domain.
Since converting we have had constant problems while
connected to our intranet from DSL connections to a VPN
server and trying to map network shared folders.
Occasionally there are successful mappings but always
after 5-20 minutes of machine frozen time. The successful
mapping will occur or the following error message will be
presented after the machine hang time:
"The mapped network drive could not be created because the
following error has occurred: There are currently no logon
servers available to service the logon request."
The problem seems confined to when the initial
authentication is to a local cashed profile and the share
is on an "aliased" W2K Advanced server. NT Server shares
(unaliased) don't seem to be experiencing the same trouble.
Further exasperating the issue is clients that are closest
to a remote segment of our domain do not seem to
experience this issue as often.