cancel
Showing results for 
Search instead for 
Did you mean: 

Port 8010 being blocked via Pulse

Highlighted
New Contributor

Port 8010 being blocked via Pulse

Hello, we are running Juniper MAG Pulse VPN. We are finding that TCP 8010 is being blocked somehow. We cannot establish connections to any machine on port 8010.
We have nothing in our firewalls preventing this port. We are not inadvertently using this port elsewhere.
As soon as we connect to our network bypassing Pulse VPN, port 8010 starts to work, therefore it points to the VPN causing this blockage.
Does anyone know of any issues with this port ?
2 REPLIES 2
Pulser

Re: Port 8010 being blocked via Pulse

Hi,

The TCP ports 8009-8010 are used for Session Data for Clustering [Applicable to 8.2+ and above] (https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB24280) but this would only be between the internal interface IP addresses of the cluster nodes so should not block any communication on those ports to other IP addresses.
Using tcpdump do you see the packets arriving on the external interface and leaving the internal interface and do the packets show up on the next hop router? On the PCS you can use the following filter to only capture the relevant traffic:

tcp port 8010

Pulser

Re: Port 8010 being blocked via Pulse

Also worth checking that the port is allowed by any access policies on the MAG, see:

https://docs.pulsesecure.net/WebHelp/PCS/8.3R1/Home.htm#PCS/PCS_AdminGuide_8.3/About_VPN_Tunneling_Resource.htm

and

https://docs.pulsesecure.net/WebHelp/PCS/8.3R1/Home.htm#PCS/PCS_AdminGuide_8.3/Defining_VPN_Tunneling_Access.htm