smaunsell

Lets forget about CVD for a start. Lets test IP connectivity.

Can you ping the IP address of the LIU??? (or are you using the MAP?)

If you can't ping then you've got an IP networking problem. If you can ping, try using Hyperterminal to telnet to the IP address (port 11001 is default for the LIU). If you can talk to it then IP networking and LIU are ok. If you can't talk, try using t4eportping (or similar) to ping port 11001. If this doesn't work then there may be a firewall blocking this port.

This is the basic testing to check if you have connectivity over the LAN. If you do then we can move on to issues with the CVD application.

The way I understand it works (as I dont use CVD) is that CVD is installed on a PC, has a connection (serial or IP) to the Coral, and you can also use a web browser from any PC that basically creates a remote desktop session over http.

thor

I can ping the IP Address of the LUI. I then tried a telnet to port 11001 and that connection failed. Unless there is a firewall on the LUI there is no firewall between me and the LUI.

The webiste appears to only have connection settings. Which is where I loaded the factory defaults by accident. You are correct CVD works via serial or ip.

smaunsell

If you can't telnet then either there's a firewall or the LIU isn't responding to the telnet request.

Can you browse the LIU ie Index of / (ILU IP address)?? If you can, check it's settings. If not, either there's a firewall or the LIU isn't responding. If you're adamanent there's no firewall and the LIU isn't responding then I'd restart the system.

Forget about CVD until telnet works.

smaunsell

I've just gone back and read you initial post. Web Manager is talking directly to the LIU - I thought you were using CWA (Coral Web Administrator).

It appears that you have altered the connection settings to the LIU which is why you can no longer get in with CVD. If you then clicked Update Settings then you've saved the settings. Clicking Factory Settings 1 or Factory Settings 2 in itself won't do anything, it just shows you a couple of default options but clicking Update saves it.

Go back to the Web Manager and click on Server Properties. Confirm the speed matches that of KB0 in TERM (in the PI) - I had this the other night that they didn't match and I couldnt get in. Also confirm that dip switch 1 on the MCP-IPx2 is to the left.

This should sort it out.

thor

This is what I had to do to get it fixed. I don't know how secure these settings are but they got me into my system that night. I'm having our vendor review these settings when they come in. Most are the Factory Defaults.

And as stated above you may also need to check you settings for your Terminal Connection and make sure they match these settings or vis-versa.

Serial Port Settings
Serial Protocol: RS232
Speed: 19200
Character Size: 8
Parity: None
Stopbit: 1
Flow Control: None

Connect Mode Settings
UDP Datagram Mode: Disable
UDP Datagram Type: Blank
Incoming Connection: Accept unconditional
Response: Nothing (quiet)
Startup: No Active Connection Startup

Dedicated Connection
Remote IP Address: Blank
Remote Port: Blank
Local Port: 11001

Flush Mode Input Buffer (Line to Network)
On Active Connection: Enable
On Passive Connection: Enable
At Time To Disconnect: Enable

Flush Mode Input Buffer (Network to Line)
On Active Connection: Enable
On Passive Connection: Enable
At Time To Disconnect: Enable

Packing Algorithm
Packing Algorithm: Disable
Idle Time: Greyed Out
Trailing Characters: Greyed Out
Send Immediate After Sendchars: Greyed Out
Sendchar Define 2-Byte Sequence: Greyed Out
Send Character 01: Greyed Out
Send Character 02: Greyed Out

Additional Settings
Disconnect Mode: Ignore DTR
Check for CTRL-D To Disconnect: Disable
Port Password: Disable
Telnet Mode: Disable
Inactivity Timeout: Enable
Inactivity Timer: 5:0
Port Password: Blank