Remote user's NSLOOKUP resolves wrong IP address.

Good morning,

1. Remote user (XP service pack 3) was able to connect in with Sonicwall vpn client late last night.
2. Today he is unable to connect (other remotes are connected).  NSLOOKUP shows incorrect ip address for our host.
3. I changed the VPN host target to the host ip with same result.
3. User cannot access - goes to a google search page.
4. Provider Verizon claims, anecdotally, that they are receiving calls this morning from users having problems accessing secure sites (my user can access other secure sites).  They are blaming it on last night's Microsoft patch.
5. Only change to user's system is the patches.

1. Is anyone else experiencing this problem?
2. Does a bad NSLOOKUP imply DNS poisoning, and if so, where should I look?

Any advice is appreciated.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have the remote user restart their Verizon router, and then restart their computer.  Perhaps Verizon is having DNS problems with one of their DNS servers.

JosephLemosAuthor Commented:
Thanks, but I've tried restarting several times (as did the Verizon rep).  I suspect a DNS problem with Verizon, but I'm trying to find out if others are experiencing it as well.
Just saw this post.  Can you check the DNS server settings on that workstation?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JosephLemosAuthor Commented:
Thanks for the tip.  The DNS servers were Verizon's.  

Verizon did a hard reset of the modem/router, and I ran "netsh int ip reset" on the workstation - now it's working.  

I would still really like know what happen - bad DNS makes me very nervous.  BTW the workstation runs on limited privileges and I run Symantec Corporate Antivirus - doesn't mean I'm completely safe, but hopefully it helps.  The hosts files were also clean.
JosephLemosAuthor Commented:
Thanks for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.