ipsetup can't see netburners

[gerald lucha]

We have a product with 4 SB2le board in each unit.
Previously, I would run IPSETEP and it would immediately "see" all 4 of the netburners. Then I would be able to set the static IP addresses required (4 addresses per unit).

Now we have units coming off the production line and I can't configure any of them because IPSETUP can't seem to find any of them. What am I missing here? Has anything changed?

[Ridgeglider]

Is your AppName really long? There is an issue w/ long AppNames not showing up. Can't remember, but I think 64 chars may be the limit. When longer, the NB modules don't appear in either IPSETUP, or NBFind. Try downloading the factory demo by hitting 'A' to enter the monitor, and then FLA to enter the serial download mode. If a known-good app works w/ IPSETUP or NBFind after the serial download, try shortening the AppName you're using to something short.

[rnixon]

Are you using *exactly* the same computer, switch, etc? If a different computer, is the firewall enabled?
Your application must be good/running. Did you download an app to the units or do you use the factory apps?
If you take one of them and put them in the nb development board, what do you see in ipsetup, and what do you see over the serial port?

[gerald lucha]

These are standard netburners from the factory. So the "app" is not ours.
It seems as if there has been some production change wherein they now are shipped expecting to see a dhcp server. The IPSETUP program used to see all 4 netburners in our units right from the start and allow us to set the 0.0.0.0 addresses to the static addresses we want them to have.

Now, we need to plug them into the company network where they eventually get assigned a company address (which we quickly change to a non-routable fixed address that we need).

Needless to say the IT department is not happy to see dozens of strange devices showing up requesting addresses. This expedient will not work for us in the future.

As to the comment about hooking to the serial interface, too late for that. These are built into a product and the serial port is not available to us.

I have a ticket open with Netburner about this problem.
I posted here in case I had missed some documentation change or information that I should have seen somewhere. But thanks for the ideas.

[tod]

In the meantime you could stay in the good graces of IT by just getting your own inexpensive (< $30) router with DHCP and let it assign the addresses, no need to connect to your company LAN. It might be informative to put a new factory unit in a dev carrier board and see if IP Setup sees it on that board, just in case something on your hardware is interfering with the protocol and IPSetup uses.

[pbreed]

Which netburner, and when did you buy them?

What S/W is your PC using IPSETUP running?

Windows 7 and windows vista has a problem seeing IP addresses of 0.0.0.1 (The return address used by a netburner with no values set)

This has been fixed in the latest releases, and was just fixed a few days ago for the SBL2E devices.

It may take a while for this to chatch up with everything in the production /stocking queue...