WinXP RDP success is version dependent

Hi,

I had no problems with Win7. Now I have two Win10 machines and one WinXP
Pro -32bit machine. I can RDP from WinXP into Win10 no problem But from
Win10 into WinXP I get blue screen. I also have virtual WinXP on each Win10
machine. I can RDP each virtual WinXP into the other. This leads me to
believe the bug is in Win10.
Comments?
Thanks

On Sun, 11 Mar 2018 00:45:59 -0800, Norm X wrote:

Hi,

I had no problems with Win7. Now I have two Win10 machines and one WinXP
Pro -32bit machine. I can RDP from WinXP into Win10 no problem But from
Win10 into WinXP I get blue screen. I also have virtual WinXP on each
Win10 machine. I can RDP each virtual WinXP into the other. This leads
me to believe the bug is in Win10.
Comments?
Thanks

It could be a bug but perhaps it is time to consider moving on from
Windows XP. It is an archaic OS that while it had its time to shine that
time has long since past.

On 3/11/2018 1:02 AM, wg_2002 wrote:
On Sun, 11 Mar 2018 00:45:59 -0800, Norm X wrote:

Hi,

I had no problems with Win7. Now I have two Win10 machines and one WinXP
Pro -32bit machine. I can RDP from WinXP into Win10 no problem But from
Win10 into WinXP I get blue screen. I also have virtual WinXP on each
Win10 machine. I can RDP each virtual WinXP into the other. This leads
me to believe the bug is in Win10.
Comments?
Thanks

It could be a bug but perhaps it is time to consider moving on from
Windows XP. It is an archaic OS that while it had its time to shine that
time has long since past.


Have you seen this discussion?

"For RDP from Windows 10 to Win XP you need to enable ping on Win XP.
By default it is disabled."

http://www.sysprobs.com/enable-ping-in-xp

https://answers.microsoft.com/en-us/...a-65474c1c061b

On Sun, 11 Mar 2018 00:45:59 -0800, "Norm X"
wrote:

Hi,

I had no problems with Win7. Now I have two Win10 machines and one WinXP
Pro -32bit machine. I can RDP from WinXP into Win10 no problem But from
Win10 into WinXP I get blue screen. I also have virtual WinXP on each Win10
machine. I can RDP each virtual WinXP into the other. This leads me to
believe the bug is in Win10.
Comments?
Thanks


Windows 10 *IS* the bug!

You'll never get me to use Win10.....

Norm X wrote:

I had no problems with Win7. Now I have two Win10 machines and one
WinXP Pro -32bit machine. I can RDP from WinXP into Win10 no problem
But from Win10 into WinXP I get blue screen.

You know which Windows platform crashed but you didn't tell us. Which
host crashed: your Windows XP host crashed (when RDP'ed from your
Windows 10 host) or your Winodws 10 host crashed (when RDP'ed from your
Windows XP host)?

You never identified what security software (anti-virus, anti-malware,
3rd party firewall, etc) you use on each host. Disable all security
software on both hosts and re-test. Some users reporting BSODs while
using RDP were memory corruption caused by drivers. It is very likely
your Windows XP and 10 hosts do not have identical hardware so their
drivers would be different, plus the drivers would be different because
of the different operating systems. Because RDP is buffering up the
screen, even a video driver could cause a conflict and crash. You could
check if you have the latest drivers on each host but sometimes the
latest is not the best. Sometimes you have to find a best suite of
drivers which could include using older driver versions. For example,
the latest video driver for my hardware means losing compatibility with
my old games and also losing some handy features (like a color palette
reset after a game crashes). You might also want to run memtest on both
hosts.

https://answers.microsoft.com/en-us/...3-c48669e4c983
"Driver verifier is a utility built into the OS (Vista, WIN 7, Win 8,
and win 10) that will often find the driver/drivers that are the
underlying cause of BSOD/Crashes"

