[SOLUTION] Dial-In tab error "Dial-in page initialization failed" on 2012 and 2008 servers

Dial-In tab error "Dial-in page initialization failed" on 2012 and 2008 servers

I have a two-server environment with a 2008 and a 2012 server. 2012 is the only domain controller.
I cannot access the "Dial-In" tab in Active Directory Users and Computers. When I try, I receive the following error:

Dial-in page Error
Could not load the Dial-in profile for this user because: The network path was not found.
.

When I click OK on this error, the following is displayed:

Dial-in page initialization failed.

I have done Google searches on this error.
The permissions on the winreg and allowedpaths folders are correct.
The Remote Registry service is running.
The primary NIC is the first in the binding order.

I am not able to find any useful errors in the event log that indicate trouble with this, or any other trouble that might be related.

I installed the AD Remote Administration Tools on the Windows 2008 server, opened AD Users and Computers on that server, and I get the same error.
The DNS pointers are correct, including the domain suffix. I have no other indications of Active Directory lookup failures.

Update: I was able to use the following netsh command to get the job done for now, but I'd like to resolve this issue.
netsh RAS set user name=[username] dialin=PERMIT

Any ideas?

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LVL 38

bbaoIT ConsultantCommented: 2015-02-26

> The permissions on the winreg and allowedpaths folders are correct.

are you talking about the READ permission for LOCAL SERVICES against the given registry items?

LVL 4

Member_6162666Author Commented: 2015-02-26

That is correct. I read that article, in various forms, on about 50 websites. I double checked and triple checked those settings, and they are correct.

The only other thing I have been able to find that seems unhappy on the 2012 R2 server is that it takes about 2 minutes to open the Services.msc applet. If I make any changes to any services, for example the Startup Type, it takes the same amount of time to save those changes and close the properties dialog. This does not happen on the 2008 R2 server.
I don't know if this is related, but it's the only other thing acting strangely on this server so I thought I would mention it.

> That is correct. I read that article, in various forms, on about 50 websites. I double checked and triple checked those settings, and they are correct.

that's a bit weird.

have you ever tried reporting this to MS or applied for their technical support against the issue?

if i was you, in the mean time, i would install a new 2012 server and set up a new AD on the sever. then if the newly installed system does not have the issue, i may compare the two servers' settings one by one...

I have already spoken with the customer about setting up another DC to see what happens, and provide a bit of redundancy to their network, so that is in the works.
I figured if nobody comes up with a solution here, I might call MS support. But MS support is not what it used to be, so that's not my first choice.

> MS support is not what it used to be,
so that's not my first choice.

however they may provide prioritised services especially if you are covered by their license subscription or partner membership.

moreover, probably the most important thing is that they can remotely touch your system and/or collect the diagnosis information which will be essential for troubleshooting this kind of issue. obviously, you can't do this at EE or other tech support communities online.

Member_6162666Author Commented: 2015-03-03

Anyone else have feedback on this?
Has nobody had this happen, without "the usual suspects" solving the problem?

Member_6162666Author Commented: 2015-03-16

Fortunately, I had not yet increased the domain functional level and forest functional level, so I added a Windows 2008 R2 domain controller, and I do not have the Dial-In tab problem on that one. I am not going to spend any more time on the problem with the 2012 domain controller.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial

Member_6162666Author Commented: 2015-03-21

Nobody came up with a viable solution, so I set up a workaround.

Dial-In tab error "Dial-in page initialization failed" on 2012 and 2008 servers

Who is Participating?