headers
William Liporace | 1 Jan 2007 18:47
Picon

SuSE 10.2 & TightVNC


Does any one have tight VNC working? I get the grey screen and have not
had any luck using it...

Will

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Permalink | Reply | 9 comments |
headers
William Liporace | 1 Jan 2007 19:54
Picon

Re: SuSE 10.2 & TightVNC

I can not even connect to my PC from another PC in my own home... 

On Mon, 2007-01-01 at 12:10 -0600, Ron Reed wrote:
> Will, it's working great for me.  I created a Virtual Private Network
> utilizing Hamachi
> to work around any firewall or router issues.  Feel free to email me
> directly if you have any questions. 
> 
> Ron
> 
> 
> 
> On 1/1/07, William Liporace <will.na2na <at> gmail.com> wrote:
>         
>         Does any one have tight VNC working? I get the grey screen and
>         have not
>         had any luck using it...
>         
>         Will
>         
>         
>         -------------------------------------------------------------------------
>         Take Surveys. Earn Cash. Influence the Future of IT 
>         Join SourceForge.net's Techsay panel and you'll get the chance
>         to share your
>         opinions on IT & business topics through brief surveys - and
>         earn cash
>         http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>         ___________________________________________________________
>         TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
(Continue reading)

Permalink | Reply | 3 comments |
headers
Frank Bax | 1 Jan 2007 21:13
Picon
Favicon

Re: SuSE 10.2 & TightVNC

Did you modify firewall settings yet?  Default firewall does not allow 
"remote admin" (SuSE terminology for TightVNC).

At 01:54 PM 1/1/07, William Liporace wrote:

>I can not even connect to my PC from another PC in my own home...
>
>
>
>On Mon, 2007-01-01 at 12:10 -0600, Ron Reed wrote:
> > Will, it's working great for me.  I created a Virtual Private Network
> > utilizing Hamachi
> > to work around any firewall or router issues.  Feel free to email me
> > directly if you have any questions.
> >
> > Ron
> >
> >
> >
> > On 1/1/07, William Liporace <will.na2na <at> gmail.com> wrote:
> >
> >         Does any one have tight VNC working? I get the grey screen and
> >         have not had any luck using it...
> >
> >         Will

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
(Continue reading)

Permalink | Reply | 2 comments |
headers
William Liporace | 1 Jan 2007 22:54
Picon

Re: SuSE 10.2 & TightVNC

I have even gone the point of disabling the firewall from the linux box.
The system will allow me to connect with a xxx.xxx.xxx.xxx:01
xxx.xxx.xxx.xxx:02 and etc, but I can not connect using xxx.xxx.xxx.xxx
or xxx.xxx.xxx.xxx:00. When I do connect, all I get is a grayish screen
and I do see a graphical X (for a better discription) that moves with my
mouse. I have tried RealVNC Viewer and TightVNC viewer.

Will

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Permalink | Reply | 1 comment |
headers
Michael D. Setzer II | 2 Jan 2007 03:10

Re: SuSE 10.2 & TightVNC


I would suggest check the xstartup file in the .vnc directory.
On Fedora, I would get a simiar Screen with the X for the mouse pointer.

The xstartup on Fedora has two lines to uncomment.
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc

I remove the # from those two lines, and save the file. Then restart the vnc 
server. Not sure if suse has the same thing. 

On 1 Jan 2007 at 16:54, William Liporace wrote:

Subject:        	Re: SuSE 10.2 & TightVNC
From:           	William Liporace <will.na2na <at> gmail.com>
To:             	vnc-tight-list <at> lists.sourceforge.net
Date sent:      	Mon, 01 Jan 2007 16:54:51 -0500

> I have even gone the point of disabling the firewall from the linux box.
> The system will allow me to connect with a xxx.xxx.xxx.xxx:01
> xxx.xxx.xxx.xxx:02 and etc, but I can not connect using xxx.xxx.xxx.xxx
> or xxx.xxx.xxx.xxx:00. When I do connect, all I get is a grayish screen
> and I do see a graphical X (for a better discription) that moves with my
> mouse. I have tried RealVNC Viewer and TightVNC viewer.
> 
> Will
> 
> 
> -------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Calcote | 2 Jan 2007 17:36
Picon
Favicon

Re: SuSE 10.2 & TightVNC

Yes, I got it working - I got a note from a SuSE support tech indicating that the problem was with a new form of
configuration available in SuSE 10.2.

1. Login as root on the graphical console.

2. Go to the "computer" button, choose "More Applications...", then scroll down to "System"

3. Choose "Login Window".

4. Choose the "Remote" tab.

5. In the drop down box, set remote login to "Same as Local"

...or whatever. At this point, you can choose your options. The point is, remote login (which is managed
through VNC) is disabled by default in 10.2 through this configuration window. I don't really know why
this configuration information is not the same as the legacy VNC configuration information - just that
it's not and it's new.

