You are currently migrating users away from a legacy proxy to the Netskope client in the company's corporate offices. You have deployed the client to a pilot group; however, when the client attempts to connect to Netskope, it fails to establish a tunnel.
In this scenario, what would cause this problem?
30 comments · newest first
BI
Billye
10 months ago
What if it's a mix of all these problems? Just a thought!
MA
Markus
11 months ago
I agree, the firewall is probably the issue here.
PE
Pete
11 months ago
Wait, can the client really not reach dns.google? That seems odd.
SA
Samira
11 months ago
I think it's definitely the firewall blocking something.
JE
Jenelle
11 months ago
Sounds like the legacy proxy could be messing things up.
CA
Catina
12 months ago
I don't recall much about DNS issues, but if the client can't reach dns.google, that might also cause connection problems.
KA
Katy
12 months ago
I feel like we had a similar practice question about firewall rules and specific addresses. Could the Netskope EPoT address be blocked?
MA
Malcom
12 months ago
I'm not entirely sure, but I think if the firewall is blocking UDP port 443, it could prevent the client from connecting.
DA
Dante
1 year ago
I remember we discussed how legacy proxies can interfere with SSL/TLS traffic. That might be what's happening here.
IL
Iluminada
1 year ago
Okay, I think I've got a strategy here. I'll start by verifying the proxy settings, then check the firewall rules, and finally look into any DNS resolution problems. Gotta cover all the bases.
DO
Doyle
1 year ago
I'm a bit unsure about this one. The options cover a range of potential issues, so I'll need to carefully consider each one and try to eliminate the unlikely ones.
RA
Rashad
1 year ago
Ah, I see. The options mention firewall rules and DNS resolution, so those are good things to check as well. Gotta make sure all the network settings are configured properly.
AM
Amber
1 year ago
Hmm, the question mentions a legacy proxy, so that's probably the first thing I'd look at. The proxy could be interfering with the Netskope connection.
YU
Yuette
1 year ago
This seems like a tricky one. I'll need to think through the different network components and potential points of failure.
BE
Ben
1 year ago
I'm going with the legacy proxy. It's like the corporate version of that old 'man in the middle' trick. Gotta love it when technology tries to outsmart itself!
GA
Gayla
1 year ago
C) The corporate firewall is blocking the Netskope EPoT address.
EU
Eun
1 year ago
B) The corporate firewall is blocking UDP port 443 to Netskope.
YO
Youlanda
1 year ago
A) The legacy proxy is intercepting SSL/TLS traffic to Netskope.
KR
Krissy
1 year ago
Haha, I love these proxy migration problems. It's like a game of 'spot the bottleneck'! I'm putting my money on the legacy proxy, but hey, maybe the firewall admins are just having a bad day and decided to block everything.
BR
Brynn
1 year ago
C) The corporate firewall is blocking the Netskope EPoT address.
SE
Sean
1 year ago
B) The corporate firewall is blocking UDP port 443 to Netskope.
SH
Shannon
1 year ago
A) The legacy proxy is intercepting SSL/TLS traffic to Netskope.
JO
Josephine
1 year ago
You know, I bet it's the DNS resolution issue. The client can't reach dns.google, so the whole thing falls apart. Classic case of a simple DNS problem causing a world of trouble.
JA
Janna
1 year ago
Hmm, I'm not so sure. The corporate firewall could be the issue if it's blocking the UDP port or the Netskope EPoT address. Gotta love those overzealous firewall admins, am I right?
TR
Tresa
1 year ago
The legacy proxy is definitely the culprit here. It's probably intercepting the SSL/TLS traffic to Netskope and messing everything up. Classic proxy problem!
LE
Lemuel
1 year ago
B) The corporate firewall is blocking UDP port 443 to Netskope.
HI
Hillary
1 year ago
A) The legacy proxy is intercepting SSL/TLS traffic to Netskope.
VE
Verlene
2 years ago
I'm not sure about that. I think the corporate firewall blocking UDP port 443 to Netskope could also be a possible cause.
SH
Sherita
2 years ago
I agree with Eveline. That could definitely be causing the problem with the tunnel establishment.
EV
Eveline
2 years ago
I think the issue might be with the legacy proxy intercepting SSL/TLS traffic to Netskope.