I've recently setup XRDP on my Ubuntu Workstation (11.04, Gnome). XRDP works just fine when I have it set to the default RDP port (TCP 3389) or customly set to a higher port number (i.e. TCP 7432). I've noticed when I try to change it to a lower-numbered port (i.e. TCP 110), the XRDP process dies. The XRDP-sesman process remains functional. Does anyone have any insight why this may be the case?
My only consideration would be to step through the source code and make a (hopefully) minor modification and re-compile.
was wondering if there is an alternative method to using udev rules in order to get access to the USB serial ports. Is there a command to check the names and give them to you? I'm looking for something along the lines of "ttyUSB".
I am doing this as a test for bigger deployment. I have Apache running on CentOS5 in a clean VM (just a few tools installed, PHP and such).If mod_ssl is set to listen on 443 in /etc/httpd/conf.d/ssl.conf the the site at https://192.168.1.137 loads just fine.If I change the listen port to eg. 9443 in ssl.conf and reload httpd the page wont load athttps://192.168.1.137:9443 - I set the eth0 to be trusted and disabled SElinux in case that was interfering but still no luck.
I've setup my own repository which I want to use SSH as the protocol. I managed to get everything working with an SSH key using port 22. Now, I would like to change the SSH port. I've already changed it on the SSH/repo server. Now I can't figure out how to change apt to use a custom port on the client computer.
My sources.list file line which worked over port 22: deb ssh://user@1.1.1.1/home/user/repo lenny main contrib non-free I've tried: deb ssh://user@1.1.1.1:12345/home/user/repo lenny main contrib non-free and it fails and actually says "failed connecting to port 22"
Can this be done? I've searched google for hours and I getting nothing but unrelated data. I've read the man pages. The man page for apt.conf specified that you can set the port this way for HTTP, but doesn't mention anything about ssh ports.
I want to do a simple port redirect, i.e. whatever comes trough whatever interface on port AAAA will get redirected to port BBBBI thought that iptables -t nat -I PREROUTING --source 0/0 --destination 0/0 -p tcp --dport AAAA -j REDIRECT --to-ports BBBBhowever it doesn't work, e.g. nc -v -w2 -z localhost AAAA gives:
nc: connect to localhost port AAAA (tcp) failed: Connection refused while nc -v -w2 -z localhost BBBB
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?
I installed ubuntu server 10.04 32-bit and I installed XRDP so I can connect to it using RDP sessions. I was wondering if there is a better alternative to it. I have the following issues with it: 1. When I connect to the server locally using rdp it works just fine the first time. Then when I close the session I cannot connect to it again (it says connection timed out). Then if I uninstall then reinstall it will work again for another time then do the same thing. 2. I receive a protocol error when using Windows 7 or RDP version 6.1.7600 (Newest RDP version)
I was looking for good way to remote login into my computer. VNC wasn't good because it causes problem to run before logging into gnome. XRDP haven't got such problems, BUT i can login only once. I mean, that after rebooting computer and login remotely via rdp, and logging off on remote session, i cannot log in again. Client application stucks on message "sending info to sesman".
I am new to ubuntu. I hava a headless ubuntu machine. Had aa virgin installation of 10.04. Installed xRDP. Login to the ubuntu box through XRDP is successful. But while I login through XRDP, USB memory devices, or the windows XP partition, dont get mounted (even though it gets detected..snapshot attached). It woks fine when I login directly through console.
Is there anyway the mounting can be authorized while connecting through XRDP
While connecting over Xrdp, hitting the "D" key alone hides all my windows and shows the desktop. This is problematic since I often wish to type words containing at least one "D" in it. In case anyone else is having this problem, I've wrestled through it and offer this help.I'm using Ubuntu 10.10 Maverick Meercat and connecting via Xrdp. I only have this problem when connecting remotely.
APPARENT CAUSEI don't pretend to know for sure, but the problem appears to be that the remote connection is flubbing Metacity's "<Super>d" binding for the "show desktop" command. More precisely, the string "<Super>" doesn't appear to be functioning for me. If I change <Super> to <Ctrl>, I can use Ctrl + D to show desktop, and I can then type the letter D without it hiding every window from me.
Further evidence <Super> isn't working for me, if I change Metacity's "panel_run_dialog" global key binding from "<Alt>F2" to "<Super>F2" I bring up the run dialog by hitting F2 alone.
WORKAROUNDChange the system's "show desktop" keystroke. Here are the steps.
1) Alt+F2 2) gconf-editor 3) /->app->metacity->global_keybindings 4) Change the assigned keystroke for show_desktop from "<Super>d" to "<Ctrl>d" or "<Ctrl><Alt>d" or "disabled"
If someone finds this worthy of submitting a bug ticket, please let me know so I can follow it.
I am trying to enable rdp server on my ubuntu machine. I installed xrdp using apt-get, but when I try to connect (setting protocol to sesman-X11rdp) it authenticates, but dies with the error "only supporting 8 and 16 bpp rdp connections".
I recently installed the XRDP server on my desktop edition of Ubuntu v10.04 following the simple instructions available here. I did this on two computers. One computer has Firestarter installed while the other does not.
When I use Windows to connect to the Ubuntu box without Firestarter, everything works just fine. However, when I try to connect to the one running Firestarter, I get a pop up showing an error message (see the attached file).
I checked the incoming rules in Firestarter and I don't see a way to add RDP sessions to the list of exceptions. I also tried adding my IP address in the host section but this too didn't help the situation.
I can log into my Debian 8 Jessie XFCE server via XRDP from Windows 7 and can do everything I could normally do if I was using the machine. The only problem is the Network Manager, it states I have no connection. It doesn't display connection information, even states that there is no connection (even though I am remotely connected to it from my Windows machine, can install software and can access the Internet on the machine in question). This isn't a problem as it seems I can access anything regardless, the only thing I can not access is the Network Manager which I need access to so I can connect to my VPN.
I can access the Network Manager if I use the machine but as soon as I go headless and XRDP into it, I no longer can.
I've been racking my brain over this for days, trying to read up on as much as I can about the issue but am still struggling to find a solution. Unfortunately this must be done via a GUI.
I didn't change any settings, but now I get login failed.I checked the password and I using the correct pasword.for the first account I used when installing openSUSE I get past the login but then the rdesktop client hangs and then closes whit the incomplete message "error: did not receive a reply. possible causes include.."the other account I created doesn't accept the password.I checked /var/log/xrdp-sesman.log and it was empty.
I am helping a local genealogy society set up their research center. They want three workstations and a single data server. The genealogy program of choice was GRAMPS, which I have used for years a Wonderful program! No data is going to be input on the workstations the users are simply researching existing data on the server.
Since several RDP-based Wyse thin client units were available for free as were monitors and keyboards, the decision was quickly made to use an RDP based client/server system. Using VNC was unacceptable due to its speed and latency issues, plus, it isn't supported by the Wyse thin client units ONLY RDP and Cytrix.
Using Microsoft's server OS and Terminal Server package was far, far beyond the society's budget. We briefly considered equipping a Windows XP box with a copy ThinSoft's RDP server package, WinConnect Server XP, but its $300 price tag was still too much for the society.
The decision was to use Linux for the server. At first we considered LTSP but it is oriented towards PXE net boots and, while this may have worked, its complexity scared us off and we opted for what, we initially thought, was a much simpler solution XRDP.
We were right and wrong at the same time. It is simple to set up very simple, but the lack of documentation places many pitfalls in front of you, PLUS the solution is distribution dependent.
I spent many hours on this issue. There are numerous sources on the web citing solutions to running XRDP. Unfortunately, they all involve running vncserver against the destination logins. This is NOT what we desired. We wanted to be able to boot up the host system but not login at all, yet still be able to connect to a session via RDP.
I tried numerous distributions and eventually spending a lot of time going through the xrdp source code and planting out my own debug messages in /etc/xrdp/startsm.sh to output to a file in /tmp. Putting in ps -eS >> /tmp/xrdp.txt was particularly useful because it showed that xrdp/sesman DID launch an Xvnc, meaning that it was unnecessary to pre-launch vncserver, as most pundits recommend. The solution was figuring out how to connect to the Xvnc session created by sesman.
I discovered the solution somewhat by accident. It seems that the files created in the destination user's .vnc folder by vncserver were interfering with xrdp/sesman. Here is what worked. 1.Starting with a nearly virgin install of Ubuntu 10.04 beta 1, installed two users intended to be accessed for remote login via RDP. That is ALL that I did I never even logged into them. 2.My first entry xrdp.ini was unmodified except that ask was deleted from username=. Everything was unmodified.
3.Using tsclient on another machine, with the desired username, that was NOT logged in, and password pre-filled, I connected and received a nice Gnome desktop. 4.The session was on 5910. 5.While keeping this session active, I logged into the next login created for remote access and received my second nice Gnome sesktop on port 5911 automatically. Xrdp-sesman DOES automatically launch Xvnc in a useful way!
I can ONLY get this to work on Ubuntu version 10.04 e/w Gnome. It fails on CentOS 5.2, Xubuntu 9.10, SuperOS 9.10 and Lubuntu 10.04. In all cases xrdp was version 4.1.1, so the issue is not with xrdp/sesman it lies within the OS what, I do not know. I did not test KDE at all.
Code:
The system is running Ubuntu 10.04 LTS beta - the Lucid Lynx, amd64:
uname -a Linux ubu910 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux --------------------------------- Contents of /etc/xrdp/sesman.ini: --------------------------------- [Globals] ListenAddress=127.0.0.1
I am using xRDP to remotely log into my desktop. I have my user set up to use the classic no-effects desktop when logging into the console. Problem is, when I log in via xRDP, it uses unity. How do I tell the machine to use classic no-effects when using xRDP?
I have a mail server i need it to send message via port 587 not port 25, i make some changes to my postfix server which i use and it is already successed making a telnet to 587 port like it :
I am connecting to SuSE 11.1 from an XP workstation. The host is running XRDP xorg-x11-server-rdp-7.3.99-9.1, xorg-x11-server-dmx-7.3.99-42.1, xrdp-0.4.1-39.1 The client is running MS RDP 6.0.6x Generally, all is well. But Cut/Paste is not working outside of the XRDP session. I can Cut/Paste between apps in the XRDP session but not between the XRDP session and the client?
I am using XRDP 0.4.1-85.1 from here and I am having problems with the keyboard mapping from remote clients.After lots of looking at, I am stuck with this clue: if I run xev and type 1234, I see this (abridged) output:
I installed XRDP on my home machine, made sure the service was running, NAT'ed ports 3350 and 3389 TCP to the machine in my router and punched corresponding holes through Guarddog on these ports on the machine as well, but connecting with: rdesktop -f "my IP here" from my workplace doesn't work. I get "unable to connect".
I have a feeling, it's still the firewall. Do I need to tick permitting the rdesktop protocol in both the "local" and the "Internet" zone or do I need to also establish specific custom rules?
I've obtained the latest xrdp .rpm package (xrdp- .5.0-0.5.20090811cvs.el4.x86_64.rpm) installed it (rpm -ivh) and it installs fine. But when I start the xrdp service, xrdp starts but not the xrdp-sesman which in turn causes xrdp to immediately fail. Has anyone seen this? If so, what would be some good suggestions for a troubleshooting path?
Btw, the version for el5 works great on rhel 5, but the version for el4 consistently fails on rhel 4. The upgrade to 0.5.0 is necessary as rdp 7 for xp (and newer) breaks xrdp 0.4.1 with a protocol error.
Looking to install xrdp on my machine, but have not been able to do so. I have followed the directions that came with it, but the install command does not seem to work.
I have just upgraded my old work horse from 9.10 to 10.04 and on the surface everything looks ok. However there are a few annoying issues that I have not been able to resolved. One of these is an annoying auto shortcut that links the 'm' key to the Indicator applet while running my desktop inside an XRDP session (Windows Vista client). Everytime the m key is pressed, the focus is autotragically hijacked by the Indicator applet. Attempting to type any text from any application such as the terminal or text editor is excruciating since everytime the m key is pressed the focus jumped to the Indicator applet, the only way to disable this 'feature' is by removing the Indicator applet.
This problem is not seen in the native console, only in XRDP sessions.
There is another thread that deals with similar issue [URL] but only for users with Apple keyboards and does not apply to my situation.
I use XRDP alot so this affects me severely. How do I go about diagnosing this problem, xev doesn't even see any event when the m key is pressed, the focus just jumped to the Indicator applet?
Code: Select allroot@tom-deb:/home/user# apt-get install xrdp Reading package lists... Done Building dependency tree Reading state information... Done
[Code] ....
Now from windows using Remote Desktop connection, an attempt was made to connect remotely, I can see xrdp working just fine, but when I am logging into xrdp-sesmanx11 with the username and password, it exits out suddenly, are there other packages that need to be installed?
I just recently setup a OpenSUSE 11.3 server with Xrdp which I got from the 11.1 tutorial. Everything had been working great until yesterday I let the system run a update and now whenever I try to login I get login failed. When I look in xrdp-sesman.log file it says X server died. I've searched around for this problem and it seems there is some talk about it from a few years back but nothing as of recent and nothing that has worked so far. I'm kinda at a loss with this and really would like to get it up and running again.
I'm running debian 8.3 (kernel 4.1) on a BeagleBone black and writing a program with C# (vs2015) along with mono on the beagle. So far everything is working out great. What I'm trying to figure out now is how to make this setup run like a kiosk with it booting into my program with a graphical environment but with no actual desktop (just a blank screen). There will be an LCD showing the program but at the same time I want the program available through a remote connection.
I've got the blank desktop working via VNC but I think I should change to xrdp (the target users all have windows with remote desktop connection installed by default but what vnc is or have the permissions to install a vnc client).
Anyway, I think getting xrdp started with my program at boot will be pretty simple (famous last words?). I simply start the xrdp instance in rc.local then use the session script to start my program.
What I cant wrap my head around is not having two copies of my program running - one showing on the LCD using HDMI and the other running on a second desktop through xrdp...
To connect server use mstsc.exe in windows, rdesktop in linux - if you do not have it yum install rdesktop. But if you use different from english localasation of fedora, you will see only english Gnome and instead of your local fonts in terminal
[code]...
Now you can use fedora RDP session with your native language.
I installed the xrdp rpms as detailed by swerdna. I would like the pulldown menu to default to kde instead of twm. How can I change the configuration files to allow that.