I haven't used it (knock on wood) to know if it requires crash dumps be
enabled. You never mentioned if you attempted to review the BSODs or
what got reported in the BSOD screen. Did you ever look in the Event
Viewer (eventvwr.msc) to see if there was an error reported at the time
of the BSOD? Digging through crash dumps (assuming you actually have
dumping enabled) can be tough, so I use Nirsoft's BSOD viewer to help
decipher the dump (https://www.nirsoft.net/utils/blue_screen_view.html).
Doesn't require a full memory or kernel crash dump, just a minidump
(much smaller). Nirsoft's and other similar debugging tools can be
wrong in their analysis. The gold standard is to use Microsoft's own
debugging tool available at:

https://docs.microsoft.com/en-us/win...ed/adk-install

However, at that point, it's just too much work for me to debug the
crash. If changing the video driver (even back to an older one),
reducing startup programs, and looking for other programs that attempt
to buffer the screen, secure the host, or throttle the network didn't
work then I'd switch away from using RDP. In fact, I've only used RDP
when I was required (someone else's setup or requirement or 3rd party
solutions not allowed) or to play with it.

I also have virtual WinXP on each Win10 machine. I can RDP each
virtual WinXP into the other. This leads me to believe the bug is in
Win10.

RDP has caused BSODs in every version of Windows. You might want to
consider using something else, like a variant of VNC. RDP is a
Microsoft proprietary protocol so it works only on Windows. VNC is open
source and works on Windows and *NIX (except for UltraVNC which only
supports Windows).

https://www.xtontech.com/blog/rdp-vs-vnc-access/
https://en.wikipedia.org/wiki/Virtual_Network_Computing

For remote control software, including variants of VNC, see:

https://en.wikipedia.org/wiki/Compar...sktop_software

In the past, I've used VNC, RealVNC (Open edition is freeware),
TightVNC, and might've tried UltraVNC. Some others are mentioned in the
"See also" section in the above Wikipedia article. UltraVNC, TightVNC,
and RealVNC are usually the ones that get compared against each other.
RealVNC Open (free edition) is lacking many features in other VNC
variants and is not actively maintained. It's found under RealVNC's
archive site (https://archive.realvnc.com/download/open/). It's non-Open
(non-community) edition is payware and probably why I didn't bother
using it: lacking features in the freeware version, non-Open version is
payware, but they still base their protocol on VNC which is free.
TightVNC's graphics and performance can sometimes be more sluggish than
RealVNC; however, TightVNC is free for both personal and business use.
If you have an always-on high-speed Internet connection, you might not
experience any sluggishness. TightVNC seemed more stable than the other
two. UltraVNC has more features (encryption, file transfer, cut-n-paste
between remote and local hosts, a chat client, and NTLM authentication)
but that also makes it bloated if you don't use them, like all you want
in remoting software is remote control of a host. Although sometimes a
bit more buggy than the other two, UltraVNC seems to perform the
fastest. Both TightVNC and UltraVNC can be used for both personal and
business use. If you are using a VNC variant to support customers,
UltraVNC has its SingleClick (http://www.uvnc.com/products/uvnc-sc.html)
so customers don't have to pre-install UltraVNC for you to remotely help
them. They use the client but they don't install it (just delete the
downloaded file after the help session). TightVNC claims a low
bandwidth (slow connection) mode yet, in practice, it generated more
traffic in bytes than did RealVNC or UltraVNC. However, where TightVNC
is tight[er] is on its memory footprint. As I recall, I ended up using
UltraVNC but it's been many years since I last used a VNC variant to
remote to a host. Instead I moved to the following method which is
easier to setup and maintain. However, UltraVNC only supports Windows
so if *NIX hosts are involved then use TightVNC.

In addition, you can use other types of remoting software, like
TeamViewer, GoToMyPC, LogMeIn, or Mikogo. Except for LogMeIn (who quit
providing a free personal-use account), the others let you use their
service for free but only for personal use. Even then, they might have
quota limits on usage to ensure their freeloading users don't abuse
them. You never identified how or why you need remote access to your
different hosts. Could be for personal use. Could be you use them to
support others (which means your use is not personal use). Unlike a VNC
server listening for incoming connection requests which requires
punching holes in firewalls in routers along with redirection of inbound
connects on a port to a specific intranet host to support requests that
originate external to your intranetwork (both of which require access to
the remote host's router to configure its firewall and redirection)
along with setting up a DDNS (dynamic DNS) service (e.g., OpenDNS, NoIP)
to find the remote host by name instead of by IP address (which could be
dynamic which means it can change), these remoting tools work as clients
that make outbound connections via HTTPS, just like your web browser, to
check if requests came into their server. Firewalls won't block those
outbound connections; else, they'd also be blocking your web browser.
The server is only used for mediation between a host that accepts
inbound remote connection requests and the remote host that wants to
connect. Both use the server to identify each other but thereafter the
server passes the connection off to the endpoints (i.e., the server get
the two ends talking to each other and thereafter is no longer
involved).

On Sun, 11 Mar 2018 12:54:07 -0500, VanguardLH wrote:

RDP has caused BSODs in every version of Windows. You might want to
consider using something else, like a variant of VNC. RDP is a
Microsoft proprietary protocol so it works only on Windows.

I remember VNC being much slower than RDP on Win 7 and Win 10. I`m
using a lot of RDP on Win 7 and Win 10 and have not seen a BSOD (it
happened on XP, though).

RDP is available for Linux, some clients and a server:
http://www.xrdp.org

On 03/11/2018 06:50 AM, wrote:

[snip]

Windows 10 *IS* the bug!

Yes.

The purpose of Windows 8 is to make Windows 10 look good. It didn't work
very well.

BTW, I hadn't thought of that before, comparing Win 8 to "new Coke"
which some people say existed to hide the inferiority of "Coke Classic"
(which is NOT the real thing).

You'll never get me to use Win10.....

I still use Windows 7 (the last semi-good version) for anything
important requiring Windows. I still don't have any plans for when that
stops working.

On 2018-03-11, Michael Logies wrote:
RDP is available for Linux, some clients and a server:
http://www.xrdp.org

I've found the xfreerdp client to work well. I'm using it right now to connect
to a Windows 2012R2 server.

--
-----------------------------------------------------------------------------
Roger Blake (Posts from Google Groups killfiled due to excess spam.)

NSA sedition and treason -- http://www.DeathToNSAthugs.com
Don't talk to cops! -- http://www.DontTalkToCops.com
Badges don't grant extra rights -- http://www.CopBlock.org
-----------------------------------------------------------------------------

Sam E wrote:
On 03/11/2018 06:50 AM, wrote:

[snip]

Windows 10 *IS* the bug!

Yes.

The purpose of Windows 8 is to make Windows 10 look good. It didn't work
very well.

BTW, I hadn't thought of that before, comparing Win 8 to "new Coke"
which some people say existed to hide the inferiority of "Coke Classic"
(which is NOT the real thing).

You'll never get me to use Win10.....

I still use Windows 7 (the last semi-good version) for anything
important requiring Windows. I still don't have any plans for when that
stops working.

Windows 8.1 isn't too bad. Just don't use the silly tiled 'Metro' apps
and add the 'Classic Start Menu' and everything will be mostly like a
'normal' Windows version (FSSVO 'normal' :-)).

I will stay on 8.1 [1] as long as possible, unless Microsoft wises up
with 10, which is unlikely.

[1] I'm on 8.1, because I outgrew my Vista laptop and bought a new one
which came with 8.1, otherwise I would probably be on 7 as well.

On Sun, 11 Mar 2018 16:26:22 +0000, Good Guy
wrote:

On 11/03/2018 11:50, wrote:
Windows 10 *IS* the bug!

Or it could be that you are mentally challenged.

You'll never get me to use Win10.....

Nobody would waste time trying to make anybody with learning
difficulties to use Windows 10. The level of intelligence required to
use Windows 10 is well above that required to use Linux because Windows
10 users have to create something useful while Linux users are back-end
workers. Front liners are always Windows users.

I'd actually agree that using Windows 10 is actually a little more
complicated than using Linux nowadays. Linux detects your hardware at
installation and at startup, requires no additional security software
which can conflict with other software and updates all of your
software and drivers automatically. In comparison, Windows 10 is
harder since the same functionality requires additional software.

So yeah, you're right.

"Norm X"
news in alt.comp.os.windows-10, wrote:

Hi,

I had no problems with Win7. Now I have two Win10 machines and one
WinXP Pro -32bit machine. I can RDP from WinXP into Win10 no
problem But from Win10 into WinXP I get blue screen. I also have
virtual WinXP on each Win10 machine. I can RDP each virtual WinXP
into the other. This leads me to believe the bug is in Win10.
Comments?
Thanks




I'm sorry I can't help. I haven't experienced this issue. So far...


--
Don't become the next David Brooks cyberstalking victim!
Visit https://tekrider.net/pages/david-brooks-stalker.php (10/10 WOT)
to learn more. If you've already become a victim or know someone who
has, you can provide the following information to them, your lawyer,
local law enforcement, etc.
https://www.devon-cornwall.police.uk - His local police. Report?
David Brooks (BoaterDave)
Jersey Cottage 86 Granary Lane
Budleigh Salterton Devon EX9 6ER United Kingdom
Phone: 44-1395-443340 (H) 07974-193550 (M)
Email(s): ,

On 3/25/2018 4:41 PM, Diesel wrote:
"Norm X"
news in alt.comp.os.windows-10, wrote:

Hi,

I had no problems with Win7. Now I have two Win10 machines and one
WinXP Pro -32bit machine. I can RDP from WinXP into Win10 no
problem But from Win10 into WinXP I get blue screen. I also have
virtual WinXP on each Win10 machine. I can RDP each virtual WinXP
into the other. This leads me to believe the bug is in Win10.
Comments?
Thanks




I'm sorry I can't help. I haven't experienced this issue. So far...


In newer versions of windows, there's a check box in the RDP
setup to allow connections from less secure operating systems
try changing that.
I've also had issues between XP and win7/10 with the network.
Looks like it's there. Acts like it's there, but won't
transfer files. Dunno why, but sometimes, rebooting
the router fixes it.