Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Failures for RAS connections can be debugged using RAS logs.
- To enable RAS logs run command “netsh ras set tracing * enabled”
- Now run the scenario that is failing.
- Now flush the RAS logs by “netsh ras set tracing * disabled” command.
- Check the logs at %windir%tracing directory.
- Some of the files where you can look to debug the problem are –
- PPP.log
- RASMAN.log
- IASHLPR.log
- RASAPI32.log
- RASIPCP.log
- Also see the “Event viewer” and find the events created by “RemoteAccess” to troubleshoot the issue.
- Error code related to RRAS are listed at https://support.microsoft.com/kb/q163111/
- Help can also be searched at https://support.microsoft.com/default.aspx
Puja Pandey
Software Design Engineer/Test
Windows Networking Group
[This posting is provided "AS IS" with no warranties, and confers no rights.]
Comments
Anonymous
January 01, 2003
PingBack from http://www.hilpers.nl/495436-gebruiker-kan-niet-bij-fileserverAnonymous
January 01, 2003
PingBack from http://www.keyongtech.com/2496330-2000-nat-and-port-forwardingAnonymous
January 01, 2003
Check http://blogs.technet.com/rrasblog/archive/2005/12/22/416421.aspx for information to enable...