One user cannot access internet on 2003server with ISA

I have a strange problem, 10 of my user accounts join the domain and connect to the internet via the server. The server has ISA configured.

However there is only one user who fails to access the internet. It seems for some reason ISA server cannot authenticate that aprticular user. If I go on that user's workstation and use admin or another user when the ISA authentification window pops up, I can get on the internet.

Help
cvmanziraPresidentAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

fm250Commented:
try to change the username and the password to something else and test. and then rename back and put the wanted password then log of the workstation and logon back and see if that solve it.
cvmanziraPresidentAuthor Commented:
tried and did not work. Looks like any new user added to the server is not able  authenticate on ISA.
scrathcyboyCommented:
Go into the user account using the ISA server view, and you will see that some settings are not defaulting to the right values, like "allow remote connection" -- you will see a whole list of options in the ISA server screen, check the right ones, and reboot the ISA server, reboot the client, and you should be able to now make a new account, and when you do, make sure those "checked settings" took.

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
CKWTCommented:
You must check your Event Log on both Server>Client, It will tell you exactly why both are carrying along.
Every attempt will create a log entry, check the Event ID and find solution to it and will solve that way...

I you could post them would be great.
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
Software Firewalls

From novice to tech pro — start learning today.