AmiVNC (server)

[motorollin]

Has anyone ever succeeded in getting AmiVNC running? I am trying to run it on my A4000 but no matter which version I use (Planar only or RTG+Planar) I get no output from the app, and I am unable to remote control the Amiga.

--
moto

[jj]

Are you tryying to control the Amiga from a PC ?

Is it cconnecting ?

Have you got the Amiga side set as a listening server ?

[motorollin]

JJ wrote:
Are you tryying to control the Amiga from a PC ?

Well, a Mac, but using a VNC client.

JJ wrote:
Is it cconnecting ?

No. The VNC client just sits there. I can ping the Amiga, so I know there is connectivity there.

JJ wrote:
Have you got the Amiga side set as a listening server ?

Well the AmiVNC server should sit and listen for connections. But the documentation says that the software should output what it is doing to let you know it is listening, but it doesn't output anything.

--
moto

[jj]

Not too sure on the Amiga version, was just thinking outloud really from the pc version.

What happens when you try connecting through vnc from you mac to the amiga ?

[motorollin]

JJ wrote:
What happens when you try connecting through vnc from you mac to the amiga ?

The viewer just hangs and eventually times out saying it can't connect. I am assuming the server isn't actually running, since there is no output from it when I run it.

--
moto

[jj]

Mmmm , sorry I can be of more help.

Not up on Macs , but is VNC blocked on your firewall

Is the port it uses blocked on your firewall or router ?

[motorollin]

I can VNC to other (non-Amiga) boxes on the same network from the same Mac using the same client, so it's not the Mac or the network. It has to be something to do with the server software on the Amiga.

--
moto

[alexh]

I always wanted to have the connection the other way around.

Control the PC using the Amiga keyboard and mouse.

That way you maintain 100% compatibility for games and demo's which hit the Amiga hardware.

The ultimate solution for someone with two monitors, or a dual input monitor is a network KM (no V).

I had hoped that some great coder could port x2vnc to OS3.x using ixemul.library and ixnet.library

Or that Douglas McLaughlin would open source his Synergy client for Amiga OS 4 so that we could get a back-port to OS3.x

[jj]

Sorry was stating obvious things, but sometimes they are the things that throw us  :-D

Have you tried a different version, i.e older one ?

[motorollin]

@alexh
There are a couple of really good VNC clients for the Amiga, as well as Remote Desktop clients, so it is entirely possible to control a PC from an Amiga. However, I want to do it the other way round :-)

--
moto

[motorollin]

@JJ
It's ok, it's good to have someone go through the obvious points anyway, since sometimes they are not so obvious when you're frustrated :-) There is only the one version of AmiVNC on Aminet unfortunately.

--
moto

[jj]

Have a vauge memory that there was one on the RealVNC site, though could be insane

[da9000]

Having an open firewall port on the Mac would be a moot point if the Mac is the VNC client, as it initiates the outgoing connection - it's not running the server.

Now on the Amiga, if you have a firewall (is there one?), then you'd better open the port(s) if the firewall shuts down incoming connections by default (why wouldn't it!??! isn't that the point?)

Anyhow, I don't have Chicken Of The VNC in front of me, but I recall on the PC using TightVNC, when you specify the port, you *must* use two colons ( between the IP and the port. Maybe give that a try?

Also, I'd recommend hard-coding the port initially (default is 5900 if I recall correctly), just to eliminate any unneeded frustration.

Good luck moto

[Ferry]

@alexh

Take a look here.

Saluditos,

Ferrán.

[Ferry]

@motorollin

Well, I have used it a couple of times under OS4, and it worked OK, and that's over WAN, over the internet.

But the documentation says that the software should output what it is doing to let you know it is listening, but it doesn't output anything.

AmiVNC server should inform you about every step it does, something like this:

main : Listening set on port 5900
main : Waiting for client connection
main : accept()ed connection from xx.xx.xx.xx on socket 1
main : Negociating protocol version
main : Protocol supported by server : 3.3, by client : 3.3
main : Authentication
main : ClientInitialisation
main : SharedFlag = 1 (multiple clients : Yes)
main : Screen set to [TwinVNC - xx.homeip.net:5900 (My PC) - 1280x1024x8] (RTG)
main : prepared duplicate socket key 6549865165
main : sHandlerName='AmiVNC handler.0'
vProcessIncomes : got duplicate socket key 6549865165
vProcessIncomes runs on socket 0
main : RTG mode Pic96/5 @ 0x806ba6e0, 1280x1083, 2 pp, size 4325418
main : non-FastMode 32bit
vProcessIncomes : nEncodings=3/14


If AmiVNC stays on the "main : Waiting for client connection" stage it could be because, for some reason, the signal is not reaching its destination. Have you done the other way round? I mean, have you tried a client on the Amiga side and a server on the Mac side, just to check the connection?

Saluditos,

Ferrán.