Server as service ( don't run if you don't wan't to test the service...... SET PASSWORD or remove after testing)http://www.uvnc.eu/download/PCHelpWareV2Server.msiI see many people running with an empty password ( lucky desktop require accept else it was full open),SET A PASSWORD --- SET A PASSWORD

*Make sure everybody use another group. Set random group on initial run*added debug info ( viewer ->about->debug)Closing debug, also close viewer*If empty access code is set+use a random name for exe+show name on server, but field can be edited

I still can't connect from my home network. Viewer is win7 x64 also tried with kaspersky firewall disabled. I am using endian firewall with no outgoing firewall blocking as utm appliance.

I've used a couple of hosts on the lan (KCGROUPAOPEN/fdellv2 (xpsp3) and tinky (vista)) and in both cases get an error in the logs "NAT PUNCH FAILED" which presumably wouldn't be necessary on the LAN - as LAN was detected in this case.

I did see in the log various other previously requested servers which had failed from my groups starting, all on port 59412 - no errors in the debug and no change in icon in the viewer for those.

I also haven't been able to connect up to several remote clients which I installed rc2 server on either but will be trying that tomorrow when at another site.

If I took a tcpdump capture to look for some clues- any tips of what to look for?

For LANviewer connect to server outgoing pc ip address and portserver connect to viewer outgoing pc ip address and portFor WanThe ip address of the router is used instead of the server/viewer ip address

Nat push happen in both cases, i should have renamed it.. nat punsh are just udp packets that are send to each other until sync.For LAN it are direct packetsserver send udp packet to viewerviewer send udp packet to serverThen some sync protocol is used to make it send/recv

When nat punch fail in LAN, incoming packets are blocked by some firewall... Have you tested it insite LAN with both server and viewer on the same PC ( loopback mode), this doesn't have a real usage, butat least you know it connect..

Yes, correct, it did work on my PC, ran same created SC, came up with NAT PUNCH OK with PASSWORD FAILED. When I set the password by right-click in viewer it connected fine.

But tried it on vista PC sitting next to me, running sc server, and tried to connect, even with firewall off, computers didn't flash in viewer, and then LAN detected then a while later, NAT PUNCH FAILED. Restarted viewer PC flashing lights come back but still nat punch failed.

Also, on remote XP PC running service, switched off firewall and restarted service, computers also didn't flash in viewer until after restart of viewer, connect message didn't show in debug window until later on. No connect, no NAT PUNCH message. After I restarted viewer, and rebooted remote PC, the flashing lights came back on on viewer, and nat punch failed messages came back on.

Also with remote XP machine, first time I used SC with Group KCGROUPAOPEN, then later installed service with different group, server still comes up as visible in both groups?

So I was able to connect to both vista and xp hosts at home when off-site. And was able to connect to to my own pc running SC. I can't think what might be wrong, firewall is switched off on both machines when testing. Would be happy to try some tests if you can recommend any to try.

Thanks for the softwareFew questions:Is there need for port forwarding at the server/viewer or the access_server side?

Why can't is use any other port config at the acces_server? It's just only a command prompt that is doing "something"I want to connect to our own server, in this case the acces server, in stead of ur default ip. Is that possible with the access_server?