Re: DC dis-allowing remote desktop

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


If you mean you can not RDP into the client workstations then most likely
the Windows Firewall was enabled by Group Policy when the computers were
joined to the domain. Disable the Windows Firewall on those computers if it
does not pose a risk or create needed exceptions such as for Remote Desktop.
You may have to modify or disable the Group Policy managing the Windows
Firewall on the server to do what you want. If you run rsop.msc on a domain
computer you will be able to see which Group Policy is enforcing Windows
Firewall settings.

Steve


"Larry Clark" <info@xxxxxxxxxxxxx> wrote in message
news:mgH%j.1207$P5.521@xxxxxxxxxxxxxxx
I have a DC on my LAN, and all WKS have been accessing it as a workgroup.
Recently I have started to add the WKS one by one to the domain for more
security, but as soon as I join the computer to the domain, remote desktop
access is no longer available, nor is PC Anywhere.
the only way to access the machines remotely is with logmein or someother
type of remote access software, but osme people need the file transfer
ability that RDP allows.
any help to turn this back on would be greatly appreciated.
thanks,
Larry Clark




.

Relevant Pages

  • RE: group policy
    ... "Windows Firewall" settings should work properly in Group Policy. ... The domain profile settings that are used by the computers when they are ...
    (microsoft.public.windows.server.sbs)
  • RE: group policy
    ... We already manage our windows firewall settings on the local computers by ... group policy (Specifically the 'windows firewall' group policy in SBS ... Windows Firewall settings for computers running Windows XP with SP2 can be ...
    (microsoft.public.windows.server.sbs)
  • Offer Remote Assistance - "Permission denied" - Windows XP SP2
    ... We are having problems getting "Offer Remote Assistance" to work in our ... Administrators group on all computers with the \format to ... the Group Policy above ... - Opened all of the items below in the Windows Firewall through Group ...
    (microsoft.public.windowsxp.work_remotely)
  • remote desktop wont listen on port 3389 - cannot connect
    ... her windows firewall was greyed out, ... with group policy because by changing a few settings in group prolicy ... on a test box here at home, portqry tool shows remote desktop listening ... nmap reports this port closed. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: remote desktop wont listen on port 3389 - cannot connect
    ... her windows firewall was greyed out, ... with group policy because by changing a few settings in group prolicy ... on a test box here at home, portqry tool shows remote desktop listening ... nmap reports this port closed. ...
    (microsoft.public.windowsxp.work_remotely)