Skip to main content
Question

Publisher not able to access private applications but can telnet

  • August 27, 2024
  • 3 replies
  • 237 views

Deepak_InfoTru
Netskope Partner
Forum|alt.badge.img+1

We are having an issue where user can`t access a private app via publisher and we have checked all the configuration is correct in Netskope Tenant and the same has been confirmed with Netskope Support engineering as well.

However, we can telnet the same application on the same port from publishers itself.

Both publishers and private applications are on the same subnet. 

 

When we run a TCPdump on the publishers we can see SYN packet from user`s machine is reaching to the publisher, but publisher is not getting SYN-ACK packet from the private applications. There is no firewall blocking it as publishers and private apps are in the same subnet.

 

Let me know what your thoughts on this.

 

This topic has been closed for replies.

3 replies

Forum|alt.badge.img+6
  • Netskope Employee
  • August 28, 2024

Where is the Publisher located? How was it built? Via the bootstrap script or is it a default AMI/OVA image from Netskope?

One thing that comes to mind is ipv4 forwarding being enabled and functioning correctly.

 

Is there a support case with logs/pcaps # I can check?

 

Cheers


Deepak_InfoTru
Netskope Partner
Forum|alt.badge.img+1
  • Author
  • Netskope Partner
  • August 28, 2024

Here is the case number: 00450766

Publisher located in the same subnet.

How to check IPv4 forwarding being enabled?

 

ia the bootstrap script or is it a default AMI/OVA image from Netskope? Checking this with client.

 

 


Deepak_InfoTru
Netskope Partner
Forum|alt.badge.img+1
  • Author
  • Netskope Partner
  • August 28, 2024

Hi Awyte,

 

IPv4 is enabled, but working correctly, no sure.

We use Curl command to spin up the new publisher as shown below:

 

curl https://s3-us-west-2.amazonaws.com/publisher.netskope.com/latest/generic/bootstrap.sh | sudo bash; sudo su - $USER; exit