Global Protect - Problem with name resolution DNS/WINS

[FabioGarcia]

Dears,

We are facing a strange problem... sometimes external users connected via global protect cannot resolve names without the sufrix domain... 

Example:

\\NAMESERVER

or

http://netflow:8080

Strange behavior below: when we ping that name we see that it is not being resolved...

But when we do a nslookup we see the name resolution is OK

browsing problems

Usually user has to disconnect global protect and connect again until the problem is solved by itself...

sometimes disable and reenable the PANGP virtual network card solves the problem as well

Does anyone seen that problem before ?

[pulukas]

Do you have the domain DNS (and WINS if you use this) setup with the domain name suffixes on your global protect settings.

Nework > Global Protect Gateway > network settings

[FabioGarcia]

Hello my friend!

thanks for your help.. I have already done that....

I am very confused about that behavoir where user can resolve at "nslookup" but cannot resolve when pinging

[Hithead]

hi,

this is (to 99% sure) not a GP problem.

In the past (some years ago) we also had a simular problem. Its a client problem.

check this out:

http://superuser.com/questions/495759/why-is-ping-unable-to-resolve-a-name-when-nslookup-works-fine

http://superuser.com/questions/220471/dns-resolution-issue-nslookup-works-but-web-ping-doesnt

http://www.fencepost.net/2009/11/dns-fails-nslookup-works-fix/

I'm sorry but I can't remember the correct solution but may you will find the way 🙂