Error Joining Domain Rpc Protocol Sequence 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
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 2011-05-26 Windows Server 2003 Windows XP Windows Networking 1 Verified Solution 4 Comments 12,461 Views Last Modified: 2012-05-11 An XP Pro SP3 client on a Windows Server 2003 SP2 domain is unable to process GPOs at https://www.experts-exchange.com/questions/27574258/The-RPC-Protocol-Sequence-is-not-supported.html login due to Event ID 1053, "Windows cannot determine the user or computer name. (The RPC protocol sequence is not supported. ). Group Policy processing aborted." Neither can the client be rejoined to the domain, same error. I have read and tried a number of things, some related to the network card advanced settings, all to no avail. The RPC and RPC Locator services are running on both the client and server. I'm starting to think about https://www.experts-exchange.com/questions/27062442/The-RPC-protocol-sequence-is-not-supported.html OS repair install for the client, as other clients are not experiencing this problem are are processing the GPOs succesfully. Any advice appreciated. 0 Question by:westone Facebook Twitter LinkedIn Google LVL 8 Best Solution byspiderwilk007 Yes, I believe this is a corruption in the XP Pro Clients OS. I would definately recommend the OS repair. I think its going to be the easiest and fastest way to fix the problem. Go to Solution 4 Comments LVL 8 Overall: Level 8 Windows Server 2003 3 Windows Networking 1 Windows XP 1 Message Accepted Solution by:spiderwilk0072011-05-26 Yes, I believe this is a corruption in the XP Pro Clients OS. I would definately recommend the OS repair. I think its going to be the easiest and fastest way to fix the problem. 0 Message Author Comment by:westone2011-05-26 Okay, I'm on it and will report the results shortly. Thanks! 0 LVL 16 Overall: Level 16 Windows Server 2003 6 Windows XP 5 Windows Networking 2 Message Expert Comment by:R. Andrew Koffron2011-05-26 just in case. try setting the AD - DNS server as the only DNS server the XP machine has. 0 Message Author Comment by:westone2011-05-26 Repair install did the trick. Thanks for the help! 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with a
we highly recommend that you visit our Guide for New Members. Solved: XP Workstation Unable To Join https://forums.techguy.org/threads/solved-xp-workstation-unable-to-join-domain.863732/ Domain Discussion in 'Windows Server' started by Timbilt, Sep 25, 2009. Thread Status: Not open for further replies. Advertisement Timbilt Thread Starter Joined: Sep 24, 2009 Messages: 15 Sorry, I posted this 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 error joining 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 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 error joining domain 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 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