Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security NTBugtraq
[Top] [All Lists]

XP SP2 and RRAS mmc snap-in

Subject: XP SP2 and RRAS mmc snap-in
Date: Wed, 8 Sep 2004 15:54:08 +0400
  Hello NTBUGTRAQ.

  Short summary:
  This is the report of degrading/loosing functionality of RRAS mmc
  snap-in after upgrading XPSP1 to XPSP2.

        First some background.
  Windows 2000 administrative tools are not for use on Windows XP.
  This is fully documented and stated as "this is by design" in MSDN.
  As a solution they advise you to install "Windows Server 2003
  Administrative Tools Pack" for administering AD/DNS/DHCP etc. But,
  in 2003 ATP they removed RRAS snap-in. So, if you are netwotk
  administrator and you are using XP Pro as your workstation you have
  to add RRAS snap-in from 2000 ATP by using command-line switches for
  adminpack.msi for administering your 2000 RRAS servers. That's what
  is written and that's what I have done. Everything worked. Until...
        I have installed XP SP2.
  After that, trying to run "Routing And Remote Access" snap-in I
  receive the following messagebox:
    Caption: "Remote Access Policies Error"
    Text: "An error occured while trying to get information for an
    attribute. The stub received bad data."
    Buttons: OK
  Pressing OK button results in another same messagebox. And so on,
  and you have to end task via Task Manager. I suppose that this
  behaviour is because of RPC/DCOM security enhancements in XP SP2 but
  my RPC debugging skills are on 0/-1 level.

  I have tried the registry fixes mentioned in
  http://support.microsoft.com/default.aspx?scid=kb;en-us;824835 -
  "Certain IDL constructs are marshaled and unmarshaled incorrectly by
  RPC".

  and

  http://support.microsoft.com/default.aspx?scid=kb;en-us;838191
  "List of Remote Procedure Call (RPC) fixes in Windows XP Service
  Pack 2"

  Still no luck. Can anyone shed the light on this, or show me the way
  for further debug? Maybe the easiest way will be the using old RPC
  dlls with this only snap-in?

  Thanks.

;-------------------------------------------
; NKritsky
; mailto:nkritsky@internethelp.ru

-----
NTBugtraq Editor's Note:

Want to reply to the person who sent this message? This list is configured such 
that just hitting reply is going to result in the message coming to the list, 
not to the individual who sent the message. This was done to help reduce the 
number of Out of Office messages posters received. So if you want to send a 
reply just to the poster, you'll have to copy their email address out of the 
message and place it in your TO: field.
-----

<Prev in Thread] Current Thread [Next in Thread>
  • XP SP2 and RRAS mmc snap-in, Nickolay A. Kritsky <=