INTERNAL INTERFACE

[Frank]

In my RAS Server, under IP routing and general there is a
internal interface. For some reason that is saying
unavailable and can't figure out why. I'm assuming that
is why nobody can access the VPN. They are getting to
verifying username and password and then the server has
stopped responding error

 

[Rick]

-----Original Message-----
In my RAS Server, under IP routing and general there is a
internal interface. For some reason that is saying
unavailable and can't figure out why. I'm assuming that
is why nobody can access the VPN. They are getting to
verifying username and password and then the server has
stopped responding error
.

When you find a way to fix your problem let me know. I am
having the same exact problem.

Rick

 

[Marc Reynolds [MSFT]]

Hi,

This interface is part of RRAS and represents all Remote Access Services
(RAS) devices. All RAS clients are part of this interface. You should NOT
delete or try to reconfigure this interface. It should not interfere with
VPN clients connecting to the VPN server. The symptom you note sounds more
like a router or firewall between the client and VPN server is blocking GRE
(IP Protocol 47) traffic.


241398 RRAS Console Displays an "Internal" Routing Interface
http://support.microsoft.com/?id=241398

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

 

[Sam Smester]

Hi Marc,

I used the Microsoft Knowledge Base Article - 300434 to
setup the Remote Acces Server, following the Instructions
in "Enabling Windows 2000 Routing and Remote Access
Service to Allow Dial-up Connections or VPN Connections"
I notice the following step never show up:
6. On the Network Selection page, click the network
adapter that corresponds with your local area network
(LAN), and then click Next

After finish the wizard and restart the server I try to
remotely connect and all I get is a no response error.

Going back to the server and open Routing and Remote
Access, found that the Internal Interface have a Non-
operational status, a Not Available IP and an Unknown
Administrative Status.

The Internal Interface was screwed also in the DHCP Relay
Agent and in the IGMP.

The Remote Access or the VPN do not work with the Internal
Interface that way, I compare with 3 different VPN servers
and the Internal Interface have to be UP.

Any way to fix the Internal Interface?

 

[Dusty Harper {MS}]

As Marc stated the internal interface is basically irrelevant. It is a
logical interface used by RRAS. It will not have an IP address until the
first client connects. The interface state does not change until its first
connection.

When used in the protocols ( IGMP, DHCP Relay Agent etc. ) is basically
passing the protocol's functionality on to connected VPN / dial-up clients.
AS an example, The Internal interface configured as an IGMPRouter interface,
will allow the client to notify the server that it would like to receive
multicast streams. The RRAS server then notifies other IGMP enabled devices
that its clients want the stream through its IGMPProxy Interface.

I suggest you try to connect using PPTP from a local subnet ( subnet where
the RRAS server sits ). If you connect this way, then you are probably
having an issue with passing through a router or firewall
PPTP uses TCP port 1723 and Protocol 47 ( GRE )
L2TP uses UDP port 1701 and UDP port 500 ( IKE )

If you are still having issues, post back and let us know what event error
is being returned. You may also want to turn on tracing so we can see what
is going on.

Netsh ras ip set tracing * enable