VNC Connecting issue in SUSE Linux Enterprise Server 12 SP4

[rahuljain257]

Hello Geeks,

I have created one the following instance on AWS (SUSE Linux Enterprise Server 12 SP4 (HVM), SSD Volume Type - ami-0c55353c85ac52c96
SUSE Linux Enterprise Server 12 Service Pack 3 (HVM), EBS General Purpose (SSD) Volume Type. Public Cloud, Advanced Systems Management, Web and Scripting, and Legacy modules enabled) I have installed XRDP & Gnome Desktop Envoirnment.
Also I have set the status as Active & Enable for XRDP in system system services. I have executed the below commands but still the not able to login into the system

Updated the SUSE installed Gnone & XRDP
zypper update ( to update SUSE Linux Ent. Server)
zypper install -t pattern gnome-basic
zypper install xrdp

Enable VNC Remote Login
# Open yast, Select "Network Services", Select first entry "Remote Administration with VNC"
# Enable service

Configure Window Manager to use Gnome
Edit file /etc/sysconfig/windowmanager
Change entry DEFAULT_WM="" to DEFAULT_WM="gnome

Startup the RDP service and make it start automatically after Reboot
service xrdp start
chkconfig --set xrdp on
systemctl start xrdp
systemctl enable xrdp

But I am getting the below error :

please wait, we now perform access control...
Reply rom access control: Success
Connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to session manager, please wait...
xrdp_mm_process_login_response: login successfull for display 200

VNC started connecting
Waiting 2000 ms for VNC to start...
VNC connecting to 127.0.0.1 6100
VNC error - problem connecting

I have referred this link https://answers.sap.com/questions/68...rver-12-s.html but no use.

regards,

Rahul Jain

[rahuljain257 · Accepted solution]

Hello Everyone, I was struggling again on this issue and found weird work-around to tackle this issue. Please find my solution & also please help me to undertand why we need to do this to connect on the linux server.

Screen-shot 1 [Color depth - 15 bit mode]

Screen-shot 2 [Color depth - 16 bit mode]

Screen-shot 3 [Color depth - 24 bit mode]

Screen-shot 4 [Color depth - 32 bit mode]

Note - After following the above steps, still it didn't worked then please re-start xrdp service & try again either using 2nd or 3rd screenshot.

Command 1 - Service xrdp restart.

I hope this will help some-one struggling on this issue. Also one last thing if this worked for some-one then please explain why we need to change the resolution to fix this problem.

Regards,

Rahul Jain

[former_member699105]

I've seen similar issues connecting from Windows to a SLES GUI. I'm using SLES v15, so my ideas are based on that version.

Yes, matching the color depth between the client and the server can be important, but my experience is that a mis-match is not guaranteed to cause the problem you're seeing.

If you have not already done so, try stopping the local firewall.

Also, the User ID under which you want to authenticate should be a member of the tsusers Group; unless /etc/xrdp/sesman.ini does not specify that for the TerminalServerUsers configuration item.

If you're still having problems, try increasing the logging level in the /etc/xrdp/sesman.ini file

Also, if you have not already done so, try modifying /etc/xrdp/xrdp.ini to include max_bpp=32. You can also crank up logging in that file as well.

Don't forget to restart the service after making any changes to the config.

[rahuljain257]

Thanks davebnc for sharing your experience, It will surely help some-one.

[NATPET]

Hi everyone,

Are you able to resolve this issue?

Regards,

Danish

[former_member606922]

Hi Rahul,

Try below

capture.jpg

[rahuljain257]

I have tried that too but didn't worked. . Let's c if this works for some-one else.

[former_member696482]

anyone solve this problem, can you explain this please?

best regards,

[ctplakash]

Hi Rahul,

Have you found solution ?

[MichaelTe]

Hello Rahul,

did you check/use the following option in YAST when activating VNC?:

- Allow Remote Administration With Session Management

Regards,

Michael

[rahuljain257]

Yes tried doing that setting as well but still the same error.