Re: Remote desktop connection error

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Sooner Al (SoonerAl_at_somewhere.net.invalid)
Date: 12/06/04 

Date: Mon, 6 Dec 2004 05:25:21 -0600

Michael,

Thanks for the feedback about Norton...

Glad its working for you... 

-- 
    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...
"Michael" <m.trott@bigpond.net.au> wrote in message news:e2RI6i02EHA.3244@TK2MSFTNGP11.phx.gbl...
> worked as soon as i tried the safe mode w/ network support.
>
> so went through msconfig, nuffin out of ordinary, I have recently upgraded to Norton Systemworks 
> 2005, and explicitly did not install norton internet security. But they now include a cutdown 
> firewall in the Antivirus portion of the package to handle worms. As soon as i disabled the norton 
> worm protection, all worked like a charm.
>
> Steven, Sooner :    I really appreciate the help :) thanks guys
>
> Michael
>
> "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
> news:OCD9T5y2EHA.1452@TK2MSFTNGP11.phx.gbl...
>> Does the computer have more than one network adapter?? Try booting into
>> safe mode with networking to see if you can access it that way. If you can
>> you have another service/application interfering in which case you can use
>> msconfig to troubleshoot.Check that the Terminal Services service and the
>> Remote Procedure Call services are both started. Also check that
>> administrators and remote desktop users groups are included in the user
>> right for "allow logon through terminal services" and that there are no
>> entries in the "deny logon through terminal services" user right. You can
>> do that by opening Local Security Policy and looking under security
>> settings/local policies/user rights.  --- Steve
>>
>>
>> "Michael" <m.trott@bigpond.net.au> wrote in message
>> news:uV$YCxs2EHA.1192@tk2msftngp13.phx.gbl...
>>> Hi steve,
>>>
>>> yeah scope set to internal network, when i disable the exception the
>>> DROP'd packects show up in the firewall log, yeah ive tried connecting
>>> via IP,
>>>
>>> maybe its just me, but if the port isn't open its either going to be the
>>> firewall or the app that uses/opens the port. And as i have tried with
>>> and without the firewall, and with both 3389 is closed to external
>>> access, so im guessing it Remote Desktop.
>>>
>>> Would make sense if the scope was only to allow from localhost, but i
>>> have enabled for local subnet, also tried all sources, neither would
>>> actaully open the port.
>>>
>>> really appreciate the help :)
>>>
>>> thnx
>>>
>>>
>>> Michael
>>>
>>>
>>> "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
>>> news:e$U%23pEi2EHA.3132@TK2MSFTNGP14.phx.gbl...
>>>> Check that your XP firewall does allow exceptions and that the "scope"
>>>> is correct as to IP addresses or subnet or all. If possible try to
>>>> disable the XP firewall when trying to connect from another computer on
>>>> your network and connect using the computer's IP address instead of name
>>>> to see if the problem is the firewall or something else. Of course do
>>>> not disable the XP firewall when connected to the internet without other
>>>> firewall protection such as a NAT router. And if using a NAT router,
>>>> port 3389 TCP will need to be forwarded to the internal IP address of
>>>> the computer you want to remote into.  --- Steve
>>>>
>>>>
>>>> "Michael" <m.trott@bigpond.net.au> wrote in message
>>>> news:%235mqsMh2EHA.2676@TK2MSFTNGP12.phx.gbl...
>>>>> only info I get is connection refused, which made me initially try
>>>>> telneting to port 3389 on my XP machine from another machine on my
>>>>> network and the port was closed.
>>>>>
>>>>> so either the firewall isin't actually allowing the exception rule,
>>>>> although it is set, or Remote Desktop, isn't for some reason
>>>>> initiallising and opening the port. The firewall is allowing some
>>>>> excetptions, ftp... , so it should be working
>>>>>
>>>>> when you said check the logs, did you just mean use the 'Event Viewer'
>>>>>
>>>>> thanks
>>>>>
>>>>> Michael
>>>>>
>>>>> "Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message
>>>>> news:unV8N9f2EHA.1400@TK2MSFTNGP11.phx.gbl...
>>>>>> Any error messages?
>>>>>>
>>>>>> Anything of interest in the logs?
>>>>>>
>>>>>> -- 
>>>>>>    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...
>>>>>>
>>>>>> "Michael" <m.trott@bigpond.net.au> wrote in message
>>>>>> news:eZb8suf2EHA.3816@TK2MSFTNGP09.phx.gbl...
>>>>>>> yeah, im admin and have p/w set, im listed as a user,
>>>>>>>
>>>>>>> its just not opening the port externally, just got me stumped
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> thnx
>>>>>>>
>>>>>>> Michael
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> "Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message
>>>>>>> news:%23u4EbUf2EHA.1392@tk2msftngp13.phx.gbl...
>>>>>>>> The account you use to log onto the PC with Remote Desktop must be
>>>>>>>> an Administrator or a member of the Remote Desktop Users Group *AND*
>>>>>>>> have a password. That account is local to the machine your trying to
>>>>>>>> log onto, not the remote PC that your sitting at...
>>>>>>>>
>>>>>>>> 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...
>>>>>>>>
>>>>>>>> <a@b.com> wrote in message
>>>>>>>> news:%23GAvuFf2EHA.2676@TK2MSFTNGP12.phx.gbl...
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> I cant connect into my XP prof (SP2) machine using remote desktop,
>>>>>>>>> remote desktop
>>>>>>>>> is enabled,
>>>>>>>>> checked and the rule is listed in the firewall exceptions, to allow
>>>>>>>>> from
>>>>>>>>> internal network.
>>>>>>>>>
>>>>>>>>> if i run netstat -a,
>>>>>>>>>
>>>>>>>>> TCP    main:3389              main:0                 LISTENING
>>>>>>>>>
>>>>>>>>> its listening on 3389, I can telnet from the box and the port is
>>>>>>>>> open,
>>>>>>>>> but cant access from other boxes on same network.
>>>>>>>>>
>>>>>>>>> The only problem i can see is in 'Select Remote Users' area, In the
>>>>>>>>> location
>>>>>>>>> field only the localhost is listed, and i cant edit. I thought may
>>>>>>>>> be due to
>>>>>>>>> an inactive service, so ive enabled all of the serives i have
>>>>>>>>> previously
>>>>>>>>> disabled, now all active, and still same problem.
>>>>>>>>>
>>>>>>>>> anyone have any ideas :)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> thnx
>>>>>>>>>
>>>>>>>>> michael
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>

