I think that "Bill Grant" may have been referring to using the dial up
connection option to connect to the VPN (not a modem).
The connection is made to the hostname or IP address of the VPN server,
not a telephone number.
For this to work, the VPN connection has to be set up on the user's end
to be available for all users, as it needs to be available _before_ they
log in, so they can log in via that connection.
This may not work if your VPN server is not set up for this (some/many?
non-MS products, for example). If they are using some VPN client program
that is loaded after they log in, this won't work, either.
It also sounds like you were having them log in using cached credentials.
They have to log in successfully at least once to the domain when it is
"available", to generate credentials that can be cached. When they were
disjoined, that probably removed the cached credentials that they had
before.
=?Utf-8?B?QWxsaWU=?= <(E-Mail Removed)> wrote in
news:698CC88D-36EC-4E8B-83BF-(E-Mail Removed):
> Thanks for the quick response but the dial up trial did not work...
> My remote client in England was able to dial up and connect but then
> would get errors saying that the domain controller could not be found.
> My second remote user is using a laptop that does not have a modem...
> Do you have any other suggestions?
>
>
> "Bill Grant" wrote:
>
>> On the client machine there is an option in the login dialog box
>> to log
>> in using a dialup connection. If you use that option (rather than
>> doing a local login) and use the domain username and password (eg
>> (E-Mail Removed)) the client should do a domain login.
>>
>> "Allie" <(E-Mail Removed)> wrote in message
>> news:4CD531CE-17DA-48EC-8BC4-(E-Mail Removed)...
>> >I have two remote users that were disjoined from the domain (their
>> >mistake).
>> > I have deleted their accounts from the DC and have logged in as the
>> > local administrator and have been successful in adding them to the
>> > domain (while connected via VPN). The problem starts when I have
>> > to reboot the machine. At that point, when they try to log in with
>> > their domain accounts, they get
>> > the error: "The system cannot log you on now because the domain
>> > XXXXX is not
>> > available".
>> > I have been able to recreate the problem by using a laptop
>> > connected to a DSL line (external to the domain), using the same
>> > VPN connection as my external users with the same result (error:
>> > "The system cannot log you on now
>> > because the domain XXXXX is not available"). The only way I could
>> > get my laptop back on the domain was to plug it back onto the
>> > network. Is there a way to accomplish the same result (so my remote
>> > users can log in
>> > with their network credentials) without having them return their
>> > computers to
>> > me so that I can physically plug their laptops on th a network
>> > jack? Please
>> > help...
>>
>>
>>
>
Similar Threads
Linear Mode
