Skip to Content
Niagara 4 Supervisors & WorkplacesWhat to do when a Platform login is failing

What to do when a Platform login is failing

Platform login failures can prevent access to Niagara Stations and Supervisors. This guide provides systematic troubleshooting steps to identify and resolve common login issues.

Overview

Platform login failures can occur due to:

  • Authentication Issues: Incorrect credentials or passphrase
  • Network Problems: Connectivity issues between Workbench and Station
  • Service Issues: Platform services not running properly
  • Configuration Problems: Incorrect platform or Station configuration
  • Security Settings: Firewall or security policy blocking connections

Initial Diagnosis

Step 1: Identify Error Message

Note the exact error message:

  • "Authentication Failed": Credential or passphrase issue
  • "Connection Refused": Network or service issue
  • "Host Not Found": DNS or hostname resolution issue
  • "Timeout": Network latency or firewall issue
  • "Platform Service Not Available": Service not running

Step 2: Check Basic Connectivity

Verify basic network connectivity:

  1. Ping Test: Ping the Station hostname or IP address
  2. Port Check: Verify platform port is accessible (typically 1911)
  3. Firewall: Check if firewall is blocking connections
  4. Network Path: Verify network path to Station

Step 3: Verify Service Status

Check if platform services are running:

  1. Station Service: Verify Station service is running
  2. Platform Service: Check platform service status
  3. Web Supervisor: Verify Web Supervisor is running (if applicable)
  4. Service Logs: Review service logs for errors

Step-by-Step Troubleshooting

Issue 1: Authentication Failed

Symptoms

  • Error: "Authentication Failed" or "Invalid Credentials"
  • Cannot connect despite correct username/password

Solutions

Check Username and Password:

  1. Verify Credentials: Double-check username and password
  2. Case Sensitivity: Ensure correct case (usernames may be case-sensitive)
  3. Special Characters: Check for special characters in password
  4. Account Status: Verify user account is enabled and not locked

