• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1845
  • Last Modified:

Routing and Remote Access Server not acting as a Router. Internal Interface is non-operational.

I am using windows 2003 server standerd
I am trying to set up a VPN Server. I want it to act as a router
It doe’s not function so. I believe the problem is. I open RRAS, Under IP Routing and under General. It list 4 Interfaces

1.Internet, 2. Network, 3. Loopback, 4 Internal.

the Internal interface is non-operational and doesn't have an IP Address, the others are working

If I look under Routing Interfaces and all 4 interfaces are connected.

I have tryed to reinstall RRAS but have had no luck.The 2 NIC have differant IP Address and subnets.
I have right clicked on the server name (local) under properties and enable this computer as a Router
and selected Lan and demand-dail routing.I have gone to the Registery and have enabled. IPEnableRouter and it is still non-operational. I have no other services runing on the server,Doe's it need an other services to run properly,I don't think it is hardware everything is working fine
How can I get the internal interface operational
0
jatzBona07
Asked:
jatzBona07
1 Solution
 
nickymoCommented:
Hi,

Start for scratch, see url below;

http://www.tacteam.net/isaserverorg/vpnkit/configisavpn.htm

:)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now