Paxton Net2 issues with controllers Unknown firmware Status

[taner91xp]

Hello,

 

I did see here a few Paxton NET2 topics.

I would like to ask you did you have any issues with NET2 classic and NET2 Plus controllers?

 

My issue now is that when I want to check the firmware status of all controllers a lot of controllers on field firmware show unknown.

My Paxton version is 6.6.12017.4376 Pro.

 

I suspect that some of the controllers are with different hardware version.

I did two times upgrade and this unknown status didn't cleared on the controllers.

The interesting part is that during upgrade I see how firmware is uploaded and installed but in the final I am not able to see the current firmware version, I only see unknown state.

 

Please keep in mind that the controllers work fine.

It's like cosmetic bug.

 

 

It's appeared after a few upgrades before and not cleared.

 

Do you have any information ?

 

Thank you in advance for your attention regarding the topic.

[JRA]

Might be worth asking Paxton themselves, they are for the most part pretty hot on supporting stuff.

 

https://www.paxton-access.com/contact-us/our-technical-support/

[Jcx500]

Might be worth asking Paxton themselves, they are for the most part pretty hot on supporting stuff.

 

https://www.paxton-access.com/contact-us/our-technical-support/

 

This , anytime I’ve had Paxton issues I haven’t been able to resolve in a hour or so I’ve escalated to Paxton support. They are always second to none

[ITGURU]

Paxton's reply to me a few year ago:

 

We have determine that any Net2 plus controllers Mk 1 with serial Numbers below 1795108 are being affected by the issue and will show “unknown” firmware. This is purely cosmetic and does not affect any of the Net2 Plus boards functionality.

 

As the controllers of this range are over 5 years old No fix is due to be implemented.

[taner91xp]

Hi, thank you for the information.

 

I have another question.

 

Do you have any issues with biometric readers after upgrading to the latest version?

We use IEVO controllers and IEVO readers for biometric tokens.

 

The IEVO controllers are IP based.

 

When I try to take new biometric finger print from menu Token Add Biometric the NET2 client stuck in not responding state and later the Net2 is closed automatically.

 

This is the error in event viewer:

Faulting application name: Net2.exe, version: 6.6.12017.4376, time stamp: 0x62fccd3fFaulting module name: OLEAUT32.dll, version: 10.0.19041.985, time stamp: 0xfc8f0d5bException code: 0xc0000005Fault offset: 0x0007043cFaulting process id: 0x5be8Faulting application start time: 0x01d950de23f98e7eFaulting application path: C:\Program Files (x86)\Paxton Access\Access Control\Net2.exeFaulting module path: C:\Windows\System32\OLEAUT32.dllReport Id: 069f22f2-69cf-498d-9ab3-9bcc67ae6b87Faulting package full name: Faulting package-relative application ID:

 

Do you have any one bad experience with Ievo and the latest Paxton upgrade?

 

The issue is happened after upgrade of NET2 server and clients.

The previous version where the Ievo was okay is 6.1.8616.3794 in remote location A and 6.2.8928.4090 on remote location B , the current version on both locations is 6.6.12017.4376.

[taner91xp]

Hi, I would like to inform you that if you use Ievo devices integrated with Paxton be carefully!

In the latest version of Paxton Net2 the ievo integration doesn't work!

Especially with this version and build 6.6.12017.4376!

 

I don't understand why Paxton hide this issue, but I didn't find any release note or information about this issue!

 

It's hard to open communication with Paxton Net2 support directly if you are not customer of their partner but in the past I was successfully reach them using their official email, today this is not possible, their official support email is filtered to white list, where are only partners and their internal employees.

 

I did find unofficial way to contact someone from NET2 but I don't receive much information, only that they know for the issue and the advice was to contact Ievo.

 

We contacted Ievo, they confirmed that it's a Paxton Net2 issue and Paxton usually recommends to their customers downgrade. Also Ievo provide new their own integration Isync which is compatible with the latest versions of NET2 but it's paid and need license.

 

Finally my colleague did find sollution:

Server could be 6.6.12017.4376!

But the clients should be 6.06.11130.2638!

In this combination client server Ievo integration works!

I hope that this information will help someone.

[Miscbrah]

Well that does indeed sound like a pickle, kudos to you for posting the resolution.