Re: RPC and XP Profesessional SP2 and RestrictRemoteClients
From: Gianluca Braccini (gbraccini_at_tiscalinet.it)
Date: 02/26/05
- Next message: Gianluca Braccini: "Re: RPC_S_INVALID_BINDING in client"
- Previous message: Eugene Gershnik: "Re: directional advice on data and control exchange between processes on one and multiple machines"
- In reply to: Greg Kapoustin [MSFT]: "Re: RPC and XP Profesessional SP2 and RestrictRemoteClients"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 26 Feb 2005 13:45:01 +0100
Hi Greg sorry for my terrible english, The policy hasn't disappeared from
the UI of gpedit.msc. But it doesn't work anymore. I try to explain to you
the problem more exactly: we have many clients with XP Pro, and when SP2 was
released, setting RestrictRemoteClients worked fine with gpedit . But now
our new clients, with XP Pro SP2 and with all windows update installed, set
RestrictRemoteClients with gpedit.msc but our program doesn't work. If i
seek in the registry i cannot find:
\\HKLM\SOFTWARE\Policies\Microsoft\WindowsNT\RPC\RestriRemoteClients
(DWORD) 0.
I find this key in another point of the registry, but the RPC server cannot
accept anonimus client. But if i setup the key manually, everything is ok.
I suppose that microsoft has changed something in the last windows update,
so now gpedit doesn't work with RestrictRemoteClients.
You can try, it's very easy. If you get a new pc with xp pro sp2 and windows
update, setting RPC policies with gpedit you couldn't use a sample RPC
server with no autenthication. You must edit manually the registry.
I know very well that i can use RpcServerRegisterIfEx() with
RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH, but we have many thousands of clients
( with windows 95, 98, ME, NT, XP ) and we prefer don't change the source
code.
thanks for your answer.
Gianluca
"Greg Kapoustin [MSFT]" <grigorik@online.microsoft.com> ha scritto nel
messaggio news:421f6f08$1@news.microsoft.com...
> If the RetrictRemoteClients setting is not visible in the UI of
gpedit.msc,
> it sounds like a potential issue with the relevant policies. Can you
> identify anything that may have caused the problem, for instrance
> installation of a new application?
>
> You should be able to work around the problem by manually editing the
> registry as you have done. However, it would be useful to identify what
> causes the policy to disappear from the UI.
>
> Greg
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Gianluca Braccini" <gbraccini@tiscalinet.it> wrote in message
> news:uQbxeBZGFHA.3368@TK2MSFTNGP10.phx.gbl...
> > For using a server RPC not secure on XP professional SP2 before i used
> > gpedit.msc for setting the RetrictRemoteClients, and all woked fine. But
> > now
> > this doens't works. After the setup if i see in the registry i don't
find
> > the key: \\HKLM\SOFTWARE\Policies\Microsoft\Windows
> > NT\RPC\RestriRemoteClients (DWORD) 0
> > If i insert the key manual in the registry and reboot, all works fine.
But
> > before this was true only for Xp Home Edition SP2, is it change
something?
> > Is it a problem with gpedit.msc? the user is administrator.
> >
> > Gianluca
> >
> >
> >
>
>
- Next message: Gianluca Braccini: "Re: RPC_S_INVALID_BINDING in client"
- Previous message: Eugene Gershnik: "Re: directional advice on data and control exchange between processes on one and multiple machines"
- In reply to: Greg Kapoustin [MSFT]: "Re: RPC and XP Profesessional SP2 and RestrictRemoteClients"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
