Additional help...

http://portforward.com/english/route...te_Desktop.htm

http://portforward.com/english/route...te_Desktop.htm
http://portforward.com/english/route...te_Desktop.htm

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

"Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message
news:O58JZJ36FHA.2264@TK2MSFTNGP11.phx.gbl...
> If the canyouseeme.org test fails it comes down to a port forwarding issue
> on either the Westell or the router or both. You could try isolating
> (between a problem with the Westell or the router forwarding) a bit by
> connecting the PC directly to the Westell modem and see if you can get it
> to work...
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
> "Mike Hardin" <Mike Hardin@discussions.microsoft.com> wrote in message
> news:8341F946-4C81-4062-85E2-4CD23707E55E@microsoft.com...
>>I am having difficulty running Remote Desktop through my WAN. I am
>>running
>> XP pro, and can access the host via a client on my LAN, but not over the
>> WAN.
>> I have a Westell Wirespeed 2200 modem/router, and a Motorola WR850G
>> wireless
>> router between the modem and the network. I have port 3389 forwarded
>> from
>> the Westell to the Motorola, and from the Motorola to the Windows XP
>> machine
>> on my LAN. I have port 3389 open in Windows XP, Remote Desktop enabled
>> with
>> a designated user, and have even tried turning off all software firewalls
>> completely, as well as all virus and anti-spyware software. Still I
>> cannot
>> get it to work. Clicking on canyouseeme.org and entering port 3389 still
>> generates an error that 3389 cannot be seen on my system. Terminal
>> services
>> is started, and netstat -a shows that 3389 is listening. I'm at a loss
>> as to
>> what to try next.
>
>