Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

CR1000/NL120 network connection lost


ciewinder Feb 19, 2011 01:48 AM

No connection in network. I was out on medical for 10 weeks and missed the loggernet and deviceconfig firmware upgrades. I was able to connect during that time via vpn network connection but the local LAN connection was lost. Upon return could not connect with Campbell SC-USB. I updated deviceconfig and connected, and after determining no LAN network access, updated the CR1000 OS to vers 21. Now I cannot connect in LAN or through VPN. I can't find old congig settings but printed them before doing the above and have reset those. Still no luck and seeing the following:


Failure: 2/18/2011 20:10:25.178
transaction failure","unreachable destination","Get Logger Program Status
Failure: 2/18/2011 20:10:25.178
transaction failure","unreachable destination","check/set clock
Failure: 2/18/2011 20:14:40.788
Open failed
Failure: 2/18/2011 20:16:26.778
unexpected socket error","10060","connection timed out
Failure: 2/18/2011 20:16:27.788
Open failed
Failure: 2/18/2011 20:17:02.548
transaction failure","unreachable destination","Get Logger Program Status
Failure: 2/18/2011 20:17:02.548
transaction failure","unreachable destination","check/set clock

Do I need DNS settings?

Thanks,

Ed


Sam Feb 21, 2011 02:56 AM

Ed,

Start with the basics:

By default the logger uses DHCP to acquire IP settings. Has the logger successfully acquired these settings?

If not using DHCP, have you entered valid IP and gateway addresses?

What is the PakBus address? The default is "1".

Is there any security set? 3 level logger or TCP password? The default is no security.

What port is specified for PakBus over IP communications? The default is 6785.

Do these settings match those specified in LoggerNet->Setup?

If so, can you ping the Logger's IP address?

If not, then you will want to work with your IT staff to check settings of the firewalls between you and your logger.

Log in or register to post/reply in the forum.