Relevant Pages

  • Re: Turning on Media Sharing in WMP11
    ... I believe it forms quite a reasonable network media device. ... Turning on SSDP (it was disabled as was uPnP) to Manual and then UPnP ... If there is a firewall, or NAT, built into your ... You need to open port s: ...
    (microsoft.public.windowsmedia.player)
  • Re: May need to move from SBS because of connection issues
    ... Just to make sure you are clear regarding port 4125, ... access remote systems and you are behind a firewall on a non-SBS network, ... established that RWW worked TO your SBS network from outside. ... have been proof that the required ports were forwarded to the SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Identifying Internet Attacks
    ... contain the hacker to a particular machine, leave the machine on the network ... Some firewall software such as ... open ports; however, this will not identify which program is using the port. ... firewall logs, the IIS web and ftp server logs and Windows security event ...
    (microsoft.public.inetserver.iis.security)
  • Re: Problems joining NT Workstation to XP Pro Workgroup
    ... Can't access sharing because of NortonFor some reason, if you set up file sharing before installing Norton, it ... ... It turned out to be the copy of Norton Firewall I had running on the NT machine. ... I want to join it to a small workgroup of computers I have running at my office. ... I went under the network properties on the NT Workstation machine and assigned it to my "development" workgroup. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Leopard Firewall Warning
    ... machines on a particular network can access a port. ... The new scheme is an XP-style application based firewall; ... This, as an example, allows an attacker, once ...
    (uk.comp.sys.mac)