John

-----
John Calcote (jcalcote <at> novell.com)
Sr. Software Engineeer
Novell, Inc.

>>> William Liporace <will.na2na <at> gmail.com> 01/01/07 10:47 AM >>>

Does any one have tight VNC working? I get the grey screen and have not
had any luck using it...
(Continue reading)

Permalink | Reply | 8 comments |
headers
William Liporace | 2 Jan 2007 23:38
Picon

Re: SuSE 10.2 & TightVNC

TNX John & Dave,
I was able to get to the VNC running again.  I did notice a few
annoyances or other things that are different.... The biggie is the
difference in screen size!  Where do I set this?  It is not the actual
desktop size.

The other item was the port. I was able to connect to port 5901 but not
5900. I want to be able to see my actual desktop. We do remote support
and collaboration.  I also leave things running on my home PC and want
access to them.

TNX Will

On Tue, 2007-01-02 at 09:36 -0700, John Calcote wrote:
> Yes, I got it working - I got a note from a SuSE support tech indicating that the problem was with a new form of
configuration available in SuSE 10.2.
> 
> 1. Login as root on the graphical console.
> 
> 2. Go to the "computer" button, choose "More Applications...", then scroll down to "System"
> 
> 3. Choose "Login Window".
> 
> 4. Choose the "Remote" tab.
> 
> 5. In the drop down box, set remote login to "Same as Local"
> 
> ...or whatever. At this point, you can choose your options. The point is, remote login (which is managed
through VNC) is disabled by default in 10.2 through this configuration window. I don't really know why
this configuration information is not the same as the legacy VNC configuration information - just that
(Continue reading)

Permalink | Reply | 7 comments |
headers
Dave Ihnat | 3 Jan 2007 00:06

Re: SuSE 10.2 & TightVNC

On Tue, Jan 02, 2007 at 05:38:56PM -0500, William Liporace wrote:
> TNX John & Dave,
> I was able to get to the VNC running again.  I did notice a few
> annoyances or other things that are different.... The biggie is the
> difference in screen size!  Where do I set this?  It is not the actual
> desktop size.

Take a look at the VNC settings in /etc/xinetd.d/vnc.

> The other item was the port. I was able to connect to port 5901 but not
> 5900. I want to be able to see my actual desktop. We do remote support
> and collaboration.  I also leave things running on my home PC and want
> access to them.

Ah--I don't think that's going to happen.  X on Linux is a truly
multi-user desktop (unlike Windows, which is essentially a single-user
system with multitasking.)  I don't believe VNC can tap into a running
X session; it will start a new session for you.

If you're using KDE, you can play with Desktop Sharing (look
for "krfb Desktop Sharing"), but it's restrictive--invitations are only
good for an hour, and AFIK you can't set the password but have to use the
generated one.  I haven't used this, but have just done some digging and
found references on how to use it.  Take a look at

  http://www.linuxjournal.com/article/6553

a bit dated but still usable.

G'luck,
(Continue reading)

Permalink | Reply | 3 comments |
headers
John Calcote | 3 Jan 2007 00:30
Picon
Favicon

Re: SuSE 10.2 & TightVNC

Will,

If you want to take over the primary desktop (5900 - screen 0), check into the LibVncServer package on the
SuSE distro CD's. This package provides a vnc server called x11vnc, which allows you to connect to screen
0. The install is a LITTLE rough around the edges - it requires you to get into the guts of service
configuration to set it up the way you want it. 

When you use x11vnc, you can type on the VNC screen and watch the characters being entered on the console
screen (if you can see the console, that is - my SuSE box is right behind me on the desk, so I can sit at my main
machine (win32) and watch my console if I look over my shoulder).

This is great tool for headless machines like my home router. The linux box is in my wiring closet, so I can
just remove the screen and keyboard, then when I want to work on my router, I just attach to screen 0 and I see
what I would see if I were sitting physically at the console. 

I think this is what you want...

John

-----
John Calcote (jcalcote <at> novell.com)
Sr. Software Engineeer
Novell, Inc.

>>> Dave Ihnat <dihnat <at> dminet.com> 01/02/07 4:06 PM >>>
On Tue, Jan 02, 2007 at 05:38:56PM -0500, William Liporace wrote:
> TNX John & Dave,
> I was able to get to the VNC running again.  I did notice a few
> annoyances or other things that are different.... The biggie is the
> difference in screen size!  Where do I set this?  It is not the actual
(Continue reading)

Permalink | Reply | 1 comment |
headers
William Liporace | 3 Jan 2007 01:12
Picon

Re: SuSE 10.2 & TightVNC

Sounds like some thing has changed... I may have removed TightVNC and
installed RealVNC. I know that TightVNC is based on RealVNC....

I do not remember how I used to get screen 0, but it did not seem hard.

Will

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Permalink | Reply | 0 comments |

Gmane