VNC Client for E75

Does anyone know of a working VNC Viewer for the E75 (and similar phones)?
I have been searching around and found the following:
http://symvnc.sourceforge.net/ - Discontinued and app will not install, due to expired certificate
http://www.symbian-freak.com/forum/viewtopic.php?f=4&t=15527&start=0 - All links to software lead to here: http://developer.symbian.org/?version=1 and I can't find the VNC software or the "PIPS" software anywhere.
I did find this as well, which I haven't tested yet, but don't really want to spend $20 on a VNC Viewer:
http://shop.my-symbian.com/PlatformProductDetail.jsp?siteId=695&jid=7229E8AD212614XX43767F7XF8B72F44...
Cheers,
Charles

Denis
I have had some success with Ultra VNC-
http://ultravnc.sourceforge.net/
Using it on WinXP to Xserve's
Ed

Similar Messages

Has anyone tried REAL VNC client for Mac OSX? Is it worth the money?

Has anyone tried REAL VNC client for Mac OSX? Is it worth the money?

you should not be getting that many crashes and unlike others here i don't see any strong reason to go to 7.2 other than to get to 7.2.1. i very strongly suspect you have dodgy AU's (probably around 218 of them) and if you have a look at your crash log it should show you why you are crashing. if you see an AU in the crash log it is telling you it is causing headaches. my guess is that upgrading is not going to solve your problems.
just so you know, if everything is running as it should be logic will hardly ever crash. post up the crashed thread from your crash log next time it happens. also make sure that you have the proapp kit latest version.
i know its deeply frustrating when things are going pear shaped. everyone but everyone feels that the stupid thing should just work and gets the over-whelming feeling that apple is supposed to make products that just work, that we paid good money for that level reliability and if it's going to act like this we might just as well have stayed with cheaper PC's. reality is, once you start throwing thrid party's into the mix it is really hard to keep control of reliabillity. if you took logic back to zero 3rd party plugs and in built audio, it would take fanatical fundamentalist to crash the thing. (having said that - i reckon i could)

Best VNC client for iPad

What is the best VNC client for the iPad? So far I've heard about iTeleport by Jaadu, Desktop Connect, Mocha, iTap, VNC Viewer. Any advice much appreciated!
Thanks,
HL

After reading the various reviews on VNC clients, I went ahead and purchased "Screens". I am happy to say so far the connection via wi fi was extremely easy and fast. I was connected in less than 5 minutes after the download. The UI is very intuitive and speed is excellent.
The only complain I have of it so far is I wish they had a full screen mode option when viewing the desktop, and that would be a minor complain. I am having problems connecting via my iphone on a 3G network which according to the website I should be able to, but not such luck here.
It might be because I might be putting in the incorrect IP address. My Airport Extreme Base is daisy chained to another non apple wifi router, and the IP address I am getting on my MAC may not be a public IP address, and I am not sure how to work around that.

Best Windows VNC client for talking to Mac Desktop

I am trying to display the screen of the secondary display of a Mac from a Netbook. Ideally, I want the functionality of the Mac "share screen" feature, in particular with this you can choose to view either one of the displays, or both together. Does anyone know of a Windows or Linux VNC client which does this? I have looked at a couple of clients (TightVNC and RealVNC) but they both show both displays in a horizontal scrollable screen. I'm also concerned about performance, in particular the impact on the remote machine i.e. the one using two screens. Are Windows VNC clients going to impose any more overhead than a remote Mac connected via "share screen".

About the external monitor, should a physical one be attached to ?
If not that would be nice to use it only w/ vnc
btw: I opened a thread on tightvnc tracker , see you there :
https://sourceforge.net/tracker/?func=detail&aid=2811360&group_id=14067&atid=364 067

Oh what I would give for an Apple VNC client for PC's

And to be able to do more to pc clients than simply view or control
How hard could it be for someone to write this? Use port 3283 to send the controls etc to the client and use 5900 for viewing.
Oh well, that's my wish list!

while the Air can play many games fine, it is not an idealized gaming machine.
examine a macbook Pro model at your local Apple store for evaluation if you plan on much gaming.

Windows VNC clients cannot connect to Snow Leopard Server native VNC server

I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

Is there VNC software for OS9?

Is there VNC software for OS9? (Like Chicken of the VNC for OSX)
I want to be able to control an OSX machine from an OS9 machine. Can this be done?
-JN

