search for: 5902

...ed. That is, if the old "colon" separator is used, or the "slash" separator is used. The man page implies that if you use the alternative (slash) syntax, the square brackets may be omitted. This is tested on several OS and versions of OpenSSH: Ubuntu Server 9.10 ssh -v -6 -L 5902/::1/5902 host.example.com OpenSSH_5.1p1 Debian-6ubuntu2, OpenSSL 0.9.8g 19 Oct 2007 Bad local forwarding specification '5902/::1/5902' Gentoo Linux ssh -v -6 -L 5902/::1/5902 host.example.com OpenSSH_5.2p1, OpenSSL 0.9.8l 5 Nov 2009 Bad local forwarding specification '5902/::1/5902'...

...to see if anything helps clear it all up. I acutally installed x windows system and 'desktop' groups since that is what worked with my ipmi card. I installed tigervnc-server as root, ran vncpasswd as root, got a password. started/stopped just like it said to, so far so good. opened port 5902 -A INPUT -m state --state NEW -m tcp -p tcp --dport 5902 -j ACCEPT in /etc/sysconfig/vncservers I added root and had to take out "-localhost" or I could never connect via vncviewer, completely blocked unless both were taken out. I imagine there is some setting somehow in vncviewer but...

...nd on the web is for "tap" interface, and I can use "hostfwd" QEMU option if I use "user" interface. For the latter approach, I basically follow this one [1] with the QEMU cmdline option below: <qemu:commandline> <qemu:arg value='-net user,hostfwd=::5902-:5901'/> </qemu:commandline> But virsh always keep saying: error: internal error Process exited while reading console log output: kvm: -net user,hostfwd=::5902-:5901: invalid option What I am missing here? I also found there was a patch for user mode port forwarding [2]. Do...

...-server-4.1.2-9.el5.i386.rpm, so it SHOULD support IPv6. Don't know how to add a setting to the command-line, as I rund VNCserver via the service command, but I added it to /etc/sysconfig/vncservers: InTransports="IPv6" (note I also tried without the quotes) and netstat -na|grep 5902 shows vncserver only running on IPv4 and I can only connect to it via IPv4. So what am I missing?????

...y client. I have tried the client/server on both -4 and -6 on a port I have enabled on my firewall. The server looks to be listening, but the client seems to never connect. what I typed in eventually gets played to the terminal session and of course bash says no such command. Say I have port 5902 open (for vncserver, and vncserver is not running). So on server foo, in a su session (because of the port range) I type: nc -4l 5902 seems to be listening. Then on bar, also in an su session: nc -4 foo.domain 5902 hello world After some time nc terminates and "hello world" gets s...

...uuid ( RO) : 0409c60f-d209-1105-e884-9a25dd238430 name-label ( RW): vm001 power-state ( RO): running At this point it appears that everything is working but I don''t know what to do next. I tried the following to access via VNC % ssh -X -L 5901:127.0.0.1:5901 -L 5902:127.0.0.1:5902 -L 5999:127.0.0.1:5999 root@10.45.2.100 % xe vm-list uuid=0409c60f-d209-1105-e884-9a25dd238430 params=dom-id % xenstore-ls /local/domain/1/serial/0 limit = "65536" tty = "/dev/pts/2" vncterm-pid = "19363" vnc-port = "5901" With that i...

...rrors in the builds or installs. I foolwed the instructions in UPDATING. I believe I did an accurate merge of my named.conf file. This is a production machine, with paying customers -- please help! Thank you! -- Mike Lempriere- Home: mike@vintners.net Phone: 206-780-2146 Cellphone: 206-200-5902; text pager: mikelemp@tmail.com

OK, first time configuring vncserver on Centos7. I have read through a bunch of old messages here on vncserver and thought I had it. Obviously not. 1) cp /usr/lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver at .service 2) vi /etc/systemd/system/vncserver at .service I changed <USER> in both places to root 3) systemctl daemon-reload 4) systemctl

...lot = VIR_PCI_ADDRESS_SLOT_LAST; 361 ┆ break; But it works in qemu: # /usr/libexec/qemu-kvm -machine q35 -m 1024 -device pxb-pcie,bus_nr=250,id=pci.1,bus=pcie.0,addr=0x4 -device pcie-pci-bridge,id=pci.250,bus=pci.1,addr=0x0 -device pcie-pci-bridge,id=pci.251,bus=pci.1,addr=0x1 -spice port=5902,addr=0.0.0.0,disable-ticketing /var/lib/libvirt/images/q35.qcow2 So why pcie-expander-bus doesn't these two controllers? For any concerns in libvirt? Thank you~ -- Best regards, ----------------------------------- Han Han Quality Engineer Redhat. Email: hhan@redhat.com Phone: +861065339333

...after start. Aug 01 08:45:19 localhost systemd[1]: Failed to start Remote desktop service (VNC). Aug 01 08:45:19 localhost systemd[1]: Unit vncserver@:2.service entered failed state. Aug 01 08:45:19 localhost systemd[1]: vncserver@:2.service failed. =========== And yet, I am able to connect to 5902!? It is running. cat /root/.vnc/localhost:2.log shows: Xvnc TigerVNC 1.8.0 - built Apr 11 2018 21:04:25 Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11903000, The X.Org Foundation Wed...

Hello everyone: I tried following the instructions on this page to set up a VNC server: http://wiki.centos.org/HowTos/VNC-Server I can telnet to port 5901 from the machine itself: # telnet 127.0.0.1 5901 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. RFB 003.008 But, when I try to connect to it from the outside world, I get a connection timeout. My

Hi, I''m struggling with a simple problem and need some help. I have a remote XP laptop connecting with SSH to my linux firewall (RH9, kernel 2.6) and creating a tunnel to port 5995 on the firewall. So now traffic going from the laptop localhost port 5902 is tunnelled to my firewall port 5995. That''s working fine. On my local network I have an XP box I want to control with RealVNC 4. VNC viewer from the firewall to the XP box works fine. I''m trying to forward port 5995 on the firewall to host 192.168.2.101 port 5900 and can'&...

Actually it is running: netstat -tuln | grep 590 tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5903 0.0.0.0:* LISTEN tcp6 0 0 :::5901 :::* LISTEN tcp6 0 0 :::5902 :::* LISTEN tcp6 0 0 :::5903 :::* LISTEN Why 5901 and 2 are listening, I don't...

...692] channel.c: Avoiding initial deadlock for 'CAPI/ISDN1/141-721' Dec 6 10:13:02 DEBUG[5878] channel.c: Didn't get a frame from channel: SIP/741411-f7c1 Dec 6 10:13:02 DEBUG[5878] channel.c: Bridge stops bridging channels CAPI/ISDN1/141-722 and SIP/741411-f7c1 Dec 6 10:14:15 DEBUG[5902] channel.c: Didn't get a frame from channel: CAPI/ISDN1/141-723 Dec 6 10:14:15 DEBUG[5902] channel.c: Bridge stops bridging channels CAPI/ISDN1/141-723 and SIP/741411-4d0f Dec 6 10:14:34 DEBUG[2692] channel.c: Avoiding initial deadlock for 'CAPI/ISDN1/141-725' Dec 6 10:14:34 DEBUG[26...

I am needing to explicitly assign VNC ports to my virtual guests so that I can connect to them externally via a VNC client, and not virt-viewer. Since I will have multiple KVM Hosts with access to the same shared storage (to facilitate migrations) I need to ensure I have unique VNC ports assigned to each guest so that I don't overlap somehow. I had planned to use a range of ports starting at

...oper behavior ? Right, Marcel? > >> But it works in qemu: >> # /usr/libexec/qemu-kvm -machine q35 -m 1024 -device pxb-pcie,bus_nr=250,id=pci.1,bus=pcie.0,addr=0x4 -device pcie-pci-bridge,id=pci.250,bus=pci.1,addr=0x0 -device pcie-pci-bridge,id=pci.251,bus=pci.1,addr=0x1 -spice port=5902,addr=0.0.0.0,disable-ticketing /var/lib/libvirt/images/q35.qcow2 > It should be noted that QEMU in general allows users to make pretty > unwise device placement choices without so much of a warning, so I > would not take the above as proof the pcie-to-pci-bridge should be > allowed to p...

...''backend'', ''0'']]], [''device'', [''vfb'', [''type'', ''vnc''], [''uuid'', ''c06b4b87-739e-0e06-f4a3-6612dd45aa5e''], [''location'', ''localhost:5902'']]], [''device'', [''console'', [''protocol'', ''vt100''], [''location'', ''3''], [''uuid'', ''87bd6940-71c1-f8e1-1e02-2434dbbda9e2'']]]]) [2007-10-19 18:02:39 10...

Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. >From that point (but maybe it is

...libvirt/qemu/omnivision_1.agent unix 3 [ ] STREAM CONNECTED 39373 20587/qemu-kvm /var/lib/libvirt/qemu/VM_Orion-1.monitor 5) if I try to re-invoke test "/var/lib/libvirt/qemu/omnivision_1.agent" then : netstat -apn | grep qemu tcp 0 0 127.0.0.1:5902 0.0.0.0:* LISTEN 20587/qemu-kvm tcp 0 0 127.0.0.1:5902 127.0.0.1:57772 ESTABLISHED 20587/qemu-kvm unix 2 [ ACC ] STREAM LISTENING 39348 20587/qemu-kvm /var/lib/libvirt/qemu/VM_Orion-1.monitor unix 2...

..., [''device'', [''vfb'', [''vncunused'', ''1''], [''vnc'', ''1''], [''uuid'', ''e40219c2-a740-c910-2840-be3a2aaa9548''], [''location'', ''127.0.0.1:5902'']]], [''change_home_server'', ''False'']]) [2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:2543) XendDomainInfo.constructDomain [2010-07-01 12:06:49 5660] DEBUG (balloon:239) Balloon: 31107320 KiB free; need 16384; done. [2010-07-01 12:06:49 5660] DEBUG (Xe...