CNI connection problem

Hi all
I have a project I am trying to connect remotely to with a cni connected directly to a VPN.Port 10001.I`ve just received the relevent IP address,username & password from the IT people.The first time I opened the connection the cni opened the network & the project could be controlled/modified.Now when i try to connect all that happens is a 23109 information message "Failed to open network,cni is inaccessable".If i open the Lantronix 3.6 & click search,It tells me there are no devices.If i ping the cni ip address the device sends a reply.The c-gate commands tell me there is a port failure.Looking through the posts,it seems to have happened to other people & wondered if anyones got a sollution.Do i need to power cycle the cni for it to release the port?

 

Yes try a power cycle....Sometimes the CNI does lock up.

 

CNI Reset

I am having the exact same problem.

Is another solution possible for reseting or closing the port on the cni. Is there a telnet command or something that can be triggered through the dos prompt.

Can the CNI be set up to auto close if no activerty.

On another note, has anyone considered remote access through VPN handshake in colour touch screen.

I'm hoping this may prick up Darrens ears.

The only possible solution at the moment seems to be the old power cycle trick with the cni.

any help

 

to state the bleeding obvious....

I have also had trouble in some remote connections... ask the IT people about wether the IP addres they gave you is within the DHCP range and what the max lease time is. Let me explain my theory:

DHCP range = 192.168.0.1 -> 192.168.0.25 - looks fine so far, only 10 devices connected to network, 24 available IP addresses, sweet.
CNI IP = 192.168.0.15 - initial power up, check comms, all OK.

DHCP max lease time = 48 hours.
CNI still connected on 192.168.0.15... lease time expires... connection 'dis-engaged' by router / DHCP.
(i'm not sure if ping still works to CNI at this point)

the next day... a computer starts up on the network. DHCP assigns it 192.168.0.15 - ** Bad news **
You can ping the IP address and get a reply, but it is not the CNI

Computer logs off, CNI has still exceeded its lease time, so not aloowed to connect. Cycle CNI power, re-registers with DHCP , but only for 48 hours!.

So what you really want is an IP that is just out of the DHCP range (say 192.168.0.30) with an indefinate lease time .

But thinking on my feet i guess you can check which really has the problem by cycling power to the router, rather than the CNI, if connection is restored, probably router config...


and as far as using the CTC as a CNI, its not possible, search the forums and you will see why!

anyway...rant over... hope this helps.

 

Just to clear up a couple of things;

Yes, a device can be pinged after its DHCP lease has expired.

Second, MOST... routers and other devices that assign IP addresses dynamically are intelligent enough to know whether a device is still on the network or not, lease or no lease, and will not hand out a new IP address matching the CNI's old one.

On another note, I think your idea of putting the CNI outside of the DHCP pool is a damn good one! Assign it it's own static IP address, and go. There isn't any need to assign a dynamic address to it, and nearly all routers and firewalls will not allow you to dynamically assign addresses outside of the DHCP pool anyway.

Darpa

 

just don't forget to adjust any firewall settings to also allow for this 'larger' IP range!

Cheers

Grant