Network Scan vs. XP SP2


http://www.s-code.com/forum/Topic38.aspx
Print Topic | Close Window

By Alphageek - Wednesday, January 12, 2005

I remember reading in the old forum something about XP SP2 breaking VNC Manager's network scan functionality.  Microsoft implemented a new security "feature" with Service Pack 2 that limits the number of unsuccessful outgoing connection attempts, which then caused scans to quit working.  Are there any plans to come up with a fix for this... or at least a work-around?

Thanks, and thank you for a great program! 

By Yury Averkiev (s-code) - Wednesday, January 12, 2005

I've very good news. Seems we were able to workaround that problem. In our tests we running Network Scan with timeout set to 200 ms and don't get blocked by tcpip.sys driver.
We are going to test new 2.5.69.1 build for one more day and after that it will be uploaded to our site.

By Alphageek - Thursday, January 13, 2005

Cool... I just tried it and it seems to work.  But did you mean 2000 ms?  Changing the timeout to 200 ms sure makes for fast scans, but it doesn't work any better than the default 800 ms.

Thanks for the help, 

Steve

By Yury Averkiev (s-code) - Thursday, January 13, 2005
I did mean 200. This seems like the lowest value in our test, at which VNC Manager still able to discover VNC servers. But I guess this all depends on network speed.
By Yury Averkiev (s-code) - Friday, January 14, 2005
Build 2.5.69.1 is now available download. The change log for this build:

NEW: Deployment Wizard - target servers list is now pre-filled with selected registered servers.
FIX: VNC server scan compatibility with Windows XP SP2
FIX: Active viewer tabs color is not updated if color was changed in server properties.
FIX: Network Scan List - Clear Results menu item is not shown if no items selected in the list.