Fix for RRAS Routing and Remote Access Error

August 9, 2010 at 11:02:22
Specs: Windows XP
Many have sought assistance in several forums related to their inability to establish a Windows XP incoming connection due to Routing and Remote Access Service errors, including those having Error 1003 and Event ID 7024.

The well-intended "guidance" I had found, including from Microsoft online resources, were of little value.

The Fix: Copying the two files, ias.mdb and dnary.mdb, from a working source, usually found in the windows\system32\IAS directory, from a machine that is able to establish an incoming connection, can eliminate this problem.

Proper setup of TCP/IP and NW Link IPX/SPX/NetBios services, including installation of these protocols if needed, and also including specifying appropriate network IP addresses, proper and appropriate port forwarding, as required, and unchecking the box "Use default gateway on remote network" under the Advanced TCP/IP settings' "General" tab, can assist you to set up your VPN successfully and save you from hours - or days - of frustration and anguish.

Best of Luck and thanks to all those who tirelessly and generously share their expertise and experience.

See More: Fix for RRAS Routing and Remote Access Error

Report •

August 9, 2010 at 12:59:47
There is no reason to install these nor would I recommend having them on a server;

NW Link IPX/SPX protocol
NetBios protocol

Report •

August 9, 2010 at 14:25:51
The essential or critical point in the original message relates to the IAS databases.

The statement that followed the main matter, "Proper setup of TCP/IP and NW Link IPX/SPX/NetBios services, including installation of these protocols if needed...", contained the clear qualification "if needed".

The statement is ancillary to the "fix" - and is essentially an addendum, which, in a proper case, may prove useful to some, especially to those who, for whatever reason, may decide or need to have these additional protocols installed and functional.

In addition, the presence of a given protocol on the client which is not present on the server may result in a warning message, one that presents the option to continue to establish the connection using the protocol that *is* available on the server or to "hang up".

Should this event occur, it could become a later and further point of confusion and misery and the solution to its avoidance or cure is to have the protocol, if needed, operational on the server or, alternatively, to eliminate it from the client when seeking to connect.

The original message sought to anticipate this event.

With Best Wishes.

Report •

Related Solutions

Ask Question