Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 20050 Source: RemoteAccess

The user <user name> connected to port <com port> has been disconnected because no network protocols were successfully negotiatated.
The connection automatically chooses a network adapter when installed. Choose one in the properties page for the connection.
I encountered this problem after I Installed VMware. VMware installed its own network adapters and the Routing and Remote Access service was set to randomly pick a LAN interface to use at startup (on the Network Selection page, "Allow RAS to select Adapter" was selected). Changing the adapter from "Allow RAS to select Adapter" to "Local Area Connection" (the connection that RAS should use) helped me to overcome this problem.
If you are using a MultiTech MT2834 modem, then see ME128976.
Check if RRAS has IP Addresses available from its DHCP server.
See ME181380 and ME233048 for details.

Sometimes the problem can be that the DHCP is trying to give to a remote access client an IP address that is currently in use. This causes a conflict.
In order to fix the problem I changed the adapter on the IP tab located in the server properties in Routing and Remote Access Manager. This worked in my case.
From newsgroups posts, the link below proved to be the fix for this problem.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.