Ras Error 913
I have configured SBS Server 2k3 for remote access but can only connect using VPN after I run the Remote Access Wizard in the todo list from Server Management. The following day if i try to connect again I get a 913 error "A Remote Access Client attempted to connect over a port that was reserved for Routers only" and i can not resolve this until i run the wizard again, which fixes it. I presumed this was an issue with a group policy that was kicking in to deny remote access but after searching the policys i can not find anything suspect. Any ideas? Anyone had the same issue? I must be missing something simple here.. DaveM, Dec 15, 2005 #1 Advertisements Brandy Nee [MSFT] Guest Hello Dave, Thank you for posting to the SBS Newsgroup. I understand the issue to be: when you try to VPN from a Windows XP client, you get the following error: error913: A Remote Access Client attempted to connect over a port that was reserved for Routers only. Per my research, the behavior occurs because the server''s RAS port is not configured to accept remote access connections. RESOLUTION ========== To resolve this problem, use the following steps: 1. Start the Routing and Remote Access administrative tool. 2. Expand the options under your RAS server''s name. 3. Click Ports, and then click Properties on the Action menu. 4. Click the appropriate port (L2TP, Modem, PPTP, LPT1, and so on), and then click Configure. 5. Click to select the "Remote access connections (inbound only)" check box, and then click OK. 6. Click Apply, and then click OK. For more information, please see: 262357 RAS Clients Cannot Connect to Windows 2000 Demand-Dial Router http://support.microsoft.com/?id=262357 [Note]: This KB article also applies to SBS 2K3 Server. Hope this information helps! If you have any further questions or concerns on this issue, please feel free to let me know. I am glad to be of further assistance! Best regards, Brandy Nee Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ====================================================== This newsgroup only focuses on S
log of VPN server Error 619 Receiving RAS error 619 while connecting to a VPN via SBC VPN error 619 - Case Study Error 624 Error 628 Error 629 Error 630 - The port was disconnected due to hardware failure Error 633 Modem Is Already in Use Error 638: The request has timed out Error 645 Error 649 VPN Error 649 - The account does not have permission to dial-in - Case Study Error 650 Error 678 Error 682 Error 691 Error 711 Error http://www.winvistatips.com/threads/remote-access-switching-off-error-913.625788/ 720 Error 721 VPN Error 732: The PPP negotiation is not converging Error 733 Error 734 - The PPP link control protocol terminated. Error 735 - The requested address was rejected by server. Error 736 - The remote computer terminated the control protocol. Error 741 - The local computer does not support the required encryption type. Error 769 The specific destination is not reachable. Error http://www.chicagotech.net/raserrors.htm 792 - The L2TP Connection Attempt failed because security negotiation timed out. Error 797 Error 781 Error 783 Error 800 Error 806 - the VPN connection cannot be completed Error 913 Error 930 Error 937: Because another connection of your type is in use. Troubleshooting VPN/PPP problem by using the log of VPN server MS windows event viewer and log are very useful tools in troubleshooting VPN/PPP. If you have a difficulty to access the VPN/RAS server, you may go to the event viewer of the VPN/RAS server to check any errors. Alternatively, you can go to %SystemRoot%\system32\LogFiles to view any possible causes. To enable the PPP log on w2k server, go to Routing and Remote Access Services (RRAS)>properties>Event Logging, Check the Enable Point-to-Point Protocol (PPP) logging box. To enable PPP Logging on a Computer Running Windows 2000 Professional Using Netsh.exe. To do this, at command prompt, type netsh ras set tracing PPP enable NOTE: The Netsh.exe utility is the only option to enable PPP logging in Win 2000 Pro. After you enable logging, the computer logs all PPP activity to the xxx.log file in the %SystemRoot%\LogFiles. Since PPP logging uses syst
was reserved for Routers only) ★★★★★★★★★★★★★★★ Ori Yosefi - MSFTDecember 7, 20102 Share 0 0 Scenario When configuring site-to-site (S2S) VPN networks, you may notice that https://blogs.technet.microsoft.com/isablog/2010/12/07/tmg2010-site-to-site-vpn-fails-to-dial-with-error-913-a-remove-access-client-attempted-to-connect-over-a-port-that-was-reserved-for-routers-only/ the VPN tunnel doesn't connect. On the dialing TMG server, you'll see the following event logs: Log Name: Application Source: RasClient Event ID: 20227 Description: CoId={A56F6195-18BB-44ED-AE45-34B70D127A2C}: The user SYSTEM dialed a connection named Net2 http://www.windows-expert.net/faq/networking/ras-error-message-routers-only.php which has failed. The error code returned on failure is 913. Log Name: System Source: RemoteAccess Event ID: 20111 Description: A Demand Dial connection to the remote interface Net2 on port VPN2-4 was ras error successfully initiated but failed to complete successfully because of the following error: A Remote Access Client attempted to connect over a port that was reserved for Routers only. And on the other TMG server, you'll see this event log: Log Name: System Source: RemoteAccess Event ID: 20270 Description: CoID={31A76222-6269-4085-95E5-B3DAC64F69FD}: The user Net2, attempting to connect on VPN2-100, was disconnected because of the following reason: A Remote ras error 913 Access Client attempted to connect over a port that was reserved for Routers only. Solution In order to accept any VPN connections, you must enable VPN client access, even if you only expect site-to-site VPN connections. -Gabriel Koren, TMG product team Comments (2) Cancel reply Name * Email * Website Larry Green says: May 23, 2011 at 5:10 pm B.S. Sorry to be so crass. But this product about to send me over the deepend. S2S using TMG to TMG works without VPN client enabled. Will dial in. No such error. I have over 50 in the filed so I can attest to that. What does NOT work on S2S atter tunnel fails and reconnects you can no longer ping through from TMG to other TMG S2S…Use S2S same circuits and one device is TMG and the other ISA2006 and all works fine. Larry.Green@chsfl.org Reply dejf says: April 20, 2016 at 9:24 pm Well, nope. This error message seem to mean about a dozen of possible reasons. The other one I tried yet was issuing certificates for both sides and use those instead. And no, RRAS is still unable to dial while control panel inte
ports for routers. Source: Remote Access Event ID: 20188
The user xxx, attempting to connect on VPNx-y, was disconnected because of the following reason: A Remote Access Client attempted to connect over a port that was reserved for Routers only. Answer: It sounds like the ports are configured for demand-dial routing instead of inbound dial in services. In RRAS MMC check the properties on "ports", and check the configuration for whatever port type you're using. You usually want to deselect "demand-dial" and just check on "inbound connections". If that system is used both as a dial in server as well as a router, both settings must be checked. Home Articles FAQ Windows XP Seminars Online Forums Books Links Newsletter Archive Web Server Check Contact Us Search Printer Version Send this page to a friend Copyright © 1988-2005 Adiscon GmbH All rights reserved. Contact us via Secure Web Response|Privacy Policy Topic Links: syslog