Error Joining Domain The Rpc Protocol Sequence Is Not Supported
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 Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > The RPC Protocol Sequence is not supported Want to Advertise Here? Solved The RPC Protocol Sequence is not supported Posted on 2012-02-07 Windows OS Windows XP Windows Server 2008 1 Verified Solution 2 Comments 6,930 Views Last Modified: 2012-06-27 I have a user that has had a windows xp workstation for years. We are running WINDOWS 2008R2 servers in our domain environment. Yesterday he picked up some kind of virus, then kind that tries to sell you a AV software, but is really a virus in itself. Anyway, we ran our Vipre anti virus as the local administrator. Then I renamed his profile in Windows XP. I removed the machine from the domain and last night I ran ClamWin anti virus as an extra precaution. I tried to rejoin the domain today, but it gave me some difficulty. I finally ranmed his workstation and it let me rejoin. I tried logging in as a domain user but cannot get OUTLOOK to connect to our EXCHANGE 2007 server. I keep getting an error "The RPC Protocol Sequence is not supported". I logged back in as the local administrator and tried to add my domain admin account to the PCs local administrator account. It finds my name when I CHECK NAMES, but when I go to click OK I get the same message "The RPC Protocol Sequence is not supported" I am running out of ideas. I check DNS and everything seems to be running fine. I can ping all devices on the network by name and ip address....all advice is welcome 0 Question by:Thor2923 Facebook Twitter LinkedIn Google LVL 33 Best Solution byExchange_Geek Please ref: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_27062442.html Cheers, Exchange_Geek Go to Solution 2 Co
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet https://www.experts-exchange.com/questions/27574258/The-RPC-Protocol-Sequence-is-not-supported.html Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events https://technet.microsoft.com/en-us/library/cc978975.aspx Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Library Wiki Learn Gallery Downloads Support Forums Blogs We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Windows 2000 Error Messages Reference Kernel System Resources System Resources The RPC protocol sequence is not supported. ... The RPC protocol sequence is not supported. ... The RPC protocol sequence is not supported. ... The RPC server is unavailable. ... A lock request was not outstanding for the supplied cancel region. ... The file name is too long. ... Some mapping between account names and security IDs was not done. ... Child windows cannot have menus. ... All pipe instances are busy. ... The netwo
we highly recommend that you visit our Guide for New Members. Solved: XP Workstation Unable To Join Domain Discussion in 'Windows Server' started by Timbilt, Sep 25, 2009. Thread Status: Not open for further https://forums.techguy.org/threads/solved-xp-workstation-unable-to-join-domain.863732/ replies. Advertisement Timbilt Thread Starter Joined: Sep 24, 2009 Messages: 15 Sorry, I posted this https://modem7.wordpress.com/2013/07/24/rpc-protocol-sequence-is-not-supported/ yesterday in the wrong section. Hopefully I get some more help. Here we go... This is my first post on this site, and I just want you guys to know that I tried my best before making this post, but I just can't seem to solve this problem. We have a domain with all workstations running Windows XP Professional. The server is error joining Windows 2000 Server. A new computer running Windows XP Professional x64 Edition is trying to connect to the domain but is getting the following error: The following error occurred attempting to join the domain "domain_name"; The account is not authorized to log in from this station. I tried the following settings in local security settings: Digitally sign client communications (always) - disabled Digitally sign server communications (always)- disabled Digitally sign server communications (when possible) - disabled LAN error joining domain Manager Authentication Level set to Send LM and NTLM - use NTLMv2 session security if negotiated - (default) send LM & NTLM responses Secure channel: Digitally encrypt or sign secure channel data (always) - disabled Secure channel: Require strong (Windows 2000 or later) session key - disable Unfortunately this did not solve the problem. Thanks a lot to anyone that even attemps to help me think of the solution to this problem. I'll continue to poke around the Internet for any leads. Timbilt, Sep 25, 2009 #1 Sponsor srhoades Joined: May 15, 2003 Messages: 2,281 Do an ipconfig /all and make sure your NIC has the correct DNS servers. srhoades, Sep 25, 2009 #2 Timbilt Thread Starter Joined: Sep 24, 2009 Messages: 15 That is one of the first things that I did, and it's correct. This just seems so strange. This weekend I'm gonna try to think of some things to try on Monday. Timbilt, Sep 26, 2009 #3 avisitor Joined: Jul 12, 2008 Messages: 1,710 This might be obvious but, check that in Active Directory Users and Computers the user you are trying to join the domain with has permission to log onto that PC. That is, right click on the user, click properties, then Account, then Log On To, then select "All computers" or put in the NetBIOS name of the
by email. Join 488 other followers Meta Register Log in Entries RSS Comments RSS WordPress.com Posts Google Chrome ScrollAnchoring How To Reset A Forgotten Raspberry PiPassword Setting Message Size Limits in Exchange 2010 and Exchange2007 Using Process Monitor to measure logontimes Clean WSUS Server User Accounts Do Not Show Up in the Windows SBSConsole How to perform clean install of Take Control on a singledevice How to kill a Windows service that's stuck on stopping orstarting SBS MSSQL$SBSMONITORING 1105 Event ErrorSQL Change the Default OU for New Users or Computers in ActiveDirectory Exchange 2010 Mail Queue – 451 4.4.0 DNS QueryError Outlook 2003 Out of Office Assistant Error: “The command is not available. See the program documentation about how to use thisextension” Print SharePoint wiki pages all atonce DrayTek's Vigor 2850 Firmware v3.6.4 Breaks Windows Server 2012 Essentials AnywhereAccess Batch script - Remove HPBloatware RPC protocol sequence is notsupported July 24, 2013 by Alex 1 A member of staff contacted me in regards to his Outlook client not connecting to the Exchange server. The obvious quickfix of setting a new profile up kept reporting that Exchange is offline. A quick check the event logs gave quite a few Userenv errors, event ID 1053: Windows cannot determine the user or computer name. (The RPC protocol sequence is not supported. ). Group Policy processing aborted. This means that we can’t properly complete the RPC call, and suggests that network communication is having issues. So, let’s see if there’s any other evidence of problems with the machine’s networking. First, let’s see if we can get the machine’s name out of it. Open cmd, hostname: Well then, problems with the networking stack, let’s do a winsock reset and reset the TCP/IP stack… Right… so MSWSOCK.dll is broken, just unregister that and reregister… Ok, winsock totally broken. Let’s work on that first. Nope, turns out that’s apparently normal for both dlls. However, netsh int ip reset NULL fails with: The following helper DLL cannot be loaded: IFMON.DLL. The following command was not found: int ip reset And the same error I got while trying to do a winsock reset. Start thinking virus, so Hosts file is good, get and then run a malwarebytes scan, and it comes up with a couple of trojans that it cleans. Unfortunately the problem still persi