/
Cannot access Time and Attendance within the network
Cannot access Time and Attendance within the network
Description of Issue
Users can't reach any of the Time and Attendance environments within the organization's network
Browser error received:
Hostheader took too long to respond
ERR_CONNECTION_TIMED_OUT
No errors will be shown in the Time and Attendance application/error logs
Context
- Time and Attendance
- ExecuTime
- On-Premise Only
- Firewall
- Ports
Cause
Windows Firewall on the Time and Attendance server is enabled and blocking traffic for the instances designated ports
Resolution
Firewall rules for the Time and Attendance ports will need to be made on the application server so that the application can be reached from other devices and servers within the network.
The standard TCP ports for Time and Attendance are:
- 7120 (Prod)
- 7130 (Train)
- 7140 (Test)
Depending on how many Time and Attendance environments there are, additional rules will need to be made for those, for example:
- 7150 (Impl)
- 7160 (Impl2)
Additional Information
, multiple selections available,
Related content
Error Remote Access to the Primary Interface not Allowed
Error Remote Access to the Primary Interface not Allowed
More like this
After upgrading to TA 2024.1 or higher Timeclocks displaying Server Unreachable
After upgrading to TA 2024.1 or higher Timeclocks displaying Server Unreachable
More like this
Unable To Run Time and Attendance Reports Due To Reporting Error
Unable To Run Time and Attendance Reports Due To Reporting Error
More like this
Okta enabled Time and Attendance instance gives No Such Host is Known when logging in
Okta enabled Time and Attendance instance gives No Such Host is Known when logging in
More like this
Remote access to the primary interface is not allowed for this user error
Remote access to the primary interface is not allowed for this user error
More like this
Tyler Connectivity between Time and Attendance and EERP Failing - 503 Service Unavailable
Tyler Connectivity between Time and Attendance and EERP Failing - 503 Service Unavailable
More like this