@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.
