Windows 10: Windows 10 BSOD When Connecting to RDP

Hi we have a client that is receiving a BSOD when attempting to connect to a RDP session it blue screens with the error apc index mismatch win32kfull.sys. We have attempted to do Windows updates and update drivers. The only driver we did not update was the intel management interface firmware driver. The minidump files should be attached. Thanks in advance for any advice!

:)

 

RDP not allowing remote connection

I had it working perfectly fine the other day but I logged into my server, removed a open port and both computer quit.

I run the computers with the firewall off, I see no point in them being on, it's a windows firewall a hacker will know how to get around so fire wall is OFF.

Ports are 9000 for server and 3390 for htpc

ip:9000
ip:3390

This does not work from a linux workstation using 'Remote Desktop Client'

It does not work from mac RDP
It does not work from windows RDP
And it does not work from my iphone.

I know it's enabled as I can RDP into the computers at my home (except htpc at the moment, I think that one needs restarted)

Ports are open, both tcp / udp ports are open using the internal server IP wich is MAC assigned by the router. Server - 10.0.1.2 - 9000
And same thing for the htpc - 10.0.1.8 - 3390

Besides the obvious of firewall, ports, and 'remote connection enabled' any ideas?

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

RDP and Network Connection Drops While on Ethernet

Sam,

1. Even without issuing the ping -t command I will experience a RDP drop and network bottleneck
2. RDP clients are the same version
3. No firewall setup
4. All connecting with the same cables from similar ports

winbox1 has full duplexTrue
winbox2 does not have duplex True

Pretty sure it's something with the network setup, I might reinstall the OS