Yes there is VNC software out for classic
here are a few links
VNC Thing for classic
ChromiVNC for classic
NetMath VNC for
classic
VNC clients for classic
MacVNC for PPC and 68K
I hope this is what you was talking about and hope
this helps
Well, it is what I was looking for. Too bad that...
#1 is no longer there
#2 doesn't work
#3 doesn't work
#4 & 5 (same program) crashes big time
Oh well, it was worth a try. Perhaps there are extension conflicts or something. Thanks anyway for the suggestions. I think I'll just switch over to OSX when I need to on the machine in question. Chicken of the VNC works like a charm.
-JN

VNC Client [SOLVED]

I am looking for a VNC client that I can use to remote users on our internal network. I liked the original VNC, but it has been moved to AUR and when I try to install it, it always errors out when compiling. Is there any client that you can recommend?
Thanks.
Last edited by tyndallc (2010-05-18 15:53:26)

i like tightvnc, myself
$ pacman -Ss vnc
extra/gtk-vnc 0.3.10-1
A VNC viewer widget for GTK
extra/libvncserver 0.9.7-3
The vnc library
extra/tightvnc 1.3.10-5
VNC Unix server && viewer
extra/vinagre 2.30.1-1 (gnome-extra)
A VNC Client for the GNOME Desktop
extra/vino 2.28.2-1 (gnome-extra)
a VNC server for the GNOME desktop
extra/x11vnc 0.9.9-3
A VNC server for real X displays
extra/x2vnc 1.7.2-2
Lets you use two monitors on two different computers one one computer

How to use VNC-Client or sim. for remote management

Hi folks,
how can i use a VNC-Client to do a remote session with a ZCM10 RM-enabled
client ?
Any ideas ?
Regards
Thorsten

thanks !!1
>>> Michael Fleming<[email protected]> schrieb am
Dienstag, 11. Januar 2011 um 14:06 in Nachricht
<[email protected]>:
> After you have set a Remote Management Policy (with VNC password) and
> assigned to the device, then run %appdata%\novell\ZENworks\Remote
> Management\bin\nzrViewer.exe. Put in device IP/DNS ~50. Done.

How do I connect with a webbased VNC client to a dual-monitor Lion machine?

I'm using a webapplication to manage a narrowcasting system.
For this I use an installation of XAMPP on a dedicated Mac Mini hooked up to some monitors.
This software is accessible through a webinterface on the local Mac Mini. With this software people can arrange video's and send them to the monitors connected to the Mac Mini.
This works very well, but know I also want to build a feature where people can see what the Mac Mini's are sending to the monitors. For this I want to use a webbased (now it is Java) vnc viewer build into the webinterface.
I've tried a setup with the TightVNC Java viewer and the build-in OSX VNC server. This gives me the problem that when I try to connect to the Mini I always encounter the Lion login screen. This seems to be new Lion behaviour that can't be disabled. I know that there are some vnc clients that support OSX authentication (like Mocha), but at this point I haven't found a webbased solution for this.
If I use the Wine vnc server I don't have this problem (when I access the Mac Mini I go straight to the active desktop). Unfortunately Wine doesn't support multiple monitors.
I use two monitors on the Mac Mini (one for showing the video playback and one for admin work). I want to setup the vnc client in a way where the user only sees the second screen.
Is there a solution out there that eliminates both of these problems (so connecting without the Lion login screen and only giving a view of the second monitor?).
Any help would be much appreciated.

No one? Seems I want something that can't be done. To bad.

NX Client for intel Mac?

Does anyone know if NX client for Mac works under the Intel Macs? I've got a linux box (SuSe 10.0) at work on which I have NX server set up so that I can access my stuff easily from home. Will be adding the MBP to my home network, and am wondering if NX client for PPC will work under Rosetta. So far, no intel Mac NX clients appear to be available.

I'm pretty sure that the NX client for PPC would work under rosetta, however is NoMachine the only option for accessing your SuSE box? Is this the only protocol allowed by your employer for remote access? How about using X over SSH or VNC? these are much more open standards of remote access that are fully supported "Out of the box" with Intel Mac OS (they are totally free too!)

Remote Management and Windows VNC clients

