I can see the Can@Net II/VCI in the Can@Net II configurator, but when I try to connect to it via the VCI Device Server Control I get an 0x8007274C error.
I am using the latest version of Windows 10 with VCI 4.0.590.0.attest. Even with all firewalls outright disabled, this fails. I have also tried DIP-switch resetting the Can@Net II and reconfiguring it with the default password “IXXAT”.
Pinging the device is successful.
Hello,
I will have to look into this and get back to you, thanks!
Nick
Can you confirm the part number of this device?
Best regards,
Nick
Hi Nick.
Thanks for the
response. Where might I find that? It’s a CAN@net II V1.4. Serial# HW806842.
Hello,
I have no way of finding it from the serial number, the part number should be in form of 1.XX.XXXX.XXXXX.
Best regards,
Nick
1.01.0086.90001
Hello,
I received some feedback from a colleague, can you please do the following.
For a wireshark you would need to use a managed switch with port mirroring.
Best regards,
Nick
I’ve been using a
direct connection to troubleshoot with static IPs. 30.30.30.1 is the host
and 30.30.30.2 is the Can@Net II. I get a port unreachable from the adapter.
Despite specifying
a logfile on desktop, I haven’t been able to get the VCI Device Server
Control to actually output a file.
Ok, are you able to do a wireshark?
Best regards,
Nick
Yes, it was attached in the last email I sent. I’ll attach it to this email as well.
Ok, I think the problem is that we do not have wireshark file white-listed. Could you please put it in a zip folder? If that doesn’t work I can have you send it to our no-reply us-support email.
Best regards,
Nick
Thanks, my colleague and I will review.
Nick
Hello,
From my colleague, we wanted to confirm the following,
"When I understand right
The Wireshark Trace you sent me look like a trace of the Configuration tool, this uses UDP:
“No.”,“Time”,“Source”,“Destination”,“Protocol”,“Length”,“Info”
“1”,“0.000000”,“30.30.30.1”,“255.255.255.255”,“UDP”,“105”,“15001 > 15000 Len=63”
“2”,“0.002165”,“30.30.30.2”,“255.255.255.255”,“UDP”,“185”,“15000 > 15001 Len=143”
“3”,“0.102353”,“30.30.30.1”,“255.255.255.255”,“UDP”,“105”,“15001 > 15000 Len=63”
“4”,“0.106088”,“30.30.30.2”,“255.255.255.255”,“UDP”,“185”,“15000 > 15001 Len=143”
“5”,“0.207212”,“30.30.30.1”,“255.255.255.255”,“UDP”,“105”,“15001 > 15000 Len=63”
“6”,“0.210168”,“30.30.30.2”,“255.255.255.255”,“UDP”,“185”,“15000 > 15001 Len=143”
“7”,“0.310397”,“30.30.30.1”,“255.255.255.255”,“UDP”,“105”,“15001 > 15000 Len=63”
I made here an example trace on my workstation when starting the CAN@net in the device server:
“No.”,“Time”,“Source”,“Destination”,“Protocol”,“Length”,“Info”
“1060”,“26.077283”,“10.41.1.60”,“10.41.24.100”,“TCP”,“66”,“54961 > 15000 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1”
“1061”,“26.079679”,“10.41.24.100”,“10.41.1.60”,“TCP”,“60”,“15000 > 54961 [SYN, ACK] Seq=0 Ack=1 Win=8192 Len=0 MSS=1456”
“1062”,“26.079718”,“10.41.1.60”,“10.41.24.100”,“TCP”,“54”,“54961 > 15000 [ACK] Seq=1 Ack=1 Win=64240 Len=0”
“1063”,“26.080065”,“10.41.1.60”,“10.41.24.100”,“TCP”,“66”,“54962 > 15001 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1"”
He also wanted to make sure you have the configurator close when trying to connect with the device server. Can you verify this?
Best regards,
Nick
I apologize for the long delay. I just needed a point to point connection, so I used a offline network and was able to get it working.