Thursday, March 15, 2018

Semaphore timeout period has expired

Hi there,

I found a solution to my issue but I was wondering if someone could give me an explanation about that ?

I'm working on HP Aruba controller at my work and since few weeks, we had to split our network at the branch office, creating 2 new subnets for the employees being connected to the wifi.

Since then, If we had to connect remotely to the branch HP Aruba controller there was no issue. However, if we tried to do the same locally, so myself being at the branch office, I was getting the Semaphore timeout period has expired. I managed to solve the issue by connecting locally through its IP address being on the same subnet as myself.

Can someone explain why though ?

Cheers! Xzi.



No comments:

Post a Comment