ip address

[kcscadmin]

My firm frequently uses the VNC tray icon as a way to quickly determine IP address by mousing over it. This is usually not a problem. However, when a computer gets the address 127.0.0.1, the pop-up still shows this address even after the computer gets a real address.

[B]

But your computer always has that address, well actually a whole range of addresses that are localhost addresses. I haven't seen them show up in the VNC tray icon though.

Are you saying that VNC will listen on a newly acquired DHCP address and still show 127.0.0.1 as one of the other listening addresses?

If so, I wouldn't personally consider that much of a bug, though maybe a cosmetic preference.

If not, and VNC isn't listening on the new address, that's <b>the same bug</b> that has been highlighted here a few times recently -- UltraVNC's WinVNC just won't recognize IP addresses that come into being (whether by DHCP or otherwise) <b>after</b> the WinVNC process has started running.

[kcscadmin]

this is happening when computers are out in the field (on an isolated network), so i don't know if vnc is listening on the newly acquired address.

your last sentence makes sense though because, they wouldn't acquire an ip address until after windows (and winvnc) is up an running and they connect to the wireless router.

and if winvnc won't recognize it, i guess the tray icon wouldn't show the newly acquired ip address

[B]

Yeah, some people have scripted workarounds, where the VNC service is either delayed or frequently made to restart, but personally I think that's really bad form and that the developer should fix this in UltraVNC. A single DHCP refresh can break all existing running UltraVNC servers. (Or in your case, keep them from ever responding at all.)