NetBurner Community Forum

Problem: Using Windows 7, Find(IPSETUP, etc.) can't see a NB though can ping, http, etc.

The solution for us was getting all of the information. [skipping ahead, it has to do with broadcast.] This happened in our lab on PCs that had two NICs. There is a new "feature" for Windows 7 that fixed an evil capability in NT that allows broadcasts to go out over multiple NICs. In Windows 7, the broadcast only goes out one NIC, the one with the highest priority. So, sometimes it would work on some PCs depending on the topology. argh!

Our techs had the problem, then our IT guy grabbed our resident NB guru(?), me.
And thru the magic of google, i found the following link. So if you've had
this problem with Windows 7 and multiple NICs, give the solution in the following link
a try. it worked for us - not as nice as NT, but we can at least set up
our lab topology to get it to work consistently for us.

How to fix the global broadcast address (255.255.255.255) behavior on Windows?
http://social.technet.microsoft.com/For ... ddde1c8aa/

Hey greengene, thank you for sharing that link. I ran into this as well, but was not able find such a detailed description of the problem.

Hello,

This should be fixed in the latest release of the tools. We fixed it by having IPSetup (and other applications that need to use udp broadcasts) do a search for all NICs before sending out a UDP broadcast. It then loops through the NICs when it needs to send out the broadcast and listens on all ports for the reply. I don't agree with the change the microsoft made when they gave us this "feature" in windows 7, but I don't think they are going to change it back at my request

The update of IPsetup in 2.5.3 did not solve our problem but we've
stilll got our workaround.

Also a couple more comments:
1) shouldn't this solution need to be applied wherever Find is used
in any of the PC tools, e.g., AutoUpdate, not just IPsetup?
2) wouldn't it be nicer if the resource for the app was also updated
to reflect the new version? since it appears all of the tools are
recompiled regardless of any changes made in the current release
giving the file properties modified date the same date.

okay, it looks like my changes were not included due to some CVS conflict You can get IPSetup/Autoupdate's that work properly at http://www.netburner.com/updates/pctools.zip. I will make sure this gets in the new beta too.

in these zipped files:
ipsetup went from v2.0 to v2.1 and works great - thanks.
autoupdate stayed v2.0 and its find still doesn't work for us.

also, the files are ~5 times the size of before. debug versions?

upon further testing, the "Find" in autoupdate is working in our 2 NIC
PC configuration. version labelling is confusing, but we'll get by. thanks.

greengene wrote:in these zipped files:
ipsetup went from v2.0 to v2.1 and works great - thanks.
autoupdate stayed v2.0 and its find still doesn't work for us.

also, the files are ~5 times the size of before. debug versions?

I commonly email these files to customers so they can administer their devices. Can we get a build that is closer in size to the original ~200kB executable?

Thanks.