Re: Group Policy Results Wizard and XP SP2
From: Darren Mar-Elia (dmanonymous_at_discussions.microsoft.com)
Date: 09/30/04
- Next message: Ian McGuinness: "Group policy switched off??"
- Previous message: Grant: "Printer web interface"
- In reply to: Greg M: "Group Policy Results Wizard and XP SP2"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 18:24:23 -0700
The first and easiest is to simply enable the following policy on the target
computer:
Computer Configuration|admin. Templates|Network|Network Connections|Domain
(or Standard) Profile|Windows Firewall: Allow Remote Administration
Exceptions. This will open ports 135 (RPC) and 445 (SMB) as well as higher
level ports >1023, which are also used by RPC. A more complete description
can be found here:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2maint.mspx
and in particular focus on the section called Resultant Set of Policy.
-- Darren Mar-Elia MS-MVP-Windows Server--Group Policy Check out http://www.gpoguy.com -- The Windows Group Policy Information Hub: FAQs, Whitepapers and Utilities for all things Group Policy-related "Greg M" <greg@vid-h2o.org> wrote in message news:9eee4bac.0409291532.7bfaa7d5@posting.google.com... > I'm in the process of testing all of our applications with Windows XP > SP2 (firewall active). Most normal apps run without any trouble but > I've come across some issues trying to do normal remote > administration. We use the Group Policy Results Wizard often to > troubleshoot and test new GPO settings before we roll them out. When > I run the wizard on an admin workstation connecting to a remote > machine that has XP SP2 with the firewall turned on, the wizard gets > an RPC error ("The RPC server is unavailable") after about 30 seconds > trying to connect. I turned on the exception for file and print > sharing on the remote machine and that didn't help. I looked at the > pfirewall.log file on the remote machine to determine what ports were > being used. TCP port 135 was being dropped from the admin machine to > the test machine so I added an exception to the test machine for tcp > port 135. Now instead of it taking about 30 seconds for the > connection to fail, it takes less than 1 second, but it still fails > with the above error message. I do not see any other ports being > blocked in the log. If I disable the firewall, I can connect without > any problems. Any suggestions would be appreciated. > > Thanks Greg.
- Next message: Ian McGuinness: "Group policy switched off??"
- Previous message: Grant: "Printer web interface"
- In reply to: Greg M: "Group Policy Results Wizard and XP SP2"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading