Paxton Net2 issues after moving server

[Bruce123]

I have exactly the same problem although I completely uninstalled my V6 as the database was corrupted beyond repair so did a complete reinstall with a blank database. All my doors won’t connect to the new one despite being ticked in the config utility. They all say update pending. I’ve even dropped the power on a couple to see if it helps but it didn’t. Left it overnight and hoping when I go in tomorrow it’s worked otherwise I’m going to be doomed for Monday as all the doors are locked shut! Paxton didn’t know what the issue was when I rang them earlier. Did you have any joy?

 

I was going to update this thread anyway. The Issue was that I had clicked Update Firmware, but hadn't clicked on OK (on the Nodes tab) of config window (I must have waited and waited for the firmware to upgrade and given up and clicked Cancel). When I went through it again I clicked OK and a dialog box popped up to say the Net2 service would be stopped to allow the firmware upgrade to take place. After I clicked OK it actually initiated the firmware upgrade and rebooted the controllers. We also found that we needed to click Re-instate in Net2 to push out the config to the controllers (as per advise earlier in this thread - this can be found by in the main Net2 application, select Doors and click on Re-instate). So if you don't recall a dialog box asking if it's OK to stop thee Net2 service, then it's probably because you didn't click OK.

 

I hope this advice is useful reaches you in time!

 

Thanks, Bruce.

 

PS You might have to start the Net2 service manually afterwards - right click on the triangle on the task bar.

[DalekSec]

I was going to update this thread anyway. The Issue was that I had clicked Update Firmware, but hadn't clicked on OK (on the Nodes tab) of config window (I must have waited and waited for the firmware to upgrade and given up and clicked Cancel). When I went through it again I clicked OK and a dialog box popped up to say the Net2 service would be stopped to allow the firmware upgrade to take place. After I clicked OK it actually initiated the firmware upgrade and rebooted the controllers. We also found that we needed to click Re-instate in Net2 to push out the config to the controllers (as per advise earlier in this thread - this can be found by in the main Net2 application, select Doors and click on Re-instate). So if you don't recall a dialog box asking if it's OK to stop thee Net2 service, then it's probably because you didn't click OK.

 

I hope this advice is useful reaches you in time!

 

Thanks, Bruce.

 

PS You might have to start the Net2 service manually afterwards - right click on the triangle on the task bar.

 

Thank you for this, saved me a ton of time! Just had the same issue!

[Duffstar]

This worked for me. Putting in a V6 system and the installer has never done anything large enough to be networked. I'm the on-site IT and setting all the backend up for them so I can add the doors to the access profiles as we go. Trying my best to make it seamless to the users, but we all know that's never going to happen

 

+1 Kudos from me for the update

[Olliedawg]

I've previously had issues with one door where a token scan would do literally nothing. You would hear a beep but you would not get a message to state that the door is opening, nor anything on the event logs.

 

This particular door had a green tick in the utility software, I could also ping the door. In the end, a reboot of the net2 unit for this particular door fixed the issue. No idea whatsoever what was up with it.

[Guest Guest]

I've previously had issues with one door where a token scan would do literally nothing. You would hear a beep but you would not get a message to state that the door is opening, nor anything on the event logs.

 

This particular door had a green tick in the utility software, I could also ping the door. In the end, a reboot of the net2 unit for this particular door fixed the issue. No idea whatsoever what was up with it.

 

I’ve had that a few times, re-instating the controller usually resolves the issue

[Jcx500]

When I moved a net2 server from win10 to Server 2019 , I had to go a reboot all the controllers manually , seemed to kick in then

[miloshmedia]

+1 - if it beeps with no reader status change or server entry it usually means the controller is 'blank' and has no DB settings - if you go to Net2, doors on the left, reinstate at the bottom when it shows the list of doors/groups, then select the ACU then reinstate, you'll hear a series of beeps (can't remember how many) and it'll start accepting tokens again.