Subframe: 0
BCCH-BCH-Message
message
dl-Bandwidth: n50
phich-Config
phich-Duration: normal
phich-Resource: one
systemFrameNumber: {8
bits|0x17}
spare: {10 bits|0x0000|Right
Aligned}
http://www.ee.columbia.edu/~roger/ShmooCon_talk_final_01162016.pdf
BCCH-BCH-Message
message
dl-Bandwidth: n50
phich-Config
phich-Duration: normal
phich-Resource: one
systemFrameNumber: {8
bits|0x17}
spare: {10 bits|0x0000|Right
Aligned}
http://www.ee.columbia.edu/~roger/ShmooCon_talk_final_01162016.pdf
and then, while you're in the midlea .
How to restart RDP without rebooting windows
WARNING: Test this process before you try it on an production system, to make sure you like the results and have the process down.
Problem:
RDP has stopped working but your server still work just users can’t connect to modify applications
The most common fix is to reboot windows, because “Remote Desktop Services” aka TermService can’t be restarted at least thats the case on 2003 as the option is grayed out. This will also create an outage just for a remote control issue and thats not always desirable.
The fix: (remotely)
from command line
- tasklist /s \\servername /svc /fi “imagename eq svchost.exe” (locate PID for TermService)
- taskkill /s \\servername /pid xxxx (may need /f to force, UAC might give problems as well)
- sc \\servername start TermService
The Fix: (local, using remote admin card/other remote control software/other remote command line)
From command line
- tasklist /svc /fi “imagename eq svchost.exe” (locate PID for TermService)
- taskkill /pid xxxx (may need /f to force, UAC might give problems as well)
- sc \\servername start TermService
more helpful RDP troubleshooting
No comments:
Post a Comment