VPN Error 930

[James Goodman]

I have a network with two domain controllers.

Domain Controller SERVER1 used to be an RRAS server. I had to upgrade the
disk in it, so ran DCPROMO to demote it to a member server. I then installed
the new disk, OS & ran DCPROMO again to promote it back to being a domain
controller. All of this passed without error.

I am now attempting to configure it for RRAS again. I manually configured it
to allow PPTP VPN connections. This DC is also a DHCP server, so I added
127.0.0.1 & 192.168.1.3 (the other DC) as DHCP relay agent addresses.

When I attempt to establish a VPN I get error 930.

To see if it was a network problem I configured the other DC (named DC2) for
RRAS exactly as above. I can immediately connect to this, as expected.

The only difference I see is the existence of an Internal interface on DC2.
This is missing on SERVER1 & I cannot add it.

Does this explain why authentication would fail?
Any suggestions for a fix?

 

[James Goodman]

Ok, to confuse the issue further it is now working. I made no changes. I
restarted RRAS (which I have tried many times) & it is now working.

Mystified...

 

[Priya Raghavan [MSFT]]

Hi James,

Regarding the internal interface which you were seeing on DC2, that comes
automatically when the first client connects to the RAS Server.
As no client was able to connect to DC1, it did not get the internal
interface.Whereas DC2 was able to get it.

930 usually comes when you have configured your RAS Server for RADIUS auth
and you are not able to reach the RADIUS Server.
If you dont have RADIUS auth, this usually gets corrected by refreshing the
RAS Server (or re-starting the service) as you have done.