Hey guys,
I recently had a go at getting the built-in VNC server in Leopard (as part of remote management) up and running.
Remote control works flawlessly from other Macs, but it refuses connections to Windows clients most of the time (throws up errors like 'Error waiting for server message' or something).
Any ideas? I thought it might have something to do with the Windows client not understanding the encryption, but haven't found any way to change security settings.
Thanks in advance!

Have you giving the server a VNC password?
System Preferences -> Sharing -> Remote Management -> Computer Settings -> VNC viewers may control screen with password: xxxxxxx
What VNC client are you using on Windows. Not all VNC clients are created equal? I know about TightVNC (which has been reported to work), RealVNC, and UltraVNC are 3 that I've heard about.
You can also install your own VNC server (in parallel using a different port or instead of the Mac OS X VNC). Vine Server (aka OSXvnc) has been used successfully for years. After all not all VNC servers are created equal either

Windows client for ARD?

I'm looking in to how to establish a remote desktop connection from Windows to Macs with the stipulation that we not use VNC so I'm wondering if a Windows client for ARD exists.
If not, does anyone have a suggestion for doing RDC from Windows to Mac. I can already do it going from Mac to Windows using MS's client or the open source CoRD, but I'm really hitting dead-ends trying to figure out how to go the other way.

To continue what Templeton Peck said, most any VNC client will work. I personally prefer UltraVNC, and I use that to control 5 different Windows machines from my Mac. While you don't get all the advanced options like sharing clipboards, waking/shutting down, collecting reports etc... You still get full access to the remote Windows machine as you do when you connect to a Mac in ARD.

Connect to VM console directly with VNC client

I used to be able to connect to a VM's console with the VNC client by logging onto the OVM server where the VM was running and discovering what port the VM's VNC server is listening on (xm list -l | grep location). Now it seems that doesn't work anymore. Is there still a way to do this with OVM 3.1.1?

