autoreconnect with dynamic ip address at repeater

[saise]

hi,

i am facing the following problem with the latest version of chunkvnc:

when running the repeater on a host having a dynamic ip address issued by the provider using a dyndns service the autoreconnect does not work

everytime the repeater host changes the ip address, the instantsupport ultravnc server is not able to reconnect, because according to wirehark dumps i made it is not resolving the new ip address of the repeater host.

indeed the ultravnc server always tries to reconnect to the old ip address.

it seems that the name resolution is done only once at starting the service.

any ideas how to overcome this limitation?

thanks in advance!

lg
saise

[B]

You're correct. Some of us have been complaining about this for a long time; I had hoped it was going to be fixed in the new version of UltraVNC?

This problem -- UltraVNC checks network connections and resolves names into IP addresses ONLY on first starting -- affects people with full time servers, people who roam, people who are on cellular connections, people who occasionally swap network cards (e.g., laptop users), all forms of dynamic DNS users, etc.


The only workaround would be to schedule a periodic restart of the UltraVNC service. Perhaps a dynamic DNS client applet could cause the VNC server to restart when an IP address change is detected.

[supercoe]

This is exactly what I'm working on, I want the InstantSupport wrapper to communicate with the repeater. This way InstantSupport will just start the UltraVNC service (which then would resolve the DNS name properly). I believe this would also increase security a bit.

[B]

That's great, supercoe; that will help a lot.

<b>However</b>, I really think UltraVNC itself should be fixed in this regard; there's no reason it should play so dumb as to underlying network changes, <b>especially</b> when there's no current session established.

In my opinion it's a rather big bug.

[supercoe]

Hopfully this will get Rudi's attention.

[post=84198][/post]

[B]

Thanks, supey; I added my two cents.

[tbran6]

saise,
have you tried purging and updating your local DNS cache? I don’t seem to have this issue, I’m using no-ip.com for DDNS over uverse ISP, however here are the commands from a command line: “ipconfig /flushdns” and for flushing WINS/NetBIOS cache enter "nbtstat -R" I also like to flush the address Resolution Protocol (ARP) cache "arp -d"

not sure if it will help you but wanted to throw that at ya.