Dial In Page Error
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand could not load the dial-in profile for this user because the network path was not found Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups dial-in page initialization failed Website Testing Store Headlines Experts Exchange > Questions > Dial-In tab error "Dial-in page initialization failed" on 2012 and 2008 servers Want could not load the dial in profile for this user because member not found to Advertise Here? Solved Dial-In tab error "Dial-in page initialization failed" on 2012 and 2008 servers Posted on 2015-02-25 Windows Server 2012 Windows Server 2008 Active Directory 1 Verified Solution 10 Comments 1,031 Views Last Modified: could not load the dial-in profile for this user because unspecified error 2015-03-21 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? 0 Question by:Scovndrel Facebook Twitter LinkedIn Google LVL 4 Best Solution byScovndrel 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 Go to Solution 10 Comments LVL 36 Overall: Level 36 Windows Server 2008 9 Active Directory 6 Windows Server 2012 6 Message Active today Expert Comment by:Bing CISM / CISSP2015-02-26 >
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs https://www.experts-exchange.com/questions/28624774/Dial-In-tab-error-Dial-in-page-initialization-failed-on-2012-and-2008-servers.html by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Dial-up Forum at Tek-Tips HomeForumsData TransmissionData TransmissionsDial-up Forum Dial-in properties in W2k3 AD fails thread584-754181 Forum Search FAQs Links MVPs Dial-in properties in W2k3 AD fails http://www.tek-tips.com/viewthread.cfm?qid=754181 Dial-in properties in W2k3 AD fails swedishthom (IS/IT--Management) (OP) 20 Jan 04 09:57 Desperat need of help!The problem has been posted earlier and I really are in need of a solution..I have searched all the Internet for this problem and tried everything I possible can think of but havenĀ“t found any solution.After moving my remote access server from my Windows 2003 / Active Directory domain controller to a member server in the same domain I cannot access the dial-in property page in Active Directory users and computers.This applies to any user in the AD:Clicking the Dial-in tab I get the following error message:Dial-in Page errorCould not load the Dial-in profile for this user because: The network path was not found.Clicking the "ok" option it displays the following:"Dial-in page initialization failed".All other tabs works fine.Have not made any changes in the group policy nor anywhere else regaring the Remote Access.Anyone got a clue? I would be able to define the network path somewhere?Please Please !!! help My management are on my case everyday since they a
for any user and on either server then click on the Dial-In tab I receive could not the following error: Dial-in Page Error Could not load the Dial-in profile for this user because: The network path was not found. The only button on the could not load window is the OK button. After I click on the OK button the Dial-In tab says: Dial-in page initialization failed. Any ideas? Stacey . Follow-Ups: Re: Dial-in Page Error From: Ulf B. Simon-Weidner [MVP] Prev by Date: AD 2003 OU Security Question Next by Date: Problems opening the GPO Previous by thread: AD 2003 OU Security Question Next by thread: Re: Dial-in Page Error Index(es): Date Thread Flag as inappropriate (AWS) Windows Science Usenet ArchiveAboutPrivacyImprint www.tech-archive.net >Archive >Windows >microsoft.public.windows.server.active_directory >2005-06