Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
Hi Al,
Thnak you for finding that MS fix. I contacted MS, downloaded the fix,
installed it and am still experiencing the same issues. I also verified that
Port 3389 is indeed open with the tool you sent me.
I'm going to try to re-test remotely later this morning and will keep you
apprised. Incidentally, I'm using dyndns.org and Direct Update to keep my IP
updated. If you would be available and wouldn't mind, I was wondering if
you'd be willing to help me troubleshoot later this evening. I could give
you my dyndns address and you could attempt connecting. If that's against
your policy, I completely understand and thank you for following this thread
through.
Tom
--
Tom Richards
tom@webhandprintSPAM.com
http://webhandprint.com
http://brainsturgeon.com
"Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message
news:%23QIeLlaSFHA.1528@TK2MSFTNGP09.phx.gbl...
> Did you see this post from yesterday? Its possible this is the root cause
> of your new issue...
>
>
http://groups-beta.google.com/group/microsoft.public.windowsxp.work_remotely/browse_thread/thread/7a8406b7ded135bf/4b69bbbd11cbefbe?q=group:*.work_remotely+author:Sooner+author:Al&rnum=5&hl=en#4b69bbbd11cbefbe
>
> Also see this recent thread for a possible solution...
>
>
http://groups-beta.google.com/group/microsoft.public.windowsxp.work_remotely/browse_thread/thread/6bc536b273d55441/25706322dacb2259?q=group:*.work_remotely+author:Sooner+author:Al&rnum=6&hl=en#25706322dacb2259
>
> Also, make sure that port forwarding through the router is working as
> advertised. Run the
http://www.canyouseeme.org test from the RDP host
> PC...
>
> --
>
> 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...
>
>
> "Tom Richards" <email@brainsturgeon.com> wrote in message
> news:e8aGuqZSFHA.1176@TK2MSFTNGP12.phx.gbl...
>>I disabled Norton 2005 Worm protection and am now able to connect with my
>>lan. But not remotely. I use Zone Alarm Pro with the 3389 port allowed and
>>forwarded through my linksys router. I've tried turning off ZA too with no
>>success. Windows firewall is disabled.
>>
>> I'm flummoxed because these same settings worked for months. But I guess
>> there's something about bringing a new pc into the mix, something I'm
>> missing.
>>
>> --
>>
>> Tom Richards
>> tom@webhandprintSPAM.com
>>
http://webhandprint.com
>>
http://brainsturgeon.com
>>
>>
>> "Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message
>> news:e1UZASZSFHA.1396@TK2MSFTNGP10.phx.gbl...
>>> Are you running any personal firewall software, like the XP SP2 Windows
>>> Firewall, on the PC?
>>>
>>> Are you running any anti-virus/Trojan software like NAV 2005 on the PC?
>>> There have been reports that NAV 2005 worm protection kills Remote
>>> Desktop connections if its running on the RDP host PC.
>>>
>>> --
>>>
>>> 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...
>>>
>>>
>>> "Tom Richards" <email@brainsturgeon.com> wrote in message
>>> news:uy5qJLZSFHA.204@TK2MSFTNGP15.phx.gbl...
>>>> Thank you Al. I've been troubleshooting based on the info contained at
>>>> that link and I'be been going step by step.
>>>>
>>>> 2 things are amiss:
>>>>
>>>> 1) I can't access my main (new) pc via RD from either of the other 2
>>>> workgroup pcs using the basic IP address. That was one of the first
>>>> things recommended to try.
>>>>
>>>> 2) Even though my port 3389 shows as "Listening" when I run the netstat
>>>> query...
>>>> ===================================
>>>> TCP DellDesktop:3389 DellDesktop:0 LISTENING
>>>> ===================================
>>>> ...after installing the Port Query tool and manually querying 3389, it
>>>> shows as "Not Listening." Here's the exact report:
>>>> ===================================
>>>> Starting portqry.exe -n DellDesktop -e 3389 -p TCP ...
>>>> Querying target system called:
>>>> DellDesktop
>>>> Attempting to resolve name to IP address...
>>>> Name resolved to 192.168.1.101
>>>> querying...
>>>> TCP port 3389 (unknown service): NOT LISTENING
>>>> portqry.exe -n DellDesktop -e 3389 -p TCP exits with return code
>>>> 0x00000001.
>>>> ===================================
>>>> Are there enough clues now for a fix or workaround?
>>>>
>>>> --
>>>>
>>>> Tom Richards
>>>> tom@webhandprintSPAM.com
>>>>
http://webhandprint.com
>>>>
http://brainsturgeon.com
>>>>
>>>>
>>>> "Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message
>>>> news:e93AuPYSFHA.2348@TK2MSFTNGP09.phx.gbl...
>>>>> This page has troubleshooting information that may help...
>>>>>
>>>>>
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
>>>>>
>>>>> --
>>>>>
>>>>> 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...
>>>>>
>>>>>
>>>>> "Tom Richards" <email@brainsturgeon.com> wrote in message
>>>>> news:O7VsmjTSFHA.3664@TK2MSFTNGP15.phx.gbl...
>>>>>> After a substantial period of trial and error, I finally got my RD
>>>>>> working last year and it worked flawlessly for about 15 months.
>>>>>> However, after adding a new pc to my home network, it won't work at
>>>>>> all:
>>>>>>
>>>>>> Network pcs are Dell laptop, Gateway desktop and Dell Desktop (the
>>>>>> new one). The laptop and Gateway desktop are now relegated to my two
>>>>>> children and the Dell desktop has become the main pc of the
>>>>>> workgroup. File sharing, print sharing, etc. all run fine. But, for
>>>>>> the life of me, I can't get RD to work. This is what DOES work - the
>>>>>> new Dell WILL connect to my former main pc, the Gateway desktop, via
>>>>>> remote desktop, in-network. But I can't get the 2 other network pcs
>>>>>> to hook up to the new main pc via RD. And no remote pcs can get
>>>>>> through via RD either.
>>>>>>
>>>>>> Tonight I thought I had the solution because I had neglected to
>>>>>> install Remote Desktop web connection. So I went 5 deep into the
>>>>>> nested menus and installed it, made sure the Anonymous Access box was
>>>>>> checked and giddily rebooted, had my girlfriend reboot and
>>>>>> NOTHING...still no connection.
>>>>>>
>>>>>> In System Properties | Remote - Remote Desktop is enabled
>>>>>> My Linksys router has port 3389 pointing to the appropriate IP
>>>>>> address
>>>>>>
>>>>>> Is there something I have to do to get my new Dell recognized as the
>>>>>> "main" pc of the workgroup? Should I rename the new Dell and give it
>>>>>> the name of the Gateway (the former main pc)? Does naming have
>>>>>> anything at all to do with this?
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Tom Richards
>>>>>> tom@webhandprintSPAM.com
>>>>>>
http://webhandprint.com
>>>>>>
http://brainsturgeon.com
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Facebook
Twitter
Instagram