Re: VNC Problem

[David G. Miller (aka DaveAtFraud)]

Gene Lapointe"  wrote:
> In my xstartup file, i also had this line
> > > [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup.
> > My xstartup may have been carried forward from a previous release.  
> > Seems to work fine though.  The main thing is to comment out the 
> > xsetroot, vncconfig, and xterm entries.  These won't affect just getting 
> > things working but the default is minimal.
>
> Ok, we're getting somewhere.  /etc/vnc/xstartup doesn't exist.

If /etc/vnc/xstartup doesn't exist, [ -x /etc/vnc/xstartup ] && exec 
/etc/vnc/xstartup will fail and vnc won't work.  Try converting your 
.vnc/xstartup to use exec /etc/X11/xinit/xinitrc.  I've included my 
.vnc/xstartup below if you just want to drop a copy into ~/.vnc on one 
of your systems to see if it works for you.
> > > You might want to check that /etc/vnc/xstartup exists and is executable 
> > > by your VNC user (none of my systems with vnc-server installed have that 
> > > file).  If not, try using the relevant portion of the .vnc/xstartup I 
> > > provided instead.
> > >
> > > Cheers,
> > > Dave

~/.vnc/xstartup:

#!/bin/sh

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
# xsetroot -solid grey
# vncconfig -iconic &
# xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
gnome-session

VNC Problem

[Gene Lapointe]

I followed your instructions and tried from a machine within the local
network with the same failed to connect to server message.  I also
had shut the firewall completely off.
> Gene

Lapointe"  wrote:
> > In my xstartup file, i also had this line
> > >
>
> [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup.
> > > >
> > > My xstartup may have

been carried forward from a previous release.
> > > Seems to

work fine though.  The main thing is to comment out the
> > >

xsetroot, vncconfig, and xterm entries.  These won't affect just
> > getting
> > > things working but the default is

minimal.
> > >
> >
> > Ok, we're getting

somewhere.  /etc/vnc/xstartup doesn't exist.
> >
>
> If

/etc/vnc/xstartup doesn't exist, [ -x /etc/vnc/xstartup ] &&
exec
> /etc/vnc/xstartup will fail and vnc won't work.  Try

converting your
> .vnc/xstartup to use exec

/etc/X11/xinit/xinitrc.  I've included my
> .vnc/xstartup below if

you just want to drop a copy into ~/.vnc on one
> of your systems

to see if it works for you.
> > > > You might want to check

that /etc/vnc/xstartup exists and is
> > > executable
> > > > by your VNC user (none of my systems with vnc-server

installed have
> > > that
> > > > file).  If

not, try using the relevant portion of the .vnc/xstartup I
> > > > provided instead.
> > > >
> > > > Cheers,
> > > > Dave

~/.vnc/xstartup:
> #!/bin/sh
>
> #

Uncomment the following two lines for normal desktop:
> unset

SESSION_MANAGER
> exec /etc/X11/xinit/xinitrc

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
> #

xsetroot -solid grey
> # vncconfig -iconic &
> # xterm

-geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> gnome-session
>
> --

Politics, n. Strife of interests masquerading as a contest of
principles.
> -- Ambrose Bierce
>
> --

fedora-list mailing list
> [e-mail]
> To

unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>

VNC Problem

[Gene Lapointe]

Ok, so on fedoraforum.org, i was told to spit out the results of
iptables -L so here it is.

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
RH-Firewall-1-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
RH-Firewall-1-INPUT  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain RH-Firewall-1-INPUT (2 references)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     icmp --  anywhere             anywhere            icmp any 
ACCEPT     esp  --  anywhere             anywhere            
ACCEPT     ah   --  anywhere             anywhere            
ACCEPT     udp  --  anywhere             224.0.0.251         udp
dpt:mdns 
ACCEPT     udp  --  anywhere             anywhere            udp
dpt:ipp 
ACCEPT     tcp  --  anywhere             anywhere            tcp
dpt:ipp 
ACCEPT     all  --  anywhere             anywhere            state
RELATED,ESTABLISHED 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:ftp 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:smtp 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:ssh 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:https 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:http 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:vnc1024 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:5902 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:60851 
ACCEPT     udp  --  anywhere             anywhere            state NEW
udp dpt:60851 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:imap 
ACCEPT     tcp  --  anywhere             anywhere            state NEW
tcp dpt:pop3 
ACCEPT     udp  --  anywhere             anywhere            state NEW
udp dpt:xdmcp 
REJECT     all  --  anywhere             anywhere            reject-with
icmp-host-prohibited

I was also told to try to connect tcpdump port 5902 to see if anythings
getting there.  but it showed nothing.

On Tue, 2007-04-03 at 10:28 -0400, Gene Lapointe wrote:
> I followed your instructions and tried from a machine within the local
> network with the same failed to connect to server message.  I also had
> shut the firewall completely off.
> > Gene Lapointe"  wrote:
> > > In my xstartup file, i also had this line
> > > > > [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup.
> > > > My xstartup may have been carried forward from a previous
>
> release.
> > > > Seems to work fine though. The main thing is to comment out the
> > > > xsetroot, vncconfig, and xterm entries. These won't affect just
> > >
> > > getting
> > > > things working but the default is minimal.
> > >
> > > Ok, we're getting somewhere. /etc/vnc/xstartup doesn't exist.
> >
> > If /etc/vnc/xstartup doesn't exist, [ -x /etc/vnc/xstartup ] && exec
> > /etc/vnc/xstartup will fail and vnc won't work. Try converting your
> > .vnc/xstartup to use exec /etc/X11/xinit/xinitrc. I've included my
> > .vnc/xstartup below if you just want to drop a copy into ~/.vnc on
>
> one
> > of your systems to see if it works for you.
> > > > > You might want to check that /etc/vnc/xstartup exists and is
> > > >
> > > > executable
> > > > > by your VNC user (none of my systems with vnc-server installed
>
> have
> > > > that
> > > > > file). If not, try using the relevant portion of
>
> the .vnc/xstartup I
> > > > > provided instead.
> > > > >
> > > > > Cheers,
> > > > > Dave
> >
> > ~/.vnc/xstartup:
> >
> > #!/bin/sh
> >
> > # Uncomment the following two lines for normal desktop:
> > unset SESSION_MANAGER
> > exec /etc/X11/xinit/xinitrc
> >
> > [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
> > # xsetroot -solid grey
> > # vncconfig -iconic &
> > # xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> > gnome-session
> >
> > --
> > Politics, n. Strife of interests masquerading as a contest of
>
> principles.
> > -- Ambrose Bierce
> >
> > --
> > fedora-list mailing list
> > [e-mail]
> > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
> -- 
> Gene Lapointe
> [e-mail]
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list