Scott, >From my testing it never resolves the IP address again. I deleted the IP address from the registry (not the hostname) and it tries to connect to..well, nothing. I also put echoserver on a PC with DHCP. I connected to it with echovnc. I then moved the server to a different subnet (same hostname, different IP) and was able to resolve/ping the server at the new address (after ipconfig /flushdns). When I open echovnc, however, it will error out saying it couldn't connect to the old IP address.
hope that helps! Paul On Apr 1, 2005 5:27 PM, Scott C. Best <[EMAIL PROTECTED]> wrote: > Paul: > > Heya. I'll check to see if we did that wrong. If the user > puts an FQDN into echoVNC, it should "save" that entry in the > registry as it was entered, not as it resolved. We may have missed > that... > > -Scott > > On Thu, 31 Mar 2005, Paul Perpich wrote: > > > Hello again, > > > > I think I found a problem. The IP address is resolved when the server > > entry is created. It doesn't seem to be checked ever again so when > > the IP address of the hostname you entered changes the echovnc server > > will never find that new IP address. > > > > Any way around this? > > > > Thanks again, > > Paul > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
