Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
One thing that I noted - if you enable Remote Desktop via the Group
Policy method, it will not automatically enable the port in the ICF...
Weird bug...
Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com
Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....
Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
On Tue, 31 Aug 2004 14:37:00 -0400, "Bill Sanderson"
<Bill_Sanderson@msn.com.plugh.org> wrote:
>Interesting. This shouldn't happen for most folks. I've installed SP2 on a
>number of machines--a dozen or so, via Remote Desktop and haven't seen this
>issue. These machines in the main had the SP1 firewall in place with RD
>opened.
>
>"Steven" <landsteven@gmail.com> wrote in message
>news:74497317.0408260606.1d9476bf@posting.google.com...
>> Are you sure you have Remote Desktop enabled? It turns out that this
>> was simply due to an ID10T error on my end. When XP SP2 installs it
>> disables the Remote Desktop setting in My Computer > Remote tab.
>>
>> I know I had RDP enabled and working before the install... so then I
>> after installed I assumed that that was still the case and that I was
>> having a Windows Firewall issue. I was wrong. Once I enabled Remote
>> Desktop again, everything works fine!
>>
>> <anonymous@discussions.microsoft.com> wrote in message
>> news:<ab7201c4889d$84ae1260$a501280a@phx.gbl>...
>>> I'm using an ATI video card, and got no nVidia gfx
>>> drivers on the system anywhere.
>>>
>>> Nick
>>>
>>> >-----Original Message-----
>>> >Hmm - not Nvidia video driver service? Do I recall that
>>> service causing
>>> >this error message? Perhaps the video driver rev
>>> changed with SP2?
>>> >
>>> >"Tom" <Use_Reply_To_Address@qxqx.net> wrote in message
>>> >news:Xns954A620D7A13Atomcog@207.46.248.16...
>>> >> "Jeffrey Randow (MVP)" <jeffreyr-
>>> support@remotenetworktechnology.com>
>>> >> wrote
>>> >> in news:ki58i0h4aac5ju1jfnfed4g66v1cc7movm@4ax.com:
>>> >>
>>> >>> I'll send this to the TS team at MS to see if they
>>> are seeing tech
>>> >>> support incidents on this, but I haven't been able to
>>> reproduce this
>>> >>> on ten machines I have tried...
>>> >>>
>>> >>> Getting this solved will involve someone who has this
>>> issue to open up
>>> >>> a support incident with either MS or your OEM.
>>> However, this may cost
>>> >>> $$$...
>>> >>>
>>> >>> Jeffrey Randow (Windows Networking & Smart Display
>>> MVP)
>>> >>> jeffreyr-support@remotenetworktechnology.com
>>> >>>
>>> >>> Please post all responses to the newsgroups for the
>>> benefit
>>> >>> of all USENET users. Messages sent via email may or
>>> may not
>>> >>> be answered depending on time availability....
>>> >>>
>>> >>> Remote Networking Technology Support Site -
>>> >>> http://www.remotenetworktechnology.com
>>> >>> Windows XP Expert Zone -
>>> http://www.microsoft.com/windowsxp/expertzone
>>> >>
>>> >> Yeah, I would have started a support incident long
>>> ago, but believe it or
>>> >> not, even though we pay close to 10K a year for
>>> our "campus agreement"
>>> >> (just for our one college on campus, since not college
>>> & deptartment
>>> >> wanted
>>> >> to pitch in), that yearly license doesn't include any
>>> free support.
>>> >>
>>> >> Anyway, I've been too busy to post any more info, but
>>> I've tried even more
>>> >> things, going back and forth from a pre-SP2 system
>>> restore point,
>>> >> uninstalling this, changing that, installing SP2, but
>>> nothing at all has
>>> >> worked yet. I've now ruled out ATI video drivers, as
>>> well.
>>> >>
>>> >> Also, it is hard, even for me, to discount Windows
>>> Firwall, despite the
>>> >> fact I do have the 3389 exception set and I can verify
>>> it with the netsh
>>> >> firewall commands. I even enabled logging on the
>>> firewall and you can see
>>> >> my client computer connecting and then it immediately
>>> (same second) drops,
>>> >> which is exactly what I'm seeing on the various
>>> clients I try to connect.
>>> >> Again, this error is a big mystery, because there is
>>> zero documentation I
>>> >> can find about what the root cause would be:
>>> >> "The remote computer has ended the connection."
>>> >>
>>> >> Now, Nick, who started this thread, says he can get it
>>> in with Safe Mode
>>> >> With Networking, but in normal mode he doesn't get any
>>> firewall log
>>> >> entries. It doesn't necessarily sound like we are
>>> experiencing the same
>>> >> problem, as he says his times out. My problem (and at
>>> least three others
>>> >> in the various newsgroups or have e-mailed me from my
>>> newsgroup postings,
>>> >> have said they are having a similar problem) is the
>>> fact I'm connecting
>>> >> literally for a split second and then being dropped,
>>> which my firewall log
>>> >> confirms.
>>> >>
>>> >> It might be strange, it might be obscure, it is likely
>>> something a handful
>>> >> of us are just doing - and note, I have a few other
>>> SP2-updated systems
>>> >> that do *not* have this problem, and no one else on
>>> campus has reported a
>>> >> problem, so I know there has to be some very specific
>>> circumstances behind
>>> >> it. Nonetheless, since SP2 still hasn't been widely
>>> deployed at all, I
>>> >> fully expect the number of incidents of this 'SP2
>>> kills Remote Desktop'
>>> >> problem to grow exponentially as thousands of XP Pro
>>> users install SP2
>>> >> over
>>> >> the coming weeks and months.
>>> >>
>>> >> - Tom
>>> >
>>> >
>>> >.
>>> >
>
One thing that I noted - if you enable Remote Desktop via the Group
Policy method, it will not automatically enable the port in the ICF...
Weird bug...
Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com
Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....
Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
On Tue, 31 Aug 2004 14:37:00 -0400, "Bill Sanderson"
<Bill_Sanderson@msn.com.plugh.org> wrote:
>Interesting. This shouldn't happen for most folks. I've installed SP2 on a
>number of machines--a dozen or so, via Remote Desktop and haven't seen this
>issue. These machines in the main had the SP1 firewall in place with RD
>opened.
>
>"Steven" <landsteven@gmail.com> wrote in message
>news:74497317.0408260606.1d9476bf@posting.google.com...
>> Are you sure you have Remote Desktop enabled? It turns out that this
>> was simply due to an ID10T error on my end. When XP SP2 installs it
>> disables the Remote Desktop setting in My Computer > Remote tab.
>>
>> I know I had RDP enabled and working before the install... so then I
>> after installed I assumed that that was still the case and that I was
>> having a Windows Firewall issue. I was wrong. Once I enabled Remote
>> Desktop again, everything works fine!
>>
>> <anonymous@discussions.microsoft.com> wrote in message
>> news:<ab7201c4889d$84ae1260$a501280a@phx.gbl>...
>>> I'm using an ATI video card, and got no nVidia gfx
>>> drivers on the system anywhere.
>>>
>>> Nick
>>>
>>> >-----Original Message-----
>>> >Hmm - not Nvidia video driver service? Do I recall that
>>> service causing
>>> >this error message? Perhaps the video driver rev
>>> changed with SP2?
>>> >
>>> >"Tom" <Use_Reply_To_Address@qxqx.net> wrote in message
>>> >news:Xns954A620D7A13Atomcog@207.46.248.16...
>>> >> "Jeffrey Randow (MVP)" <jeffreyr-
>>> support@remotenetworktechnology.com>
>>> >> wrote
>>> >> in news:ki58i0h4aac5ju1jfnfed4g66v1cc7movm@4ax.com:
>>> >>
>>> >>> I'll send this to the TS team at MS to see if they
>>> are seeing tech
>>> >>> support incidents on this, but I haven't been able to
>>> reproduce this
>>> >>> on ten machines I have tried...
>>> >>>
>>> >>> Getting this solved will involve someone who has this
>>> issue to open up
>>> >>> a support incident with either MS or your OEM.
>>> However, this may cost
>>> >>> $$$...
>>> >>>
>>> >>> Jeffrey Randow (Windows Networking & Smart Display
>>> MVP)
>>> >>> jeffreyr-support@remotenetworktechnology.com
>>> >>>
>>> >>> Please post all responses to the newsgroups for the
>>> benefit
>>> >>> of all USENET users. Messages sent via email may or
>>> may not
>>> >>> be answered depending on time availability....
>>> >>>
>>> >>> Remote Networking Technology Support Site -
>>> >>> http://www.remotenetworktechnology.com
>>> >>> Windows XP Expert Zone -
>>> http://www.microsoft.com/windowsxp/expertzone
>>> >>
>>> >> Yeah, I would have started a support incident long
>>> ago, but believe it or
>>> >> not, even though we pay close to 10K a year for
>>> our "campus agreement"
>>> >> (just for our one college on campus, since not college
>>> & deptartment
>>> >> wanted
>>> >> to pitch in), that yearly license doesn't include any
>>> free support.
>>> >>
>>> >> Anyway, I've been too busy to post any more info, but
>>> I've tried even more
>>> >> things, going back and forth from a pre-SP2 system
>>> restore point,
>>> >> uninstalling this, changing that, installing SP2, but
>>> nothing at all has
>>> >> worked yet. I've now ruled out ATI video drivers, as
>>> well.
>>> >>
>>> >> Also, it is hard, even for me, to discount Windows
>>> Firwall, despite the
>>> >> fact I do have the 3389 exception set and I can verify
>>> it with the netsh
>>> >> firewall commands. I even enabled logging on the
>>> firewall and you can see
>>> >> my client computer connecting and then it immediately
>>> (same second) drops,
>>> >> which is exactly what I'm seeing on the various
>>> clients I try to connect.
>>> >> Again, this error is a big mystery, because there is
>>> zero documentation I
>>> >> can find about what the root cause would be:
>>> >> "The remote computer has ended the connection."
>>> >>
>>> >> Now, Nick, who started this thread, says he can get it
>>> in with Safe Mode
>>> >> With Networking, but in normal mode he doesn't get any
>>> firewall log
>>> >> entries. It doesn't necessarily sound like we are
>>> experiencing the same
>>> >> problem, as he says his times out. My problem (and at
>>> least three others
>>> >> in the various newsgroups or have e-mailed me from my
>>> newsgroup postings,
>>> >> have said they are having a similar problem) is the
>>> fact I'm connecting
>>> >> literally for a split second and then being dropped,
>>> which my firewall log
>>> >> confirms.
>>> >>
>>> >> It might be strange, it might be obscure, it is likely
>>> something a handful
>>> >> of us are just doing - and note, I have a few other
>>> SP2-updated systems
>>> >> that do *not* have this problem, and no one else on
>>> campus has reported a
>>> >> problem, so I know there has to be some very specific
>>> circumstances behind
>>> >> it. Nonetheless, since SP2 still hasn't been widely
>>> deployed at all, I
>>> >> fully expect the number of incidents of this 'SP2
>>> kills Remote Desktop'
>>> >> problem to grow exponentially as thousands of XP Pro
>>> users install SP2
>>> >> over
>>> >> the coming weeks and months.
>>> >>
>>> >> - Tom
>>> >
>>> >
>>> >.
>>> >
>
Facebook
Twitter
Instagram