network failing to open

I am trying to make some changes and I keep getting "network failed to open"

I have a CNI (one of the first I think) and I believe it is the culprit, but I cant be sure.

Is there anything I can do to prove it, or find out why I cant do anything anymore.

I have checked the default interface and it is fine
I can load the lantronix manager up in the web browser - so maybe it is not the CNI
I can ping the network and get all unknown an Rescan network.

Can someone shed some light on this for me please.

Mick

 

What steps are you using in Toolkit to open the Network?

 

from memory

open program

open network (says it running after that)
open second network (there is a bridge in the system)
click on units - the database loads all the units
click on scan units

The windows pops up checking for dunplicate units and then times out with network failed to open.

i am starting to think that it may be the bridge as C-gate is reporting somthing about an orphan at address 253 and a few other funny lines pop up as well about renaming "local network" to "local network".

Mick

 

Oh.. so its the bridged network that is failing to scan? Can you scan the units on the Local Network ok?

 

the local network is not scanning either.

I cant scan anything (local or remote) and the ping only responds with local devices as per the first post

mick

 

update:

I unplugged the bridge and it will go to 100% for the checking duplicate units but then fails to open thenetwork.

A scan for new finds one a address 0 and then fails. Did this a few times and it finally said there was a new PCI at address 0

deleted the one that existed in the database ad re-added it (add unit to DB).

Rescanned and it still fails after checking for duplicate units (Error 3051)

Mick

 

Mick

I assmume that you've checked all the basics, i.e. only 1 burden on the network, voltages all fine etc?

You implied that your CNI is somewhat old. In the device installer does it come up with a version number of 5.X or 4.X on the end of the device type?

 

talking to myself now

it was that stupid bloody burden again

Turned itself off again for some reason. I now have the hardware burden pluggen in and will leave it that way. This has happened a few times now with different results.

So all is well now.

Mick

 

Hardware burdens rock