#431 closed Bug / Defect (notabug)
AD Login
| Reported by: | MuFi | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Generic / unclassified | Version: | OpenVPN 2.2.2 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: |
Description
After the start of openvpn client is not possible a user logs onto the windows domain more in the local network.
Error: There is currently no logon servers available to service the logon request process available.
Change History (2)
comment:1 Changed 10 years ago by
| Resolution: | → notabug |
|---|---|
| Status: | new → closed |
comment:2 Changed 10 years ago by
To be a bit verbose: depending on the openvpn config pushed from the server, access to the local network may be forbidden from then on, or the client might use different DNS servers that do not know the windows domain.
So, it's not a bug in OpenVPN, but a configuration that conflicts with local AD access.
Note: See
TracTickets for help on using
tickets.
This is not an OpenVPN issue, more likely a configuration, routing or firewall issue. Please seek help in the forums, mailing list or IRC.
http://community.openvpn.net/openvpn/wiki/GettingHelp