10 replies
by jefrow Accepted solution
by snuffy09 Accepted solution
did you re-add it to the domain?
can you ping the Domain controller?
could be a small chance the users password has expired and needs reset
by jefrow Accepted solution
Thank you for the suggestions!
yes, re-added, can ping dc, don't think it is expired, because I can log in remotely.
Here's what the computer is set up to do. It has a batch file that runs upon login. Normally, The batch file connects to the ras via vpn, then runs the remote desktop session. It seems like it won't run the batch file or maybe won't vpn, but I can login as admin and run all this and connect, but the user needs it to be automated again.
Ahhhh. I have been pulling out my hair on this for days! Hopefully the details will help here. p.s. I can give event log errors too if that helps. Thanks Again.
by ic-it Accepted solution
by kenone Accepted solution
by jefrow Accepted solution
by nexs Accepted solution
As I am not sure what the situation is.
Is this PC plugged into a LAN which cannot see the Domain Controller? You speak about running scripts to connect to a VPN, so I am unsure as to which Domain Controller cannot be connected to.
On a blind fumble, you may want to remove the PC from the domain and try to re-add it.
edited:
P.S. you could also remove the machine from Active Directory and try to set it up in there from scratch as well.
by jefrow Accepted solution
by jefrow Accepted solution
by cg it Accepted solution
the remote desktop security settings.
probably have to go through RRAS and verify those settings, then verify the remote desktop settings to ensure the user has the appropriate permissions and rights to first establish a VPN connection, then login for a remote desktop session.
However, the initial error messages seems to point to the client system rights to access the netlogon share or the inability to find a domain controller to authenticate with.
A no domain controller was found to authenticate with means DNS queries for a DC went unanswered. That can be a DNS issue where the DNS servers contacted don't have any information on the domain name being queried. That could be an addressing problem. An addressing problem would be in RRAS with DHCP relay agent and subnet used for remote access clients.
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending