| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8
Comments:
<0> and that command will stop it
<1> ....I did an nmap localhost and vnc-http-1 , vnc-1 , X11:1 are open
<0> bah
<0> im wrong
<0> it is vncserver -kill :display#
<0> i knew there was a builtin command tho
<2> just kill the process and remove the pids in tmp
<1> i take risks screwing around with protocols i dont know about
<0> logan5: read the vncserver man page
<1> Can't tell if :display1 is on tux
<0> it tells you how to manage the processes
<1> so it will tell me how to end vnc-http-1, vnc-1, and X11:1 ?
<1> Can't tell if :display1 is on tux
<1> <-- what does that mean :O ?
<2> it means it's confused
<2> just kill the dam process (s) and then find their pids, you'll have to remove them in order to run it again
<3> yeah ..
<1> ill pkill vncserver etc ....
<1> znx: how can vnc be going if I ended ssh, i thought i was setting up tightvnc through an ssh tunnel :S
<1> I feel vulnerable :P
<2> vnc is a service, if you exit from the ssh service the vnc service is still running
<2> vnc over ssh is secure
<2> but you should have the 'standard' vnc ports (listening) blocked on iptables
<2> vnc over ssh doesnt care what port you use as long as you stipulate it
<1> is there a way i can check iptables to see if the standard vnc ports are blocked
<2> sure
<2> do this
<2> netstat -an |grep tcp
<2> paste that on paste.linux-noob.com
<2> then do this
<2> iptables -L
<2> paste that on paste.linux-noob.com
<2> ***uming you are using fedora
<2> ;)\
<1> Er
<1> http://paste.linux-noob.com/index.php?query=1126 Check it
<1> Did you see 205.210.145.3:6667, what's all that about
<1> Nevermind -
<3> Logan5: 6667 = irc :)
<3> the others are services... see the LISTEN
<3> also: netstat -altp
<4> bored!
<4> znx!!
<3> :)
<4> give me someting to doo
<3> speak to kutz
<4> kutzooi: hiya babe!
<1> 3 Xvnc's open! ports 5801 5901 6001 :(
<4> :(
<1> I guess I opened them 3 times...
<3> hello kutz
<5> :o)
<3> kutzooi: znx or square?
<5> the answer lies in the stars
<5> Bugger off there and find it.
<3> kutzooi: the answer isnt there!
<4> im going to code a c# irc bot!
<4> thx znx :P
<3> lol
<2> here's square's bot in action
<2> [bot] test
<4> here we go..
<1> znx: I'm mainly going to be 'vnc'ing' to my linuxbox through winBox
<2> * [bot] quit, connection reset by c#
<4> heh, that took time :P
<2> i had to type in the dark
<2> cant see my keyboard
<4> heh get a ligh
<2> and finding that #
<2> rocking sebbie to sleep
<2> now hes asleep
<4> znx, invite me to j00 ch4n
<3> hrmm?
<4> gimmie ya damn keys
<3> square: ..
<1> ok im gonna try and vnc to my machine through my winbox with PuTTy
<2> Logan5: if you succeed, please post how you did it on linux-noob.com
<2> thanks
<3> square: stop teasing me :((
<1> webany: is that a joke :P ?
<6> w000t i got my name from 1996 back
<6> finally
<6> only took 10 years
<6> lol
<3> "ping timeout"
<3> oops
<1> i tried 'vncviewer -quality 5 myip:1 and I keep getting ERROR: can't open display!
<1> through PuTTy on my winbox
<6> logan dont do it as root
<1> I didn't
<5> no, *I* didn't
<4> sec
<1> Lol
<6> try myip:2
<4> had to pop out
<1> I tried myip:4 :P
<6> or on the server type netstat -na
<6> and see what port
<6> actually do netstat -lvanp
<6> and it will tell you what port vncserver is on
<6> 5901 = myip:1
<6> 5902 = myip:2
<6> and so on
<1> znx: I found the pid! :D pkill Xvnc
<1> Jer: earlier on I was nmapping localhost and I saw vnc-http-1 and vnc:1 and X11:1 it was creepy
<1> however I did vnc to my box On the box --
<1> Jer: thanks for that command netstat -lvanp
<6> np
<7> PCBSD# pico named.conf
<7> /usr/local/bin/pico: Input/output error.
<7> wat the hell would couse this
<6> us vi
<6> use vi
<6> and recompile a new pico
<6> or obtain one from the package management system
<2> vi rocks
<6> it does
<1> when I *vncserver* I get xauth: (argv):1: bad display name "tux:1" in "add" command
<7> well i don't think its pico
<2> pico and nano are for girls
<6> bbl
<7> cause it doesn't run my bind either
<7> my bind won't start
<6> create a new named.conf
<6> bbl
<7> i think it's time for a restart
<7> ::(
<1> when I restart I risk going into 800x600 resolution
<1> It's this little problem i have
<1> Following anyweb's 'how to vnc to another pc via SSH'
<2> you dont need to worry about the resolution
<2> you SPECIFY the resolution that the vncserver runs at
<8> hold on
<8> let me give you the one liners you need
<1> when I ssh -L 5902:localhost:5901 192.168.0.100 I get ssh: connect to host 192.168.0.100 port 22: Connection refused
<8> dude I just got home from a dinner party
<1> I'm not worried about the rez :P
<8> vncserver :64 -geometry 1024x768 -depth 24 -name vnc -localhost
<8> then
<1> Sh4dowcat: i'll be doing this through a winbox with PuTTY
<8> vncviewer -via <destination> localhost:64
<8> putty eh?
<1> from school and stuff
<8> http://www.vanemery.com/Linux/VNC/vnc-over-ssh.html
<8> read
<8> **vnc
<9> Wish i knew, Sh4dowcat
<1> Heh,when I input vncserver :64 -geometry 1024x768 -depth 24 -name vnc -localhost I get Xauth argv:1: bad display name "tux:64 in "add" command n
<8> **vnc is <reply> http://www.tightvnc.com/ | For tutorial, see http://www.vanemery.com/Linux/VNC/vnc-over-ssh.html
Return to
#linux-noob
or
Go to some related
logs:
#red
CS SOurce Bunny hop script
#stocks
#beginner
#politics
corection en maimi
gelato wont use gpu
civil war info what did soliders do in thier off time
#gentoo
#flash
|
|