Question Locked

Connectivity Issues after Installing RRAS Win2k3

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The symptoms:

After installing RRAS on a windows 2003 server connectivity will "come and go" one moment I can ping the machine, the next i can't. Or another machine can ping but another can't. This appears to be for both in and outbound connections from the RRAS machine.

When trying to vpn, sometimes you will instantly connect. Other times it will hang at Verifying Username and Password. Oddly enough, once you are connected and in the vpn works flawlessly.

I have installed RRAS on 3 servers each with different hardware.

Last example, I will remote desktop into the machine from my desk. The connection will reach the machine and show me the desktop but then when I type in the login credentials, occasionally the machine will come back with an error that it could not reach the domain controller.

Any help will be greatly appreciated as we are about to ditch RRAS and go with a vpn appliance if this keeps up.

2 replies

by Former member

Hi eventlogmail,
I have included some info here.
I hope this helps you.

Amateurs: Do not realise that RAS is installed by default

The fact that Routing and Remote Access is installed by default is an indication of its improved reliability. While RRAS is installed on Server 2003 and Windows 2000 server, you still need to configure the settings. There may be times when you need to connect two subnets, RRAS can be your static router. Once you have run the wizard once, you can right click the server object and configure the properties.

See much more on RRAS here

?
Routing and Remote RAS

Group policies are every where in Windows Server 2003 and Windows 2000; they even extend to dial-up connections. Use the power of the Group Policy to control users' settings when ever they logon. One of the main benefits of switching the domain from mixed to native mode is that you can use group policies when users dial-in.
My Goal - To get you started with RRAS policies

1.

Go to Start \ Programs \Administrative Tools \ Routing and Remote Access
2.

Add Server (Local Computer)
3.

Run the Wizard (Start with the VPN option if you want to practice)
4.

Look for REMOTE ACCESS POLICIES (Start \Help if you are stuck)

N.B. The default RRAS Policy is to Deny users access. This a failsafe mechanism so that no-one can access the RAS server until the administrator has configured the server (or knows what they are doing!).

N.B. To get the most out of your RRAS Policy and Profiles, your domain needs to be in NATIVE mode.

Each Policy has a PROFILE tab this is where you configure how long users can connect to the server, which protocols they use and much more besides.
The Routing side of RRAS

Windows 2000 or Server 2003 servers can act as a software router. Naturally you need at least two network cards. Check out the Routing by going to RRAS \ \IP Routing \General and then right click and add the Interface or Routing protocol that you need.

This RRAS console has menus with sub menus so there are many features to evaluate e.g. OSPF, L2TP, NAT.
RAS and DHCP Relay Agent

The Relay Agent is now found inside the \IP Routing \General tab of RRAS, if you are going to set up RRAS you either need to configure a separate scope of IP addresses or else use a DHCP Relay Agent to point to the real DHCP server.

This discussion is closed to new replies.