problem with new 5500CN and Toolkit 1.2.2

I am having trouble using Toolkit 1.2.2 in that it can find my network but refuses to connect to it.
The following is what I have tried
(Any help would be appreciated)

I just installed a brand new 5500CN to the C-Bus network.
Both the Ethernet and C-Bus side lights are a solid orange.

I am running Windows XP SP2 with ZoneAlarm.

I set up the unit with the Lantronix DeviceInstaller.
IP address 192.168.0.27
Subnet 255.255.255.0
Default Gateway 0.0.0.0
Port address for PORT 1 is 14000
(I have set the Gateway to my Router address but the same happens)

I connect to the CNI via a HUB

I can ping 192.168.0.27

I can run the CBus Diagnostic program.
It finds the CNI at 192.168.0.27:14000 at address 255.
It can monitor the network etc with no problems.
It can find ALL the units on the network.

So far so good.

I installed Toolkit 1.2.2

I set it to use CNI - 192.168.0.27:14000

If I tell it to "Search for NETWORKS" it finds my network and project with 23 units.
I tell it to OPEN the project and it comes back with an error msg saying

Information - 23109
Failed to open Network, CNI is inaccessible.

After clicking OK to this message, it comes back with

Error - 3032
An attempt to set the project name on the Network Failed

I click OK.

I now look at the CGate window (java.exe)
It says

911 //OZOLINV2/254 dd88ba20-956f-1028-9849-9939c39f6576 Can't open: C-Bus interface (port failure (Connection refused: connect)):192.168.0.27:14000

If I then Import my project from V2 of CBus installation software and then try to open the network I get the same
Failed to open Network, CNI is inaccessible.

This time the CGate window shows

742 //ozolinv2/254 474566dd-305c-4eca-8401-40079a7a6d27 Network created type=CNI address 192.168.000.027:1400

The above is shown twice followed by

911 //ozolinv2/254 474566dd-305c-4eca-8401-40079a7a6d27 Can't open: C-Bus interface (port failure (Connection refused connect)):192.168.000.027:14000

Martin

 

I just solved my problem.

I just added the CNI to my project and now I can scan the network.

Dumb operator

Now I am happy.

Martin

 

Can not access the CNI again

Hmmm,

I just booted up my PC and started Toolkit.
It would not access the CNI again.
It gets the same error as before.

The diagnostic program accesses the CBus network.

Does anyone know why this could occur?

Martin

 

Yes, I disabled Zonealarm and Windows Firewall is ALWAYS disabled.
That did not make any difference.
Since the Lantronix and the Diagnostic program always work, I doubt whether it is any firewall problems.

Sometimes I manage to get it going.

Start Toolkit
Open Project
Open the wired network
Click on units
Then Scan network.

Right now it is working, trying to configure the wireless gateway and 1 wireless plug.
Just have to get the distance between units correct so they talk to each other thru walls and floor (2 storey).

Martin

 

Not quite.. If you ever configured a firewall to disallow Java.exe access to the network then it can still be a firewall issue.. I know you've said its not.. but IP access from CGate/Toolkit to a CNI is fairly well tested and well exercised stuff..

 

I note what you say Duncan, I have the Zonealarm firewall for the TRUSTED zone OFF (low setting). The IP address range is in my trusted zone.

The Zonealarm log file is empty so it appears not be be stopping anything.

Is there a recommeded method/order after starting toolkit to scan for a network?

Martin

 

My CNI does not connect either

Did you solve the CNI problem? I have the same problem since a week ago. I even tried to conect my Desktop and Laptop directly to the CNI using a crossover cable, but no luck.

It is really strange that sometimes toolkit connects, and sometimes doesn't. Same thing happens with Schedule Plus. I tired the latest Toolkit V1.4 and same thing.

It is really frustraiting to have all the logic on Schedule Plus and not been able to run it. Any help will be welcomed.

cs.

 

I think it was the order in what I was trying.
It has been working with no problems since then.

I stat Toolkit and now just open the wired network and it all works.
I really did not change anything.

Marty

 

Hi
Possibly a dum question but I have to ask!

Is DHCP switched on for your network?

Connecting the interface directly to the PC should not work unless your PC is running a DHCP service, otherwise how is the CNI to get an IP address.
Or am I assuning it has not been assigned a fixed IP Add?

All I know is the unit I was testing picked up the next avaliable IP add from my Router, via DHCP.

 

I use both DHCP and static IPs.

DHCP mainly used for when I use my work Laptop when working from home and my PDA

Static for Server, Home laptop, PC, 2 x IceBox 2 for Topfield PVRs, print server etc