Josh,

The program runs just fine on every modern windows version. My development
computer is on 7.x until I replace it sometime in the next few months.
The test computers are all on a mix of 7 and 8.  My laptop runs 8.0 (can't
get it to upgrade to 8.1).

I think what needs to happen is Microsoft and every other windows firewall
vendor needs to fix their *@#($* tcp/ip stack/firewall so someone needing
to write a program to send and receive a multicast packet under windows can
actually do so in a reliable, consistent fashion.   Under XP, making this
happen was straightforward.   Each successive windows version has made it
more difficult, and in some cases the necessary tools to make it work
consistently are simply not exposed in the windows API - especially when
you have a third party firewall involved.

The bootloader on the next iteration of the sitemonitor won't use multicast
for this reason.  Unfortunately, we're stuck with it for the Base and Base
II units.

For the base II, there's a new version of the upgrade tool up at
http://manuals.packetflux.com/index.php?page=base-unit-ii-firmware which
tries to work through some of the more common firewall issues.

In addition, there is always the possibility that the ethernet port in the
affected units have failed.   At least for the Base II, if you want to send
an email in to [email protected] with the serial number and address
ifnormation, we'll issue a UPS call tag to pick up the unit and test it
here, fix it, and ship it back to you all at our cost.     If you want to
include the original base unit in the package with a note 'please factory
reset if possible - see Forrest' attached to it, we'll also factory reset
that one if possible and ship it back to you - we just won't be able to do
any hardware fixes on it if that's what is needed.

-forrest


On Wed, Nov 26, 2014 at 12:35 PM, Josh Luthman via Af <[email protected]> wrote:

> Well if the option is newer laptop with bigger screen, memory, speed, etc
> or working with Packetflux....I think Packetflux needs to fix their program
> on Windows
>
> *duck*
>
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
> On Wed, Nov 26, 2014 at 2:33 PM, Bill Prince via Af <[email protected]> wrote:
>
>>  I don't argue with things that work.
>>
>> --
>> bp
>> <part {dash} 15 {at} SkylineBroadbandService {dot} com>
>>
>>
>> On 11/26/2014 11:03 AM, Josh Luthman via Af wrote:
>>
>> That's so 2001...and they're all tossed/sold/gone
>>
>>
>>  Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>>
>> On Wed, Nov 26, 2014 at 1:34 PM, Bill Prince via Af <[email protected]> wrote:
>>
>>>  Maybe why it works for me.  My field laptop is Windows XP.  An old
>>> reliable dog.
>>>
>>> --
>>> bp
>>> <part {dash} 15 {at} SkylineBroadbandService {dot} com>
>>>
>>>
>>>  On 11/26/2014 6:02 AM, Shayne Lebrun via Af wrote:
>>>
>>>  Find an old laptop running windows XP or (even better) Windows 2000.
>>>
>>>
>>>
>>> *From:* Af [mailto:[email protected] <[email protected]>] *On
>>> Behalf Of *Josh Luthman via Af
>>> *Sent:* Wednesday, November 26, 2014 8:38 AM
>>> *To:* [email protected]
>>> *Subject:* Re: [AFMUG] SiteMonitor discovery IP or factory reset
>>>
>>>
>>>
>>> I tried one of each.  No combo worked.
>>>
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>>
>>> On Nov 26, 2014 8:34 AM, "Jeremy via Af" <[email protected]> wrote:
>>>
>>> Yeah, I must have missed that part.  Is this one of the old site
>>> monitors?
>>>
>>>
>>>
>>> On Wed, Nov 26, 2014 at 6:04 AM, Josh Luthman via Af <[email protected]>
>>> wrote:
>>>
>>> That was a base2 though right?
>>>
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>>
>>> On Nov 26, 2014 12:59 AM, "Jeremy via Af" <[email protected]> wrote:
>>>
>>> I actually had to use this tool on a site tonight.  I used the new
>>> Ethernet Upgrade Tool for windows, was directly connected to the Ethernet
>>> port on my laptop.  I pressed 'yeah I have read the blah blah blah' and
>>> then hit discover, it told me to reboot.  I disconnected power 1 and 2 for
>>> a sec and when I plugged it back in it gave me the IP.  Then I couldn't
>>> figure out the SNMP so I had to use it again to reset, same process.  It
>>> worked perfectly both times.
>>>
>>>
>>>
>>> On Mon, Nov 24, 2014 at 7:28 AM, Josh Luthman via Af <[email protected]>
>>> wrote:
>>>
>>>  Not sure what email address to use offlist...
>>>
>>>
>>>
>>> I've done all that several times to confirm.  I also went straight to
>>> the NIC as well as trying a Netgear dumb switch (it had link light, doesn't
>>> specify speed/duplex).
>>>
>>>
>>>
>>>
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>>
>>>
>>>
>>> On Mon, Nov 24, 2014 at 3:33 AM, Forrest Christian (List Account) via Af
>>> <[email protected]> wrote:
>>>
>>> Unfortunately there's quite a few things which will break the tool.
>>> I've attached a .pdf which should cover all of them.  Make sure you have
>>> the right tool as described, and if you have problems afterwards let me
>>> know.
>>>
>>>
>>>
>>> -forrest
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>

Reply via email to