Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Is there anyting that could cause my remote desktop client not to connect to
a work pc which is on the domain. I have done all the neccessary port fwding
and opened ports on the firewall. I even have allowed remoted desktop protcol
and services to be running on windows xp pro service pack 2. Anyhow, my
question to you is there a group policy or something i can check to see what
is blocking my remote access to work computer. I think it has to do with my
domain. I have static ip address at work. My router also is setup to port fwd
3389 to the right static DHCP address within my LAN connection.
I just cannot connect to my work computer using remote desktop.
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Ankit Shah wrote:
> Is there anyting that could cause my remote desktop client not to
> connect to a work pc which is on the domain. I have done all the
> neccessary port fwding and opened ports on the firewall. I even have
> allowed remoted desktop protcol and services to be running on windows
> xp pro service pack 2. Anyhow, my question to you is there a group
> policy or something i can check to see what is blocking my remote
> access to work computer. I think it has to do with my domain. I have
> static ip address at work. My router also is setup to port fwd 3389
> to the right static DHCP address within my LAN connection.
>
> I just cannot connect to my work computer using remote desktop.
What message do you get?
Can you remote from within your work network?
--
<- Shenan ->
--
The information is provided "as is", it is suggested you research for
yourself before you take any advice - you are the one ultimately
responsible for your actions/problems/solutions. Know what you are
getting into before you jump in with both feet.
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Ask your systems admin. They probably block almost all ports at their
gateway.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Ankit Shah" wrote:
| Is there anyting that could cause my remote desktop client not to connect
to
| a work pc which is on the domain. I have done all the neccessary port
fwding
| and opened ports on the firewall. I even have allowed remoted desktop
protcol
| and services to be running on windows xp pro service pack 2. Anyhow, my
| question to you is there a group policy or something i can check to see
what
| is blocking my remote access to work computer. I think it has to do with
my
| domain. I have static ip address at work. My router also is setup to port
fwd
| 3389 to the right static DHCP address within my LAN connection.
|
| I just cannot connect to my work computer using remote desktop.
|
| Ankit Shah
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Group policy can definitely block Remote Desktop.
I like the idea of testing from the same LAN at work--try that and tell us
what error message you get, if any.
Has Remote Desktop ever worked on this particular machine?
"Ankit Shah" <AnkitShah@discussions.microsoft.com> wrote in message
news:9A8EEAFB-767A-4966-B838-F7F1EE1057C9@microsoft.com...
> Is there anyting that could cause my remote desktop client not to connect
> to
> a work pc which is on the domain. I have done all the neccessary port
> fwding
> and opened ports on the firewall. I even have allowed remoted desktop
> protcol
> and services to be running on windows xp pro service pack 2. Anyhow, my
> question to you is there a group policy or something i can check to see
> what
> is blocking my remote access to work computer. I think it has to do with
> my
> domain. I have static ip address at work. My router also is setup to port
> fwd
> 3389 to the right static DHCP address within my LAN connection.
>
> I just cannot connect to my work computer using remote desktop.
>
> Ankit Shah
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.