Re: Getting: "The RPC protocol sequence is not supported."

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Ivan Brugiolo [MSFT] (ivanbrug_at_online.microsoft.com)
Date: 03/08/04 

Date: Mon, 8 Mar 2004 09:46:09 -0800

Looks like you have configured DCOM in the W2K box to
use a tranport protocol that is not enabled by default in W2K3.
For example, RPC-OVER-TCP/UDP.
W2K3 attempts to limit the number of protocols
an RPC sever is listening at the same time,
in order to minimize the attack surface.
In fact, the binding over a transport is process wide,
and if you have 2 servers bound to 2 different transports,
you can reach both of them with the 2 transports,
and this may not a desirable effect. 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Steen Tøttrup" <never@mind.com> wrote in message
news:uNAb2lFBEHA.212@TK2MSFTNGP12.phx.gbl...
>
> This is what I'm trying to do. I'm building a windows service using C#. At
> the moment I'm using a windows app to test the functionality. When running
> this app from the windows 2000 server I'm developing on, I'm getting: "The
> RPC protocol sequence is not supported."
>
> The service is connecting to a server on another domain (windows 2003),
> using WMI (trying to access the DNS), impersonating an user on the other
> domain.
>
> When connecting to the local DNS server, no problems.
>
> Then I moved the app to the server I'm try to connect to, and run it. This
> is what I get:
>
> "System.BadImageFormatException: Exception from HRESULT: 0x800700C1.
>    at System.Management.ManagementScope.Initialize()
>    at System.Management.ManagementScope.Connect()
> "
> and the code that is generating the exception:
>
> // Set impersonation if connecting to a remote server.
> ConnectionOptions conOptions = GetConnection(sLocalMachine, sServer);
> string sServerPath = "\\\\myserver\\root\\microsoftdns";
> ManagementScope oScope = new ManagementScope(sServerPath, conOptions);
> // Explict connection to WMI namespace
> oScope.Connect();
>
> Any ideas? I've already got another service running doing something
similar,
> can't seem to locate the problem (or difference)..
> I think I've already found all the differences between 2000 and 2003 WMI,
> this seems to be something else?!
>
> Please help!
>
> regards,
> J.
>
>
>

Relevant Pages

  • Printer Driver / Port Options
    ... My client uses Windows 2003 Server and Window 2003 Pro on the desktops. ... grab their printer when connected as admin to the Server via RDP and adjust ... them through changing the setting by connecting to a RDP session w/o starting ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Enabling Remote Access
    ... you must create a sql-server login and use it when connecting ... through the VPN and the authentification mode of SQL-Server must be set to ... the mixed mode (Windows + SQL-Server). ... I am able to VPN into the server using Remote ...
    (microsoft.public.access.adp.sqlserver)
  • PPTP XP 2 minute disconnect
    ... I am running Windows XP SP2 to connect onto a Windows ... in connecting using this XP machine for many months; ... of the server and now every 2 minutes 8 seconds the XP ... Linksys router - the router was added to bounce ...
    (microsoft.public.win2000.ras_routing)
  • Re: Small remote x client
    ... than the MicroImages X server. ... On Windows, they usually have fairly elaborate GUIs ... protocol emote rameuffer protocol), ... the windows VNC client will very easily fit on a floppy: ...
    (comp.os.linux.networking)
  • Re: Printer Driver / Port Options
    ... My client uses Windows 2003 Server and Window 2003 Pro on the desktops. ... grab their printer when connected as admin to the Server via RDP and adjust ... them through changing the setting by connecting to a RDP session w/o ...
    (microsoft.public.windowsxp.setup_deployment)