WIN-PAK · Free guide

WIN-PAK controller offline: a troubleshooting order that works

One controller or every controller showing offline in WIN-PAK: check server services, the network path, the controller, then the loop and panel settings — and re-sync data once it is back.

A controller shows offline in WIN-PAK. Doors may still be working, because most intelligent controllers keep making decisions from the data they last received, but events are not reaching the operators and changes to cards and access levels are not reaching the door. This guide gives a troubleshooting order that avoids the most common time-wasters. Menu names and service names vary between WIN-PAK versions and controller models; keep the manuals for your exact versions to hand.

One controller or all?

Look at the status of every panel before you touch anything.

  • Every controller offline at once almost always means the server side: a WIN-PAK service or the database is not running, or something on the server (a Windows update, firewall or antivirus change, a changed network adapter) is blocking communication. Go to the server.
  • Several controllers on the same serial loop or the same network switch points to that loop, its converter, or that switch. Go to RS-485 loops or the network path.
  • One controller points to that controller, its cable, its address or its settings. Go to the network path.

Note when it went offline. The event history usually shows the last message from the panel; compare it with power cuts, server reboots, network work or software updates at that time.

Every controller offline: the server

  1. Check the WIN-PAK services. In Windows Services, confirm that the WIN-PAK services, including the communication service that polls the panels, are running. If one has stopped, note any error before starting it.
  2. Check SQL Server. WIN-PAK keeps its data in a SQL Server database. If the SQL Server service is stopped, or started after the WIN-PAK services following a reboot, the WIN-PAK services may fail. Start SQL Server first, then the WIN-PAK services.
  3. Read the Windows Event Viewer. The Application and System logs around the time of the failure often name the cause: a service that failed to start, a database login failure, a disk full, an expired licence.
  4. Check what changed on the server. Recent Windows updates, a new antivirus product, firewall rule changes, a replaced network card or a changed server IP address are the usual suspects. A firewall that now blocks the communication service will stop every panel.
  5. Check the licence. If the licence has expired or the server hardware changed, the software may run with limited function. Check the licence status screen.

One controller: the network path

  1. Look at the controller. Is it powered? Check the power supply output and the status LEDs against the controller manual. Check the network link LEDs on the controller and on the switch port.
  2. Ping it from the WIN-PAK server. From the server (not from your laptop), run ping to the controller’s IP address. A reply proves the network path from the machine that matters.
  3. If there is no reply, check addressing. Has the controller’s IP address changed? Controllers given an address by DHCP can move after a power cut; use static addresses or DHCP reservations. Check the subnet mask and gateway too: a wrong mask makes a controller unreachable from other subnets. The subnet planner helps check addresses and masks.
  4. Check for a duplicate address. If ping replies come and go, another device may be using the same IP address. Run arp -a on the server after a ping and compare the MAC address with the label on the controller.
  5. Check the switch and VLAN. Confirm the switch port is up, in the right VLAN, and that any firewall or ACL between server and controller allows the traffic.

Reachable but still offline

If the server can ping the controller but WIN-PAK still shows it offline, the problem is usually the connection settings.

  1. Test the port, not just the address. In PowerShell on the server, Test-NetConnection <controller IP> -Port <port> using the port set for that panel or loop in WIN-PAK. If ping works but the port test fails, a firewall is blocking it or the controller is listening on a different port.
  2. Compare the panel settings in WIN-PAK with the controller. IP address, port, panel address, panel type and any communication password must match what is set in the controller. This is the usual cause after a controller has been replaced or reset to factory settings.
  3. Check how the controller is set to be hosted. Some controllers can run on their own with a built-in web page or be hosted by software. Confirm the controller is set to be hosted by this WIN-PAK server and is not still configured for another server or for stand-alone use.
  4. Check controller firmware against the software version. A controller on firmware that the installed WIN-PAK version does not support may not come online. Check the compatibility notes for your versions before updating either.

Controllers on RS-485 loops

Older and larger sites often have controllers daisy-chained on RS-485, reached through a serial port or a serial-to-IP converter.

  1. Check the converter or COM port first. If every controller on the loop is offline, start at the converter: power, network, its own settings, and the COM port or IP address WIN-PAK uses to reach it. A USB-to-serial adapter can come back under a different COM port number after a Windows update or a reboot.
  2. Check addresses and baud rate. Each controller on a loop needs a unique address, and every device must use the same baud rate as the loop settings in WIN-PAK.
  3. Check the wiring. RS-485 should be a daisy chain, not a star, on twisted-pair cable, with the same polarity (A/B or +/−) at every controller and a common reference where the controller manual calls for one. Total length is limited (RS-485 is commonly rated to about 1,200 m at low data rates).
  4. Check termination. Terminating resistors (typically 120 Ω) belong at the two physical ends of the chain only. A missing terminator, or extra ones in the middle after a controller was moved, cause intermittent offline faults.
  5. Split the loop to find a fault. If one controller drags the whole loop down, disconnect the far half and see whether the near half comes back. Repeat until the faulty controller or cable section is found.

If the controller is online but one door’s reader gives no events, that is a reader problem rather than a controller one: see card detected but door not opening and practise the conductors in the reader wiring lab.

After it comes back online

  1. Download or sync the panel. Make sure card, access level, schedule and holiday changes made while the panel was offline have reached it.
  2. Check the panel time. Controllers that lost power may have the wrong time, which breaks schedules and event times.
  3. Review the buffered events. Most controllers store events while offline and send them when communication returns. Look through them for door forced or held-open alarms that nobody saw.
  4. Write down the cause and the fix, with the date, so the next engineer starts from what you learned.

What not to do

  • Do not delete and re-add a panel as a first step. You may lose its door, reader and access level links and have to rebuild them.
  • Do not restore an old database backup to fix one panel: it overwrites every card and change made since.
  • Do not update controller firmware or WIN-PAK without a verified database backup and a check of the compatibility notes.

This guide is general technical information written for installers, engineers and facility teams. Check the manuals for your exact equipment and follow site safety rules. Brand names identify products only; Foxnet University is independent of the manufacturers mentioned.

Talk to an engineer

Not sure which service fits?

Tell us what you are working on. A Foxnet engineer will point you to the right session, book or request — or tell you honestly if you do not need one.