Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 20188 Source: RemoteAccess
The user <username>, attempting to connect on com2, was disconnected because of the following reason: A Remote Access Client attempted to connect over a port that was reserved for Routers only.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "This behavior occurs because the server's RAS port is not configured to accept remote access connections". See ME262357 for more details.
I have found that contrary to the option 2 workaround defined in ME253145, the problem can be fixed by setting the L2TP and PPTP port settings to permit only inbound remote access. Open routing and remote access -> Right mouse click on ports -> Select properties from the list box -> Click on WAN miniport(PPTP) properties -> Click the configure button -> Place a check on the remote access connections(inbound only) -> Uncheck the remote access connections(inbound and outbound) -> Apply the change -> Then follow the same steps to change the L2TP miniport.
For dial-in, check that the dial-in port you're using is configured for demand-dial routing instead of inbound dial. Can be found in RRAS MMC. Check properties on ports and the configuration for the dial-in port. Make sure demand-dial is deselected, and inbound connections is selected.
This can also occur when the computer has ICS (Internet Connection Sharing) enabled, trying to RAS in, apparently RAS must be INDIVIDUALLY configured for each dialin account to get around this error. See the link to ME253145 below.
|Private comment: Subscribers only. See example of private comment|
|Links: ME262357, ME253145|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated