Re: Cannot connect to remote client desktops

Thanks again. 1st thing monday that is my intent. again I appreciate your
assistance

Herb_C

"Lanwench [MVP - Exchange]" wrote:

Herb_C <HerbC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
OK Now I think I need to take a step back for a few and see the
forest for the trees. I thought I had checked the windows firewall
settings on the workstations and apparently I had checked the remote
assistance instead of remote desktop. DUH! This server has been a
trouble maker from the setup with problems created by service packs
not fully installing and other features just not working for no
reason. I think I was just looking too deep and forgot K.I.S.S.
(keep it simple ...)

Thank you again

You're welcome. Group policy should have set all this for you if you ran
connectcomputer, so I suggest you run a gpupdate /force, and then an
rsop.msc on the workstations. Then check the event logs.



Herb_C

"Lanwench [MVP - Exchange]" wrote:

Herb_C <HerbC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
All Client computers were connected to the domain using the
connectcomputer wizard. I have learned many years ago to never
re-invent the wheel if it has been done already.

Great - just checking.
Check the firewall & RD settings and make sure you can connect using
the RD client directly across the LAN.

"Lanwench [MVP - Exchange]" wrote:

Herb_C <HerbC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am finalizing an installation of a sbs 2003 premium and I am
down to onw final problem. When remotely connecting to the server
everything works as it should except remotely connecting to the
workstations. remote server connection works flawlessly but if
you try to connect to client desktops you eventually get an error
message stating that you cannot connect and to check and make sure
the workstation is connected to the network

Thank you in advance for your assistance.

Herb_C

How did you join the computers to the domain? Use the
/connectcomputer wizard and it will configure this for you (the RD
settings, permissions, and firewall settings) among many other
things. Ignore the wizards at your peril. If you used the manual
method, disjoin the workstations from the domain and start over. If
you did use /connectcomputer, check the workstation to ensure RD is
enabled & the firewall exception is set (or set it manually in your
third party firewall software).




.

Relevant Pages

  • Re: Questions About Windows Firewall and Domain Policy Enforcement (Updated Info)
    ... I have a Windows 2000 domain that has 200 workstations most of which are ... If we enable the firewall on the workstations then the domain ... SP2 settings on firewall activation). ... long as there is no Standard Profile configured. ...
    (microsoft.public.win2000.group_policy)
  • Re: Questions About Windows Firewall and Domain Policy Enforcement (Updated Info)
    ... I have a Windows 2000 domain that has 200 workstations most of which are ... If we enable the firewall on the workstations then the domain ... SP2 settings on firewall activation). ... long as there is no Standard Profile configured. ...
    (microsoft.public.windows.group_policy)
  • Re: Cannot connect to remote client desktops
    ... settings on the workstations and apparently I had checked the remote ... assistance instead of remote desktop. ... Check the firewall & RD settings and make sure you can connect using ...
    (microsoft.public.windows.server.sbs)
  • Questions About Windows Firewall and Domain Policy Enforcement
    ... I have a Windows 2000 domain that has 200 workstations most of which are ... If we enable the firewall locally on the workstations then the ... If we disable the firewall settings locally then the domain ... in the policy then it applies that setting over the Domain Profile. ...
    (microsoft.public.windows.group_policy)
  • Questions About Windows Firewall and Domain Policy Enforcement
    ... I have a Windows 2000 domain that has 200 workstations most of which are ... If we enable the firewall locally on the workstations then the ... If we disable the firewall settings locally then the domain ... in the policy then it applies that setting over the Domain Profile. ...
    (microsoft.public.win2000.group_policy)
Loading