popup Initiate Connection at cold boot logon unattended

[redge]

unaceptable popup Initiate Connection at cold boot NO Network BEFORE uvnc_service live on welcome/logon screen unattended server .

NO popup Initiate Connection AFTER uvnc_service live and NO Network at welcome/logon screen/logged user unattended server as awaited

service _commandline=-autoreconnect id:1234 -connect repeaterhost
winvnc 28 April
vncviewer28 April (won't need vncviewer connected for this test)


steps:

1. remove the ethernet cable (simulate break TCP/IP) on host vnc server
2. cold start computer winvnc system service
service _commandline=-autoreconnect id:1234 -connect repeaterhost
service system + w/wo plugin.dsm


symptom:
winvnc show Initiate connection window... only at cold boot on welcome/logon screen
unaceptable on unattended server computer.



logged user or logon/welcome screen NO Network AFTER uvnc_service live

no plugin OK
SecureVNCPlugin 2.3.0.0 OK
MSRC4plugin.dsm 1.2.4.0 OK


cold boot welcome/logon screen UNWANTED pop up Iniate Connection appear, NO network BEFORE uvnc_service live
I would prefer nothing pop up and waiting network cable up TCP/IP and retry autoreconnect.

NO plugin, fail
SecureVNCplugin, fail
MSCR4Plugin, fail


fix wanted:
winvnc should stay standby or anything and reconnect as soon network available without pop up at cold boot only sent message to event viewer (eventvwr.exe of failure and continue waiting/pending and retry)

[redge]

work around solve partially until timeout (service delayed start available only from vista and up)
uvnc_service automatic change to delayed start and won't run until tcp/ip up so fix the issue on cold log on until timeout
uvnc_service is depend of tcp/ip driver but there are an bug somewhere

so the server must have only short time no network (<2min)
after, pop up initiate connection and winvnc won't self reconnect but just wait at pop up

wanted result: winvnc should self close the initiate connection and reconnect as soon network back on line.

[supercoe]

Any word on if this issue will be solved in a coming UltraVNC release?

I would love to see a -nopopups variable that suppresses all GUI windows.

Still dreaming of the command line only UltraVNC server.

[Nick_ua]

Any word on if this issue will be solved in a coming UltraVNC release?

I would love to see a -nopopups variable that suppresses all GUI windows.

Still dreaming of the command line only UltraVNC server.

I agree with supercoe.
I'm always popping up these windows
because on some computers, the Internet started 2-3 minutes after system startup
and the windows just hang and autoreconnect does not work

[Rudi De Vos]

The problem is not the network, but an incorrect name.
You always have the network running, even without a network cable (127.0.0.1)

repeater=www.uvnc.com -> not found popup
repetaer=45.12.23.12 -> always continue, doesn't need to check it.

Change:
1) unexisting dns name, via commandline or service_commandline -> stop winvnc.exe
This make the service restart winvnc
Only problem is that an incorrect hostname via the commandline doesn't give any error....
Added a 1 sec low beep, so atleast you know something went wrong...

Still need to make a new build.
Build updated, exe online.

[supercoe]

Thanks Rudi but I would still like to see a command line option to suppress all GUI messages.
Can't wait to test.

[Rudi De Vos]

Suppress all Gui message would make several function disfunction.

winvnc is build as gui application, using sendmessage to communicate between different parts.

winvnc -connect abc -run
actual does a sendmessage, no gui, no commandline injection.

[YY]

Change:
1) unexisting dns name, via commandline or service_commandline -> stop winvnc.exe
This make the service restart winvnc

So a mistyping of the host name in reverse connection will terminate all established connections,

Please also consider & take care this situation.

[YY]

Hi! Everyone,

I too had been encountering the problem of "Initiate Connection" popup when network is not ready, and have some suggestion to improve this situation.

If your are interested you can read it on:
Server ask "Add Client" (host) if internet is down!

[Rudi De Vos]

Adding a reverse connection via winvnc -connect abc -run send a message to the running winvnc server.
If you enter a wrong hostname, the message is never send. This doesn't effect the established connections.

[Nick_ua]

The problem is not the network, but an incorrect name.
You always have the network running, even without a network cable (127.0.0.1)

repeater=www.uvnc.com -> not found popup
repetaer=45.12.23.12 -> always continue, doesn't need to check it.

Change:
1) unexisting dns name, via commandline or service_commandline -> stop winvnc.exe
This make the service restart winvnc
Only problem is that an incorrect hostname via the commandline doesn't give any error....
Added a 1 sec low beep, so atleast you know something went wrong...

Still need to make a new build.
Build updated, exe online.

Everything works fine but
Can I turn off (Added a 1 sec low beep,) or not?
My friends jump when they hear this sound

I noticed that sometimes (winvnc.exe) shows that it is connected to the (repeater) but really it is not connected.

[supercoe]

+1 beeping is unnecessary, this popup should never be displayed when running from service_commandline. The connection should just be tried again.

[Rudi De Vos]

There need to be some indication that winvnc is running.
The icon also don't display as the winvnc desktop part isn't started until it can resolv the dns name.
(Makes it run invisable, until connections, something i realy don't like in this kind of software)
For giving forum help,
low beep -> unsolved dns name is something easy...
Does nothing-> '!ç(§éè! no idea.

[supercoe]

I guess I'm thinking about the issue in terms of how it would be used with ChunkVNC...

There need to be some indication that winvnc is running.
Task manager.

The icon also don't display as the winvnc desktop part isn't started until it can resolv the dns name.
Doesn't apply to my use as I hide the icon.

(Makes it run invisable, until connections, something i realy don't like in this kind of software)
I'd love to have a command line only UltraVNC as we talked about in the past.

For giving forum help,
low beep -> unsolved dns name is something easy...
Does nothing-> '!ç(§éè! no idea.
Wouldn't it be better to just enable logging by default and append a text file in the server directory on every run?
This way if forum members need help we could first ask for the log file.

Thanks for the explanation Rudi, as always you are the master here!

[B]

With the way Vista and Win7 auto-hide most of the system tray by default, I'm not even sure an icon there has much value these days... even though I personally prefer to keep it there...

[redge]

beep would not help at all, this help, maybe, developer.
my host linux vserver of repeater can be reached only via FQDN , unpossible with IP !
i really need winvnc run quiet without any pop up except log to eventviewer log