It appears they have disabled this feature in 3.1
If you look at the vm.cfg file on an old 2.x server it is of the format
bootloader = '/usr/bin/pygrub'
disk = ['file:/var/ovs/mount/3D2FD7081A3D49FCBA309AF1316E028F/running_pool/212_ThisServer/System.img,xvda,w',
'file:/var/ovs/mount/3D2FD7081A3D49FCBA309AF1316E028F/running_pool/212_ThisServer/thisDisk_1.img,xvdb,w',
disk_other_config = []
maxmem = 2048
memory = 2048
name = '212_ThisServer'
on_crash = 'restart'
on_reboot = 'restart'
uuid = 'f1bb3127-751f-4224-b348-5f7f3bc0d30a'
vcpus = 2
vfb = ['type=vnc,vncunused=1,vnclisten=0.0.0.0,vncpasswd=thispassword']
vif = ['bridge=xenbr0,mac=00:46:3E:79:C2:9F,type=netfront']
vif_other_config = []
Then on a 3.1 vm.cfg
vif = ['mac=00:21:26:45:22:68,bridge=192.168.64.0']
OVM_simple_name = 'XP Base Install'
vnclisten = '127.0.0.1'
disk = ['file:/OVS/Repositories/0005dbc00003ba00125c62ddc69f963a/VirtualDisks/0005dbc000120000caecb0faa3a25145.img,xvda,w', 'file:/OVS/Repositories/0005dbc0000300003ba20155bc480b24/ISOs/0005dbc0001500003442da06ad201438.iso,xvdb:cdrom,r']
vncunused = '1'
uuid = '0005dbc0-0006-0000-d77c-20e2f718bdd0'
on_reboot = 'restart'
boot = 'dc'
name = '0005dbc000060000d47830e2f718bdd0'
cpu_weight = 27500
memory = 2048
cpu_cap = 0
maxvcpus = 1
OVM_high_availability = False
maxmem = 2048
vnc = '1'
OVM_description = ''
on_poweroff = 'destroy'
on_crash = 'restart'
guest_os_type = 'windows'
usbdevice = 'tablet'
builder = 'hvm'
vcpus = 1
keymap = 'en-us'
OVM_os_type = 'Other Microsoft Windows'
OVM_cpu_compat_group = ''
OVM_domain_type = 'xen_hvm'
I have tried replacing
vnclisten = '127.0.0.1'
with
vnclisten = '0.0.0.0'
and it opened up the port but I could not connect successfully with tightVNC. Tight VNC appears to make a connection but you cannot see anything.
You can see what ports by running a 'netstat -nat' on the VM server (command below I removed unimportant results)
[root@ovs-c9-28-2c VirtualMachines]# netstat -nat
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1: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:6900 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6901 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6902 0.0.0.0:* LISTEN
As you can see above the port 5902 is listening while the others are set to localhost and used by the VM Manager for VNC connections.
I also tried adding in the vncpasswd line like below and was prompted for a password but the VNC session failed. Note it also broke the VNC access from the manager.
vnclisten = '0.0.0.0'
vncpasswd = 'letmein'
That said Oracle do not support manual modification of the vm.cfg file (unless pinning CPUs) so going in there is probably not a good idea.
I think the only solution is to install a VNC server on the VM directly.
Edit:
Further to this you will note that there are also ports 6900 - 6902 which are definitely related to the VNC connection. I tried connection to these ports with no success however.
It appears the manager is acting as a tunnel for the VNC as when I have a valid connection (from manager) to the server on port 5901 I see the following
[root@ovs-c9-22-2c VirtualMachines]# netstat -nat
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:9020 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7901 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7903 0.0.0.0:* LISTEN
tcp 0 0 192.168.64.125:7777 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8899 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8003 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:5901 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:5902 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:753 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6900 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6901 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6902 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp        0      0 192.168.64.125:6901         192.168.64.120:44014        ESTABLISHED
tcp 0 0 192.168.64.125:37298 192.168.64.64:3260 ESTABLISHED
tcp 0 0 192.168.64.125:8899 192.168.64.125:41445 TIME_WAIT
tcp 0 0 192.168.64.125:8899 192.168.64.125:41454 TIME_WAIT
tcp 0 0 127.0.0.1:46117 127.0.0.1:5901 ESTABLISHED
tcp 0 0 192.168.64.125:8899 192.168.64.125:41448 TIME_WAIT
tcp 0 0 127.0.0.1:9020 127.0.0.1:56940 ESTABLISHED
tcp        0      0 127.0.0.1:5901              127.0.0.1:46117             ESTABLISHED
tcp 0 0 192.168.64.125:8899 192.168.64.125:41456 TIME_WAIT
tcp 0 0 127.0.0.1:56940 127.0.0.1:9020 ESTABLISHED
tcp 0 0 192.168.64.125:8899 192.168.64.125:41450 TIME_WAIT
Then a netstat on the manager shows the pipe is definitely connecting through 6901 (on server) and 15901 (on manager)
Notable IPs
Machine I am VNCing from 192.168.64.50
VM Manager 192.168.64.120
VM Server 192.168.64.125
I have bolded the connections that disappeared after disconnecting the VNC connection.
[root@manager ~]# netstat -nat | grep .50
tcp 0 0 192.168.64.120:22 192.168.64.50:58858 ESTABLISHED
tcp 0 52 192.168.64.120:22 192.168.64.50:50838 ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:63350 ::ffff:127.0.0.1:54321 ESTABLISHED
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.50:53327 ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:54321 ::ffff:127.0.0.1:63350 ESTABLISHED
tcp        0      0 ::ffff:192.168.64.120:15901 ::ffff:192.168.64.50:49503 ESTABLISHED
[root@manager ~]# netstat -nat | grep .125
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46983 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46976 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46986 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46977 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46982 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46978 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46974 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46981 TIME_WAIT
tcp        0      0 ::ffff:192.168.64.120:44014 ::ffff:192.168.64.125:6901 ESTABLISHED
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46985 TIME_WAIT
tcp 0 0 ::ffff:192.168.64.120:7001 ::ffff:192.168.64.125:46987 TIME_WAIT
Edited by: phoenixdigital on Sep 24, 2012 4:30 PM

Telnet/ssh client for mac

My company uses a telnet/ssh client for windows called putty and since they only make it for windows i need something like it. They use the putty client to access the companies wireless internet system on that has an assigned ip. Actually they only use the ssh part of the client so i guess that woudl be fine for me too. If my mac will do it itself that would be great too. I just am completely lost anything would be great.

and if you need to create ssh tunnels, have a look at SSH Tunnel Manager
tunnel manager is not really necessary if your already using the terminal.
ssh -L 5901:localhost:5902 serverip.
The above is an example of creating a listing port making a tunnel for the above port this what people use for tunneling to initiate a vnc session for example.

VNC Client for E75

Similar Messages

Maybe you are looking for