Devolutions ForumDevolutions Forum

Wyaknow service didn't bind to proper IP - can't connect.

avatar
KriS02

Hi,

I can't connect at user computer...
For some reason wayknow service didn't change local IP and stack at old one for few days.

cmd shows me:
C:\Users\user>netstat -ano | find "4489"
TCP 172.16.13.36:4489 0.0.0.0:0 LISTENING 4292

after service restart:
C:\Users\user>netstat -ano | find "4489"
TCP 192.168.1.108:4489 0.0.0.0:0 LISTENING 8216

Detailed log as an attachment.

--
KriS

All Comments (2)

avatar
Richard Markiewicz

Hey Kris

Thanks for the bug report. We're aware of that issue - Wayk Now won't rebind it's listeners when the network layout changes. This can also bite you on a machine with multiple network adapters if one or more of them is slow to start at boot time. This affects users with the unattended service; the standalone WaykNow.exe rebinds at launch time of course.

W're working on resolving this and that will hopefully be in the next release - I'll post back here with an update.

Thanks and kind regards,

Richard Markievicz

avatar
Richard Markiewicz

Hi Kris

Wayk Now 2020.2.1 will be available later this afternoon, and contains a fix for this issue. Please don't hesitate to post back with further questions or feedback.

Thanks and kind regards,

Richard Markievicz