Check Passphrase:

  1. Workbench Passphrase: Verify Workbench passphrase is correct
  2. Reset Passphrase: Reset passphrase if forgotten (see How to reset a PC's Passphrase)
  3. Passphrase Match: Ensure passphrase matches Station requirements

Verify User Account:

  1. Station Users: Check user exists in Station user list
  2. User Permissions: Verify user has necessary permissions
  3. Account Expiry: Check if account has expired
  4. LDAP Integration: If using LDAP, verify LDAP configuration

Issue 2: Connection Refused

Symptoms

  • Error: "Connection Refused" or "Cannot Connect"
  • Workbench cannot establish connection to Station

Solutions

Check Station Service:

  1. Service Status: Verify Station service is running
  2. Service Restart: Restart Station service
  3. Service Logs: Review service logs for errors
  4. Service Dependencies: Check service dependencies are met

Check Network Connectivity:

  1. Ping Test: Ping Station hostname/IP
  2. Port Accessibility: Test if platform port (1911) is accessible
  3. Firewall Rules: Check firewall allows connections
  4. Network Configuration: Verify network configuration

Verify Platform Port:

  1. Default Port: Check if using default port (1911)
  2. Custom Port: Verify custom port configuration
  3. Port Conflict: Check for port conflicts
  4. Port Testing: Use telnet or netcat to test port

Issue 3: Host Not Found

Symptoms

  • Error: "Host Not Found" or "Unknown Host"
  • Cannot resolve Station hostname

Solutions

DNS Resolution:

  1. Hostname Resolution: Test hostname resolution (nslookup, dig)
  2. DNS Configuration: Verify DNS server configuration
  3. Hosts File: Check Windows hosts file for entries
  4. Use IP Address: Try connecting with IP address instead

Hostname Configuration:

  1. Station Hostname: Verify Station hostname is correct
  2. Network Configuration: Check Station network configuration
  3. Hostname Format: Ensure hostname format is correct
  4. Alternative Names: Try alternative hostname formats

Issue 4: Timeout Errors

Symptoms

  • Error: "Connection Timeout" or "Request Timeout"
  • Connection attempts timeout before completing

Solutions

Network Latency:

  1. Network Speed: Check network speed and latency
  2. Network Path: Verify network path to Station
  3. Bandwidth: Check available bandwidth
  4. Network Congestion: Identify network congestion issues

Timeout Settings:

  1. Increase Timeout: Increase connection timeout in Workbench
  2. Platform Timeout: Check platform timeout settings
  3. Network Timeout: Verify network timeout configuration
  4. Timeout Values: Adjust timeout values appropriately

Firewall and Security:

  1. Firewall Rules: Verify firewall allows connections
  2. Security Software: Check antivirus/security software settings
  3. Proxy Settings: Verify proxy configuration if used
  4. VPN: Check VPN configuration if applicable

Issue 5: Platform Service Not Available

Symptoms

  • Error: "Platform Service Not Available" or "Service Unavailable"
  • Platform service cannot be reached

Solutions

Service Status:

  1. Service Running: Verify platform service is running
  2. Service Restart: Restart platform service
  3. Service Dependencies: Check service dependencies
  4. Service Configuration: Verify service configuration

Service Logs:

  1. Error Logs: Review service error logs
  2. Startup Logs: Check service startup logs
  3. Platform Logs: Review platform-specific logs
  4. System Logs: Check system event logs

Service Configuration:

  1. Configuration Files: Verify service configuration files
  2. Port Configuration: Check port configuration
  3. Binding Address: Verify service binding address
  4. Service Permissions: Check service account permissions

Advanced Troubleshooting

Enable Debug Logging

Enable detailed logging for diagnosis:

  1. Workbench Logging: Enable debug logging in Workbench
  2. Platform Logging: Enable platform debug logging
  3. Network Logging: Enable network packet logging (if needed)
  4. Log Analysis: Analyse logs for specific errors

Network Diagnostics

Perform network diagnostics:

  1. Traceroute: Use traceroute to identify network path
  2. Port Scanner: Scan for open ports on Station
  3. Packet Capture: Capture network packets for analysis
  4. Network Monitor: Use network monitoring tools

Platform Connection Test

Test platform connection manually:

  1. Telnet Test: Test port connectivity with telnet
  2. Platform Tools: Use platform diagnostic tools
  3. Connection Test: Use Workbench connection test feature
  4. Alternative Client: Try alternative client tools

Common Scenarios

Scenario 1: First-Time Connection

Issue: Cannot connect to Station for first time

Solutions:

  1. Verify Station IP/Hostname: Ensure correct address
  2. Check Station Status: Verify Station is running
  3. Network Access: Ensure network access to Station
  4. Platform Port: Verify platform port is correct
  5. Initial Setup: Complete Station initial setup if needed

Scenario 2: Previously Working Connection

Issue: Connection that previously worked now fails

Solutions:

  1. Recent Changes: Identify recent configuration changes
  2. Service Restart: Restart Station and Workbench services
  3. Network Changes: Check for network configuration changes
  4. Updates: Verify if recent updates affected connection
  5. Credentials: Verify credentials haven't changed

Scenario 3: Multiple Users Affected

Issue: Multiple users cannot connect

Solutions:

  1. Station Service: Check Station service status
  2. Network Issues: Verify network connectivity
  3. Station Configuration: Check Station configuration
  4. License Issues: Verify Station license is valid
  5. System Resources: Check Station system resources

Prevention and Best Practices

Regular Maintenance

  • Service Monitoring: Regularly monitor service status
  • Log Review: Periodically review logs for issues
  • Configuration Backup: Keep backups of configurations
  • Documentation: Document connection settings

Configuration Management

  • Standard Configuration: Use standard configurations where possible
  • Change Management: Document configuration changes
  • Testing: Test changes in development first
  • Rollback Plan: Have rollback plan for changes

Monitoring

  • Connection Monitoring: Monitor connection health
  • Alerting: Set up alerts for connection failures
  • Performance Monitoring: Monitor connection performance
  • Trend Analysis: Analyse connection trends

Additional Resources

  • Niagara 4 Troubleshooting Guide
  • Platform Connection Documentation
  • Network Diagnostics Tools
  • Service Management Best Practices