Home / user-130763

J.Hudler's questions

Martin Hope
J.Hudler
Asked: 2022-01-20 12:30:33 +0800 CST
  • 1

The Issue:

Today I started receiving an error while connecting to an Azure hosted Windows 2022 Server that until recently (2 or 3 days ago) were connecting fine.

The symptom: the connection error occurs after authentication (filled still in the client app) and passing all the security checks phases. When the RDP screen is to be rendered (it is created but still all black), it gives the error.

Your Remote Desktop Services session has ended, possibly for one of the following reasons:

The administrator has ended the session.
An error occurred while the connection was being established.
A network problem occurred.

For help solving the problem, see "Remote Desktop" in Help and Support.

[Expanded Information]
Error code: 0x3
Extended error code: 0x11

Note that this error happens even when connecting inside the server host to self (using localhost or 127.0.0.1).

More Info:

The control to this server was handled to a technician who installed AnyDesk, and maybe it started some kind of conflict, but I'm not sure it is related.

Using Group Policy (gpedit.msc) all RDP settings related to Hardware Acceleration / RemoteFX optimizations / UDP connections were disabled, with no success.

Some (maybe) relevant Event Logs messages (I've translated them myself from pt-BR - ordered from last to first):

Info    103     The disconnection reason is 17
Info    72      Method interface call: GetServerAutoReconnectInfo
Info    72      Method interface call: GetServerAutoReconnectInfo
Info    72      Method interface call: DisconnectNotify
Info    72      Method interface call: SetErrorInfo(0x11)
Info    72      Method interface call: PreDisconnect(17)
Info    132     The rdpdr channel was connected between server and client using transport tunnel: 0.
Info    132     The Microsoft::Windows::RDS::Geometry::v08.01 channel was connected between server and client using transport tunnel: 0.
Info    132     The Microsoft::Windows::RDS::Geometry::v08.01 channel was connected between server and client using transport tunnel: 0.
Info    132     The Microsoft::Windows::RDS::Video::Data::v08.01 channel was connected between server and client using transport tunnel: 0.
Info    132     The Microsoft::Windows::RDS::Video::Control::v08.01 channel was connected between server and client using transport tunnel: 0.
Info    72      Method interface call: ConnectNotify(SessionId=1)
Info    162     The client offers support to version 0xA0400 of RDP graphics protocol, client mode: 2, AVC available: 0. Initial Profile: 2. Server: MyServer
Info    132     The Microsoft::Windows::RDS::Graphics channel was connected between server and client using transport tunnel: 0.
Info    132     The Microsoft::Windows::RDS::Telemetry channel was connected between server and client using transport tunnel: 0.
Info    72      Method interface call: OnReady
Info    72      Method interface call: OnConnected
Info    169     The client operating system type is (1, 0). Server: MyServer
Info    132     The rdpinpt channel was connected between server and client using transport tunnel: 0.
Info    33      The RDP protocol will be using RemoteFX guest module to connect to the client computer.
Info    132     The rdpgrfx channel was connected between server and client using transport tunnel: 0.
Info    66      The RDP-Tcp#0 connection was assigned to session: 1
Info    72      Method interface call: AuthenticateClientToSession
Info    135     The multitransport connection was completed for tunnel: 3. The transport type was defined as TCP: Reason Code: 2 (Forced by Server Configuration).
Info    135     The multitransport connection was completed for tunnel: 1. The transport type was defined as TCP: Reason Code: 1 (No Client UDP Support).
Info    100     The server confirmed the client multi-transport feature.
Info    98      The TCP connection was successfully established.
Info    72      Method interface call: ProtocolComplete
Info    72      Method interface call: SendClientLicense
Info    72      Method interface call: GetSecurityFilterCreds
Info    71      The RDP-Tcp#0 connection uses video driver RDPUDD.
Info    104     The client timezone is [-3] UTC Time 
Info    72      Method interface call: AcceptConnection
Info    72      Method interface call: OnStartLicensing
rdp windows-server-2022
Martin Hope
J.Hudler
Asked: 2021-01-21 04:18:37 +0800 CST
  • 1

In a samba share we have a directory with lots of files - binaries and resources to run our ERP application (around 20K entries).

The application is taking too long to load. The found reason is that the application tries to load several files in a trial/error fashion, looking for extensions in a particular order (e.g: file.dll, file.lbr, file.gnt, file.int). Many of these files are not required and doesn't even exist.

Every "not found" hit take ~0.2 seconds. And there are lots of these events.

The thing is that apparently samba is not caching this result.

If I run this code (in a Windows Command Prompt) in the samba share, it takes considerable time, whereas in a native Windows share it is instantaneous.

  for /L %i in (1,1,50) do @dir \\server\share\not_existing.txt >nul

Anything that can be done?

Current smb.conf content:

# Global parameters
[global]
    netbios name = ***omitted***
    realm = ***omitted***
    server role = active directory domain controller
    workgroup = ***omitted***
    idmap_ldb:use rfc2307  = yes
    dns forwarder = ***omitted***
    vfs objects = acl_xattr
    map acl inherit = yes
    store dos attributes = yes
    # 
    aio read size = 1
    aio write size = 1
    aio write behind = true
    socket options = TCP_NODELAY SO_RCVBUF=65535 SO_SNDBUF=65535
    read raw = yes
    write raw = yes
    max xmit = 65535
    dead time = 0
    getwd cache = no
    max connections = 5000
    time server = yes

Environment Details:

  • CentOS Linux release 7.6.1810 (Core)
  • Samba version 4.8.3
  • Application Runtime: Microfocus NetExpress (Cobol) v3.1
centos samba
Martin Hope
J.Hudler
Asked: 2012-08-03 11:26:35 +0800 CST
  • 1

Considering the built-in 'Backup Database' script (backup.bat) that comes with a new instalation of the Oracle Express 11g Edition, after finishing the script execution, what folders/files should be copied to an external media ('XCOPY' Backup) so the database could be fully restored the database after a new install?

Environment:

  • Windows Server 2003
  • Database is in ARQCHIVELOG
  • Datafiles/Tablespaces are set-up as default (user data is being allocated in USERS Tbs)

Edit:

I have a guess that the folder [InstallDir]\oraclexe\app\oracle\fast_recovery_area should contain all of what I need, but I'm affraid it isn't enough.

backup