Recent content by LenG58

just a quick update. i wound up creating a new rule in windows firewall. i allowed incoming tcp to the specific port # i had set up for rdc. it's working now. i'm not sure why allowing rdc through windows firewall didn't work. maybe it had something to do with my changing the default port #...

for all 3 settings, domain profile, private profile and public profile all show block (default) on inbound connections when i click on 'windows firewall properties". although in the middle of the page it states "inbound connections that do not match a rule are blocked.

i have checked the allow public remote desktop connection and am still not bale to connect unless i turn off the firewall on the desktop. all other network functions are fine.

i use windows firewall. i have the items checked just as you have shown. i cannot connect until i turn the firewall off. then all goes as planned.

thank you for your help, salt. to answer your questions... yes, desktop awake. yes, using the public ip address of my router. yes, desktop is set up to allow connections although i use the option below (the more secure option) the one you have pictured. interesting new development...it seems...

i am unable to connect at home also. my desktop does have a static ip. i have forwarded the port through my router (linksys befsr41) and i still get can't connect error message.

hello all, i would like to connect using RDC from my netbook (using windows 7 starter) to my desktop (using windows 7 professional) on the road. i have followed all the steps here: Allow Remote Desktop connections from outside your home network when i try to connect i get the dreaded...